惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

月光博客
月光博客
云风的 BLOG
云风的 BLOG
小众软件
小众软件
雷峰网
雷峰网
博客园 - 【当耐特】
V
V2EX
WordPress大学
WordPress大学
IT之家
IT之家
Last Week in AI
Last Week in AI
罗磊的独立博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Apple Machine Learning Research
Apple Machine Learning Research
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
Visual Studio Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
有赞技术团队
有赞技术团队
The Cloudflare Blog
Jina AI
Jina AI
博客园 - 司徒正美
阮一峰的网络日志
阮一峰的网络日志
博客园 - 聂微东
大猫的无限游戏
大猫的无限游戏
博客园 - 三生石上(FineUI控件)
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
Premium Tier On Cluster but cannot use PDM Enterprise Rep...
invalid@exam · 2026-06-18 · via Proxmox Support Forum

Hey there, I currently have a three node cluster on Premium Tier and my PDM Subscription Status shows "active" and Subscription Ratio (Basic or Higher): 100% (>=80%) but when I run

I get:

Code:

Err:4 https://enterprise.proxmox.com/debian/pdm trixie InRelease
  401  Unauthorized [IP: 66.70.154.82 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pdm/dists/trixie/InRelease  401  Unauthorized [IP: 66.70.154.82 443]
E: The repository 'https://enterprise.proxmox.com/debian/pdm trixie 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.

Code:

cat /etc/apt/sources.list.d/pdm-enterprise.sources
Types: deb
URIs: https://enterprise.proxmox.com/debian/pdm
Suites: trixie
Components: pdm-enterprise
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg

I adopted the Keys for all three nodes in my Node Subscription Status page. Previously I did have another cluster with two nodes I was using for testing that weren't subscribed - could that somehow be causing me to have this behavior still? Would reinstalling be easier at this point? I'm on PDM 1.1.1 and it was a fresh install of that to begin with, I didn't upgrade from a prior version.

Code:

proxmox-datacenter-privileged-api[541]: No valid Basic+ subscription found for configuring enterprise repository access..

I see that in the log when I attempt to refresh the license status in the Subscription Registry page with the refresh arrow icon. It's odd because that totally contradicts what I'm seeing in my Subscription Registry with the licenses being active and on Premium.

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...

I found this post finally and that got me sorted out! Thanks all!