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

推荐订阅源

U
Unit 42
博客园 - 司徒正美
博客园 - 三生石上(FineUI控件)
博客园_首页
IT之家
IT之家
The Cloudflare Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
酷 壳 – CoolShell
酷 壳 – CoolShell
爱范儿
爱范儿
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Y
Y Combinator Blog
A
About on SuperTechFans
Microsoft Azure Blog
Microsoft Azure Blog
美团技术团队
S
SegmentFault 最新的问题
T
Tailwind CSS Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
M
MIT News - Artificial intelligence
WordPress大学
WordPress大学
B
Blog RSS Feed
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
博客园 - 【当耐特】
小众软件
小众软件
有赞技术团队
有赞技术团队

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
Subscription check behind proxy broken in PVE9
invalid@exam · 2026-06-17 · via Proxmox Support Forum

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?

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?

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!

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.

PVE 9 Debian 13
broken ipv6 no support to subscription

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.

broken here too, any idea when this will be fixed?

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.

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.

I used the same workaround and can confirm that a dummy ipv4 record on each host allows the license to validate. Thanks for the info.

I am trying your workaround but it is not working for me. The error persists. Can you provide me with your entry in the hosts file?

What surprises me is, that when I installed proxmox end of september, the registering of the key worked. What happened?

Last edited:

systemctl status ndppd
apt update
apt install ndppd

fix IPv6 NDP Proxy Daemon

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.

Thanks for this, it worked for me on 9 PVE nodes.