Network access to the Ubuntu Livepatch Service (https://livepatch.canonical.com:443) is necessary as well as snapd version 2.15 - check your snapd version with snap version.
In addition to that, sometimes it could be a problem with the proxy configurations. Please check out this guide on how to configure the Livepatch client to use a proxy.
Hi @alesstimec,
If appropriate, can we add the following section regarding livepatch proxy issues to this page?
Problem
When a machine operates behind a proxy, users may experience an issue while enabling the default Livepatch service. The error occurs as follows:
Enabling default service livepatch
Stderr: Could not retrieve client information.:
GET request to "https://livepatch.canonical.com/v1/client/<id>/info" failed`
Stdout:
Unable to enable Livepatch: Failed running command '/snap/bin/canonical-livepatch enable <REDACTED>' [exit(1)].
Message: Could not retrieve client information.:
GET request to "https://livepatch.canonical.com/v1/client/<id>/info" failed
Solution
First, detach the machine from the Pro service. This will allow you to modify the proxy settings without affecting the current Pro service configuration.
sudo pro detach
Before proceeding, ensure that the HTTP_PROXY and HTTPS_PROXY environment variables are set with the correct values.
Set the proxy configurations for both the canonical-livepatch and pro services:
sudo pro config set http_proxy=${HTTP_PROXY}
sudo pro config set https_proxy=${HTTPS_PROXY}
sudo canonical-livepatch config http-proxy=${HTTP_PROXY}
sudo canonical-livepatch config https-proxy=${HTTPS_PROXY}
After setting the proxy configurations, re-attach the machine to the Pro service:
sudo pro attach
Best regards,
adilcan
Hi @adilcan
Thanks for this! We were actually just about to add a separate page on how to configure the Livepatch Client to work behind a proxy. I think we can take what you’ve written up here and add it to a new page then link to that from here.
Hi @kian-parvin
Thanks for your reply! It’s great to know this will be useful. Please let me know if anything else is needed.
Best regards,
adilcan
Thank you, I didn’t think proxy 
sorry if this is obvious to everyone else but why do I need a proxy? I just want to download a file, do I have to sign up for nordvpn just to update ubuntu?
Ask your system administrator
This guide is indeed meant for people that are forced to use a proxy by i.e. company policy or some such and is supposed to help you setting up the proxy settings for livepatch in that case …
You do not need a proxy if there is none set up already …
thanks for the explainer, yes, I am my system administrator. Still can’t work out what is wrong with the post call in downloading livepatch.
What issue / error are you seeing when you try to download Livepatches?
stephen@saturn2:~$ sudo pro enable livepatch
One moment, checking your subscription first
Installing Livepatch
Setting up Livepatch
Unable to enable Livepatch: Failed running command '/snap/bin/canonical-livepatch enable <REDACTED>' [exit(1)]. Message: Could not retrieve client information.: unauthorized
an unknown error
Could not enable Livepatch.
stephen@saturn2:~$
also when I attempt to curl the url for it I get a post error.
I see, thanks. Could you please provide the output of the following commands, redacting any personal/sensitive info?
snap info canonical-livepatch
pro status
canonical-livepatch status
lsb_release -a
uname -a
journalctl -u snap.canonical-livepatch.canonical-livepatchd
USER@HOSTNAME:~$ snap info canonical-livepatch
name: canonical-livepatch
summary: Canonical Livepatch Client
publisher: Canonical✓
store-url: Install canonical-livepatch on Linux | Snap Store
contact: snaps@canonical.com
license: unset
description: |
Canonical Livepatch patches high and critical linux kernel vulnerabilities removing the immediate
need to reboot to upgrade the kernel, instead allowing the downtime to be scheduled. It is a part
of the Ubuntu Pro offering.
The Canonical Livepatch Client is an application that runs on your machine and periodically checks
for patches.
See our docs at --link–
commands:
SERVICE ENTITLED STATUS DESCRIPTION
anbox-cloud yes disabled Scalable Android in the cloud
esm-apps yes enabled Expanded Security Maintenance for Applications
esm-infra yes enabled Expanded Security Maintenance for Infrastructure
landscape yes disabled Management and administration tool for Ubuntu
livepatch yes disabled Canonical Livepatch service
realtime-kernel* yes disabled Ubuntu kernel with PREEMPT_RT patches integrated
usg yes enabled Security compliance and audit tools
For a list of all Ubuntu Pro services and variants, run ‘pro status --all’
Enable services with: pro enable
Account: REDACTED@REDACTED.COM
Subscription: Ubuntu Pro - free personal subscription
USER@HOSTNAME:~$
USER@HOSTNAME:~$
USER@HOSTNAME:~$ canonical-livepatch status
Command ‘canonical-livepatch’ is available in ‘/snap/bin/canonical-livepatch’
The command could not be located because ‘/snap/bin’ is not included in the PATH environment variable.
canonical-livepatch: command not found
USER@HOSTNAME:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.2 LTS
Release: 24.04
Codename: noble
USER@HOSTNAME:~$
USER@HOSTNAME:~$ uname -a
Linux saturn2 6.8.0-60-generic #63-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 15 19:04:15 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
USER@HOSTNAME:~$ journalctl -u snap.canonical-livepatch.canonical-livepatchd
Jun 11 17:24:11 saturn2 systemd[1]: Started snap.canonical-livepatch.canonical-livepatchd.service - Service for snap application canonical-livepatch.canonical-livepatchd.
Jun 11 17:24:12 saturn2 canonical-livepatch.canonical-livepatchd[1108]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share>
Jun 11 17:24:12 saturn2 canonical-livepatch.canonical-livepatchd[1108]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/c>
Jun 11 17:24:12 saturn2 canonical-livepatch.canonical-livepatchd[1108]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/g>
Jun 11 17:24:12 saturn2 canonical-livepatch.canonical-livepatchd[1108]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc>
Jun 11 17:24:12 saturn2 canonical-livepatch.canonical-livepatchd[1108]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/javascript /usr/share/java>
Jun 11 17:24:12 saturn2 canonical-livepatch.canonical-livepatchd[1108]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/shar>
Jun 11 17:24:12 saturn2 canonical-livepatch.canonical-livepatchd[1108]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme /usr/shar>
Jun 11 17:24:12 saturn2 canonical-livepatch.canonical-livepatchd[1108]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xu>
Jun 11 17:24:12 saturn2 canonical-livepatch.canonical-livepatchd[917]: Socket already exists; daemon did not exit cleanly! Removing old socket.
Jun 11 17:24:12 saturn2 canonical-livepatch.canonical-livepatchd[917]: Socket already exists; daemon did not exit cleanly! Removing old socket.
– Boot e8fc7abf46fd46babae61ea1f80b9233 –
Jun 11 19:41:09 saturn2 systemd[1]: Started snap.canonical-livepatch.canonical-livepatchd.service - Service for snap application canonical-livepatch.canonical-livepatchd.
Jun 11 19:41:09 saturn2 canonical-livepatch.canonical-livepatchd[1112]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share>
Jun 11 19:41:09 saturn2 canonical-livepatch.canonical-livepatchd[1112]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/c>
Jun 11 19:41:09 saturn2 canonical-livepatch.canonical-livepatchd[1112]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/g>
Jun 11 19:41:09 saturn2 canonical-livepatch.canonical-livepatchd[1112]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc>
Jun 11 19:41:09 saturn2 canonical-livepatch.canonical-livepatchd[1112]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/javascript /usr/share/java>
Jun 11 19:41:09 saturn2 canonical-livepatch.canonical-livepatchd[1112]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/shar>
Jun 11 19:41:09 saturn2 canonical-livepatch.canonical-livepatchd[1112]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme /usr/shar>
Jun 11 19:41:09 saturn2 canonical-livepatch.canonical-livepatchd[1112]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xu>
Jun 11 19:41:10 saturn2 canonical-livepatch.canonical-livepatchd[914]: Socket already exists; daemon did not exit cleanly! Removing old socket.
Jun 11 19:41:10 saturn2 canonical-livepatch.canonical-livepatchd[914]: Socket already exists; daemon did not exit cleanly! Removing old socket.
Jun 11 21:23:50 saturn2 canonical-livepatch.canonical-livepatchd[914]: Updating config.
Jun 11 21:23:50 saturn2 canonical-livepatch.canonical-livepatchd[914]: Config change detected, signaling restarting.
Jun 11 21:23:50 saturn2 canonical-livepatch.canonical-livepatchd[914]: Server received context done, stopping.
Jun 11 21:23:50 saturn2 canonical-livepatch.canonical-livepatchd[914]: Received context done signal (context canceled), stopping kernel event listener.
Jun 11 21:23:50 saturn2 canonical-livepatch.canonical-livepatchd[914]: Server received context done, stopping.
Jun 11 21:23:50 saturn2 canonical-livepatch.canonical-livepatchd[914]: Socket server shutting down.
Jun 11 21:23:50 saturn2 canonical-livepatch.canonical-livepatchd[914]: Socket server shutting down.
Jun 11 21:23:50 saturn2 canonical-livepatch.canonical-livepatchd[914]: Detected config change, reloading.
Jun 11 21:23:50 saturn2 canonical-livepatch.canonical-livepatchd[914]: Validating client resource token.
Jun 11 21:23:50 saturn2 canonical-livepatch.canonical-livepatchd[914]: failed to retrieve client info: unauthorized
Jun 11 21:23:50 saturn2 canonical-livepatch.canonical-livepatchd[914]: cause: unauthorized
Jun 11 21:48:27 saturn2 canonical-livepatch.canonical-livepatchd[914]: Updating config.
Jun 11 21:48:27 saturn2 canonical-livepatch.canonical-livepatchd[914]: Config change detected, signaling restarting.
Jun 11 21:48:27 saturn2 canonical-livepatch.canonical-livepatchd[914]: Server received context done, stopping.
Jun 11 21:48:27 saturn2 canonical-livepatch.canonical-livepatchd[914]: Received context done signal (context canceled), stopping kernel event listener.
Jun 11 21:48:27 saturn2 canonical-livepatch.canonical-livepatchd[914]: Server received context done, stopping.
Jun 11 21:48:27 saturn2 canonical-livepatch.canonical-livepatchd[914]: Socket server shutting down.
Jun 11 21:48:27 saturn2 canonical-livepatch.canonical-livepatchd[914]: Socket server shutting down.
Jun 11 21:48:27 saturn2 canonical-livepatch.canonical-livepatchd[914]: Detected config change, reloading.
Jun 11 21:48:27 saturn2 canonical-livepatch.canonical-livepatchd[914]: Validating client resource token.
Jun 11 21:48:28 saturn2 canonical-livepatch.canonical-livepatchd[914]: failed to retrieve client info: unauthorized
Jun 11 21:48:28 saturn2 canonical-livepatch.canonical-livepatchd[914]: cause: unauthorized
Jun 11 23:43:08 saturn2 systemd[1]: Stopping snap.canonical-livepatch.canonical-livepatchd.service - Service for snap application canonical-livepatch.canonical-livepatchd…
Jun 11 23:43:08 saturn2 canonical-livepatch.canonical-livepatchd[914]: Received context done signal (context canceled), stopping kernel event listener.
Jun 11 23:43:08 saturn2 canonical-livepatch.canonical-livepatchd[914]: Server received context done, stopping.
Jun 11 23:43:08 saturn2 canonical-livepatch.canonical-livepatchd[914]: Socket server shutting down.
Jun 11 23:43:08 saturn2 canonical-livepatch.canonical-livepatchd[914]: Server received context done, stopping.
Jun 11 23:43:08 saturn2 canonical-livepatch.canonical-livepatchd[914]: Socket server shutting down.
Jun 11 23:43:08 saturn2 canonical-livepatch.canonical-livepatchd[914]: daemon shutting down
Jun 11 23:43:08 saturn2 systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Main process exited, code=exited, status=1/FAILURE
Jun 11 23:43:08 saturn2 systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Failed with result ‘exit-code’.
Jun 11 23:43:08 saturn2 systemd[1]: Stopped snap.canonical-livepatch.canonical-livepatchd.service - Service for snap application canonical-livepatch.canonical-livepatchd.
Jun 11 23:43:08 saturn2 systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Consumed 1.195s CPU time, 32.2M memory peak, 0B memory swap peak.
– Boot 077c8136b3b640a0891dffd3950752f9 –
Jun 12 00:01:19 saturn2 systemd[1]: Started snap.canonical-livepatch.canonical-livepatchd.service - Service for snap application canonical-livepatch.canonical-livepatchd.
USER@HOSTNAME:~$
Thanks for the info! From what I can see, the issue is that your Pro token doesn’t seem to be authorized to use Livepatch even though the pro status output says so. I will check with my Pro colleagues and get back to you.
Hey, thanks for your help. Actually I think by problem is that my machine was using tailscale with pihole and all I needed to do was to reenable a traditional dns connection and then detach/attach pro and then it worked. Thanks for your help.
I’m glad to hear you got it working