Subscription check behind proxy broken in PVE9

Aug 15, 2024
9
4
3
Ability to validate subscriptions via configured proxy server appears to have broken in version 9, not having issue on any nodes still on 8.
Receiving following error:

"Error checking subscription: io: failed to lookup address information: temporary failure in name resolution (500)"

indicating it is not trying to utilize the proxy
 
"Error checking subscription: io: failed to lookup address information: temporary failure in name resolution (500)"

It looks to me like Proxmox can't resolve the address. Can you resolve shop.proxmox.com?

Code:
ping shop.proxmox.com

Where did you enter the proxy server?

Code:
http_proxy: http://.*
Specify external http proxy which is used for downloads (example: http://username:password@host:port/)

What's the host DNS configuration?
Please provide the output of cat /etc/resolv.conf
 
It looks to me like Proxmox can't resolve the address. Can you resolve shop.proxmox.com?

Code:
ping shop.proxmox.com

Where did you enter the proxy server?

Code:
http_proxy: http://.*
Specify external http proxy which is used for downloads (example: http://username:password@host:port/)

What's the host DNS configuration?
Please provide the output of cat /etc/resolv.conf
DNS will not be able to resolve external addresses as it is in a segmented environment. 30 + other pve hosts running on pve8 and configured same way and work fine, DNS resolution is not necessary as the proxy server handles it.

Proxy server is configured under Options tab on data center.

1757521723268.png
 
could you file an issue on our bugzilla? thanks!
 
  • Like
Reactions: fireon
DNS will not be able to resolve external addresses as it is in a segmented environment. 30 + other pve hosts running on pve8 and configured same way and work fine, DNS resolution is not necessary as the proxy server handles it.

Proxy server is configured under Options tab on data center.

View attachment 90459

I tested this. A pure Apt proxy works. If your DNS resolution isn't working, you can also make an entry in /etc/hosts as an additional workaround.

I configured the proxy for Apt like this: /etc/apt/apt.conf.d/01proxy

Code:
Acquire::http { Proxy "http://myProxy:3128"; };

The proxy you configure in Proxmox Datacenter is usually entered in this file:
Code:
/etc/apt/apt.conf.d/76pveproxy
But unfortunately, that didn't work in my tests.
 
I tested this. A pure Apt proxy works. If your DNS resolution isn't working, you can also make an entry in /etc/hosts as an additional workaround.

I configured the proxy for Apt like this: /etc/apt/apt.conf.d/01proxy

Code:
Acquire::http { Proxy "http://myProxy:3128"; };

The proxy you configure in Proxmox Datacenter is usually entered in this file:
Code:
/etc/apt/apt.conf.d/76pveproxy
But unfortunately, that didn't work in my tests.
Making an entry in hosts would not direct the traffic through the proxy though? Internet is only accessible through the proxy.
 
Making an entry in hosts would not direct the traffic through the proxy though? Internet is only accessible through the proxy.

Well, I thought that if you enter the IPs + FQDN in the hosts file as a workaround and only set the proxy for Apt, it might work for you too.
 
I was able to trick it into working by putting in a dummy record in host file for shop.proxmox.com does not need to be the actual IP just something for it to get an Ipv4 address it appears. subscription check succeed afterwards.
 
  • Like
Reactions: fireon
there's a bugzilla entry linked higher up in the thread, please subscribe yourself to that - it will be updated once a fix is available.