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

推荐订阅源

IT之家
IT之家
Recent Announcements
Recent Announcements
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The GitHub Blog
The GitHub Blog
MyScale Blog
MyScale Blog
爱范儿
爱范儿
GbyAI
GbyAI
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
美团技术团队
Y
Y Combinator Blog
博客园 - 叶小钗
Apple Machine Learning Research
Apple Machine Learning Research
Martin Fowler
Martin Fowler
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
罗磊的独立博客
M
MIT News - Artificial intelligence
博客园 - Franky
V
Visual Studio Blog
I
InfoQ
V
V2EX
Hugging Face - Blog
Hugging Face - Blog
腾讯CDC
博客园 - 司徒正美
L
LangChain Blog

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
Proxy setup for PDM for updates in restricted environment
invalid@exam · 2026-06-17 · via Proxmox Support Forum

Howdy,
I have PDM, PBS, and my PVE clusters disconnected from the internet, and was preparing to start running updates though my proxy server, but I can't find a way to add a http proxy to PDM. I was able to use the Datacenter > Options > HTTP proxy for each cluster and Configuration > Other > General > HTTP proxy for PBS.

Moreover, I want to start using PDM to manage my license keys, but when trying to deploy them to my clusters the keys can't be applied because of DNS. I have tested the proxy on all other nodes (except PDM) and apt updates work as expected. So, I'm not sure if my PVE nodes are failing to use the proxy for shop.proxmox.com or if the failure is from PDM not having access to the proxy.

Regardless, I need to add a http proxy to PDM for apt updates at a minimum but can't find a way to add it in the GUI.

Here is the result of trying to apply licenses to one cluster:

Code:

Task Viewer: subscription-apply-pending
2026-06-16T14:04:27-06:00: pushing pve1s-1...9 to BDC-Cluster/BDC-PVE1...
2026-06-16T14:04:42-06:00: push of pve1s-1...9 to BDC-Cluster/BDC-PVE1 failed: api error (status = 500: Error checking subscription: io: failed to lookup address information: Temporary failure in name resolution
)
2026-06-16T14:04:42-06:00: pushing pve1s-7...1 to BDC-Cluster/BDC-PVE2...
2026-06-16T14:05:01-06:00: push of pve1s-7...1 to BDC-Cluster/BDC-PVE2 failed: api error (status = 500: Error checking subscription: io: failed to lookup address information: Temporary failure in name resolution
)
2026-06-16T14:05:01-06:00: pushing pve1s-8...c to BDC-Cluster/BDC-PVE3...
2026-06-16T14:05:16-06:00: push of pve1s-8...c to BDC-Cluster/BDC-PVE3 failed: api error (status = 500: Error checking subscription: io: failed to lookup address information: Temporary failure in name resolution
)
2026-06-16T14:05:16-06:00: TASK ERROR: apply-pending: 0/3 succeeded, 3 failed: push to BDC-Cluster/BDC-PVE1: api error (status = 500: Error checking subscription: io: failed to lookup address information: Temporary failure in name resolution
); push to BDC-Cluster/BDC-PVE2: api error (status = 500: Error checking subscription: io: failed to lookup address information: Temporary failure in name resolution
); push to BDC-Cluster/BDC-PVE3: api error (status = 500: Error checking subscription: io: failed to lookup address information: Temporary failure in name resolution
)

And hopefully relevant information for my PDM node (moved to network with internet access temporarily to get updated to 1.1.4):

Code:

$ `proxmox-datacenter-manager-admin versions --verbose`
```
proxmox-datacenter-manager-meta      1.1.0         running kernel: 7.0.6-2-pve
proxmox-datacenter-manager           1.1.4         running version: 1.1.4    
proxmox-kernel-helper                9.2.0                                  
proxmox-kernel-7.0                   7.0.6-2                                
proxmox-kernel-7.0.6-2-pve-signed    7.0.6-2                                
proxmox-kernel-6.17                  6.17.13-13                              
proxmox-kernel-6.17.13-13-pve-signed 6.17.13-13                              
proxmox-kernel-6.17.2-2-pve-signed   6.17.2-2                                
ifupdown2                            3.3.0-1+pmx12                          
proxmox-mail-forward                 1.0.3                                  
proxmox-mini-journalreader           1.6                                    
proxmox-offline-mirror-helper        0.7.4                                  
pve-xtermjs                          6.0.0-1                                
zfsutils-linux                       2.4.2-pve1
```

And a report from one PVE node (they are all identical, right of the first PVE 9 ISO):

Code:

# pveversion --verbose
proxmox-ve: 9.0.0 (running kernel: 6.14.8-2-pve)
pve-manager: 9.0.3 (running version: 9.0.3/025864202ebb6109)
proxmox-kernel-helper: 9.0.3
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
proxmox-kernel-6.14: 6.14.8-2
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx9
intel-microcode: 3.20250512.1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.9
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.3
libpve-network-perl: 1.1.6
libpve-rs-perl: 0.10.7
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2
lxc-pve: 6.0.4-2
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.9-1
proxmox-backup-file-restore: 4.0.9-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.1
proxmox-kernel-helper: 9.0.3
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.0
proxmox-widget-toolkit: 5.0.4
pve-cluster: 9.0.6
pve-container: 6.0.9
pve-docs: 9.0.7
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.16-3
pve-ha-manager: 5.0.4
pve-i18n: 3.5.2
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.16
smartmontools: 7.4-pve1
spiceterm: 3.4.0
swtpm: 0.8.0+pve2
vncterm: 1.9.0
zfsutils-linux: 2.3.3-pve1