TASK ERROR: command 'apt-get update' failed: exit code 100

C

cscript404

New Member
Sep 14, 2025
2
0
1
Hello everyone,

I'm very new to the world of Proxmox.

So far, everything has been working great. I just logged back into the host for the first time and got the message
TASK ERROR: command 'apt-get update' failed: exit code 100

I then tried the apt-get update command in the shell, which, as expected, didn't work. I'm attaching a screenshot of the shell.

Can anyone help me?

Thanks in advance for your help!
 

Attachments

  • Bildschirmfoto 2025-09-14 um 18.23.50.png
    Bildschirmfoto 2025-09-14 um 18.23.50.png
    357 KB · Views: 4
Hi, I'm new in proxmox also and facing the same problem, even though I currently have a paid support subscription.
1757990601237.png

root@pve1:~# apt update
Hit:1 http://ftp.debian.org/debian bookworm InRelease
Get:2 http://ftp.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:3 http://security.debian.org bookworm-security InRelease [48.0 kB]
Hit:4 http://download.proxmox.com/debian/pve bookworm InRelease
Get:5 http://download.proxmox.com/debian/pve bullseye InRelease [2,768 B]
Err:5 http://download.proxmox.com/debian/pve bullseye InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DD4BA3917E23BF59
Reading package lists... Done
W: GPG error: http://download.proxmox.com/debian/pve bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DD4BA3917E23BF59
E: The repository 'http://download.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


any clue ?

regards,
 
Last edited:
toosa said:
Hi, I'm new in proxmox also and facing the same problem, even though I currently have a paid support subscription.
View attachment 90660

root@pve1:~# apt update
Hit:1 http://ftp.debian.org/debian bookworm InRelease
Get:2 http://ftp.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:3 http://security.debian.org bookworm-security InRelease [48.0 kB]
Hit:4 http://download.proxmox.com/debian/pve bookworm InRelease
Get:5 http://download.proxmox.com/debian/pve bullseye InRelease [2,768 B]
Err:5 http://download.proxmox.com/debian/pve bullseye InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DD4BA3917E23BF59
Reading package lists... Done
W: GPG error: http://download.proxmox.com/debian/pve bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DD4BA3917E23BF59
E: The repository 'http://download.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


any clue ?

regards,
Click to expand...
I comment out bullseye in file "/etc/apt/sources.list.d/pve-enterprise.list "

#deb https://enterprise.proxmox.com/debian/pve bookworm pve-enterprise
# deb [signed-by=/usr/share/keyrings/pve-archive-keyring.gpg] http://download.proxmox.com/debian/pve bullseye pve-no-subscription

Then apt update works fine, and apt upgrade also works.

was that the right way to do ?

Regards,
 
Hi,
toosa said:
root@pve1:~# apt update
Hit:1 http://ftp.debian.org/debian bookworm InRelease
Get:2 http://ftp.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:3 http://security.debian.org bookworm-security InRelease [48.0 kB]
Hit:4 http://download.proxmox.com/debian/pve bookworm InRelease
Get:5 http://download.proxmox.com/debian/pve bullseye InRelease [2,768 B]
Err:5 http://download.proxmox.com/debian/pve bullseye InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DD4BA3917E23BF59
Reading package lists... Done
W: GPG error: http://download.proxmox.com/debian/pve bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DD4BA3917E23BF59
E: The repository 'http://download.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Click to expand...
toosa said:
I comment out bullseye in file "/etc/apt/sources.list.d/pve-enterprise.list "

#deb https://enterprise.proxmox.com/debian/pve bookworm pve-enterprise
# deb [signed-by=/usr/share/keyrings/pve-archive-keyring.gpg] http://download.proxmox.com/debian/pve bullseye pve-no-subscription

Then apt update works fine, and apt upgrade also works.
Click to expand...
but now you don't have a Proxmox repository configured anymore. You should configure the Proxmox repository for bookworm, so that it matches the Debian ones, see here: https://pve.proxmox.com/wiki/Package_Repositories#_proxmox_ve_8_repositories

toosa said:
Hi, I'm new in proxmox also and facing the same problem, even though I currently have a paid support subscription.
Click to expand...
Then you should use the enterprise repository. If there are any issues, please contact the enterprise support directly (you can still ask here in the forum too of course).

P.S. after fixing the repositories, make sure to always use apt full-upgrade or apt dist-upgrade rather than apt upgrade. An explanation for why can be found here: https://lore.proxmox.com/pve-devel/20240909102050.40220-1-f.ebner@proxmox.com/
 
You must log in or register to reply here.
Top Bottom