Your submission was sent successfully! Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

Use a proxy when fetching patches

Livepatch on-prem server can fetch patches through an HTTP proxy. The configuration steps vary depending on the deployment platform.

See our patch-sync config for more details.

Juju deployments (latest charms)

If Livepatch on-prem has been deployed using Juju, run the following Juju configuration command:

$ juju config livepatch \
    patch-sync.proxy.enabled=true \
    patch-sync.proxy.http=http://proxy.example.com \
    patch-sync.proxy.https=http://proxy.example.com

Juju deployments (deprecated charm)

If Livepatch on-prem has been deployed using Juju with our older reactive charm (see our migration guide here), run the following Juju configuration command:

$ juju config livepatch \
    http_proxy=http://proxy.example.com \
    https_proxy=http://proxy.example.com

Snap deployments

If Livepatch on-prem has been deployed using Snap, users can run the following commands to configure a proxy:

$ sudo snap set canonical-livepatch-server lp.patch-sync.proxy.enabled=true
$ sudo snap set canonical-livepatch-server lp.patch-sync.proxy.http=http://proxy.example.com
$ sudo snap set canonical-livepatch-server lp.patch-sync.proxy.https=http://proxy.example.com

You can see the applied configuration by running the following:

$ sudo snap get canonical-livepatch-server lp.patch-sync.proxy
Key                          Value
lp.patch-sync.proxy.enabled  true
lp.patch-sync.proxy.http     http://proxy.example.com
lp.patch-sync.proxy.https    http://proxy.example.com

This page was last modified 14 days ago. Help improve this document in the forum.