Proxy setup for PDM for updates in restricted environment

A

AaronCOW

New Member
Proxmox Subscriber
Oct 5, 2025
5
3
3
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
 
  • Like
Reactions: bosswaffle
Cold_Cloud_1 said:
For PDM proxy
Add this file
/etc/profile.d/proxy.sh
contents:
Code: 
export http_proxy=(yourproxyinfo)
and this file
/etc/apt/apt.conf
contents:
Code: 
Acquire::http:Proxy (your proxy info)
Click to expand...
Thanks, after adding a file to /etc/apt/apt.conf.d with my proxy information I was able to perform updates.

i am however leery of adding the system wide proxy in /etc/profile.d/ since my PVE nodes with the proxy configured don't have such a file and the http_proxy and https_proxy environment variables are empty.
Code: 
root@NWTF-PVE1:/etc/profile.d# echo $http_proxy

root@NWTF-PVE1:/etc/profile.d# echo $https_proxy

root@NWTF-PVE1:/etc/profile.d#
This makes me think that I might not need the system wide proxy, also I don't have enough licensed nodes to try and activate the PDM enterprise repository. Until I fix that I might not know if it's necessary.
 
You must log in or register to reply here.
Top Bottom
Back