Update impossible after upgrade to PDM 1.1.1

Jun 2, 2026
3
0
1
After we upgrade from PDM 1.0 to 1.1.1 it's seems impossible to run de updates.
We have a valid Base subscription and with the pdm-enterprise repository, we get the following error:

2026-06-02T14:37:47+02:00: starting apt-get update
2026-06-02T14:37:49+02:00: Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease
Hit:3 http://security.debian.org/debian-security trixie-security InRelease
Err:4 https://enterprise.proxmox.com/debian/pdm trixie InRelease
401 Unauthorized [IP: 45.144.208.36 443]
Reading package lists...

2026-06-02T14:37:49+02:00: E: Failed to fetch https://enterprise.proxmox.com/debian/pdm/dists/trixie/InRelease 401 Unauthorized [IP: 45.144.208.36 443]
E: The repository 'https://enterprise.proxmox.com/debian/pdm trixie InRelease' is not signed.

2026-06-02T14:37:49+02:00: TASK WARNINGS: 1

It's only possible to update with the no-subscription repository.
What are we doing wrong?
 
I've encountered a similar phenomenon.


Code:
2026-06-02T21:42:00+09:00: starting apt-get update
2026-06-02T21:42:03+09:00: Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease
Hit:3 http://security.debian.org/debian-security trixie-security InRelease
Err:4 https://enterprise.proxmox.com/debian/pdm trixie InRelease
  401  Unauthorized [IP: 51.79.228.122 443]
Reading package lists...

2026-06-02T21:42:03+09:00: E: Failed to fetch https://enterprise.proxmox.com/debian/pdm/dists/trixie/InRelease  401  Unauthorized [IP: 51.79.228.122 443]
E: The repository 'https://enterprise.proxmox.com/debian/pdm trixie InRelease' is not signed.

2026-06-02T21:42:03+09:00: TASK WARNINGS: 1
 
Can you run the following commands and post the output here?
proxmox-datacenter-manager-admin support-status update
proxmox-datacenter-manager-admin support-status get

Make sure the output does not include any sensitive information before posting it.
 
Last edited:
As promised a short update: The patch got applied and will be included in the 1.1.4 update for proxmox-datacenter-manager [1]. The package has not yet been published, it will likely become available shortly. Once it is available you should be able to update from the enterprise repository with the following workaround command:

Code:
rm /run/proxmox-datacenter-manager/api-cache/remote-*/subscription-state.json &&\
    proxmox-datacenter-manager-admin support-status update &&\
    apt update &&\
    apt dist-upgrade

This should remove the cached version of the subscription information and fetch the new one right away. Thus, the time to lose the status race here should be reduced as much as possible. You might have to try a few times if this does not work right away. After upgrading to 1.1.4, this workaround should no longer be needed.

[1]: https://git.proxmox.com/?p=proxmox-...7;hb=f5808f25f011ac00d6deb46c0298a416d9465528
 
Last edited:
  • Like
Reactions: carles89
Is this update live in the enterprise repository? Ive only got 1.1.1:
Code:
# apt update
...
Hit:3 https://enterprise.proxmox.com/debian/pdm trixie InRelease
...
All packages are up to date
# dpkg -l | grep proxmox-datacenter
ii  proxmox-datacenter-manager           1.1.1                                amd64        Manage multiple Proxmox VE cluster and other Proxmox projects
ii  proxmox-datacenter-manager-client    1.1.1                                amd64        CLI Client for the Proxmox Datacenter Manager
ii  proxmox-datacenter-manager-docs      1.1.1                                all          Documentation for the Proxmox Datacenter Manager.
ii  proxmox-datacenter-manager-ui        1.1.1                                amd64        Web UI to for the Proxmox Datacenter Manager
 
Is this update live in the enterprise repository? Ive only got 1.1.1:
At time of my last post it wasn't published at all yet, by now it made its way to no-subscription. So no, currently this is not in the enterprise repo yet. You'll either have to wait a little longer, or go down to the no-sub repository, then update once from there and switch back to enterprise.

However, there are a couple more changes since 1.1.1, so if you want to be cautious, waiting until it becomes available is currently the way to go.
 
Last edited: