Problem with one of the Subscriptions

T

tujek

New Member
Proxmox Subscriber
Jun 16, 2025
5
0
1
Hello
I have two Proxmox installations on two independent Dell servers. I also purchased two subscriptions for basic support. In the case of one of the instances, after entering the key, everything went smoothly, almost instantly. Unfortunately, in the case of the second instance, I receive the message:

Error checking subscription: https://shop.proxmox.com/modules/servers/licensing/verify.php: Dns Failed: resolve dns name 'shop.proxmox.com:443': failed to lookup address information: Temporary failure in name resolution (500)

Both servers work in the same network, so it's not a firewall :/
 

Attachments

  • Zrzut ekranu 2025-06-16 141942.png
    Zrzut ekranu 2025-06-16 141942.png
    14.5 KB · Views: 6
What's the host DNS configuration?
Please provide the output of pveversion -v and cat /etc/resolv.conf (in code tags, please!)
 
  • Like
Reactions: tujek
Code: 
root@apt:~# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-4-pve)
pve-manager: 8.3.0 (running version: 8.3.0/c1689ccb1065a83b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.0
libpve-storage-perl: 8.2.9
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.2.9-1
proxmox-backup-file-restore: 3.2.9-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.1
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-1
pve-ha-manager: 4.0.6
pve-i18n: 3.3.1
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.0
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
root@apt:~# ^C
root@apt:~#

Code: 
search local
nameserver 100.70.80.1
nameserver 100.70.1.1
root@apt:~# ^C
root@apt:~#
 

Attachments

  • Zrzut ekranu 2025-06-16 145839.png
    Zrzut ekranu 2025-06-16 145839.png
    10.5 KB · Views: 2
These DNS server addresses are part of the CGNAT-space - are these really correct? Do you have internal DNS servers running at these addresses?

What does host -v shop.proxmox.com 100.70.80.1 and host -v shop.proxmox.com 9.9.9.9 report for you?
What's the DNS configuration on the other server, where it works?
 
  • Like
Reactions: tujek
Yes, these addresses are correct - we are a network of institutions with our own DNS servers.

Code: 
root@apt:~# host -v shop.proxmox.com 100.70.80.1
Trying "shop.proxmox.com"
;; communications error to 100.70.80.1#53: timed out
;; communications error to 100.70.80.1#53: timed out
;; no servers could be reached

root@apt:~#

Code: 
root@apt:~# host -v shop.proxmox.com 9.9.9.9
Trying "shop.proxmox.com"
;; communications error to 9.9.9.9#53: timed out
;; communications error to 9.9.9.9#53: timed out
;; nie udało się dotrzeć do żadnych serwerów

These are the results from a server that ran without a problem:

Code: 
root@apt:~# pveversion -v
proxmox-ve: 8.4.0 (running kernel: 6.8.12-11-pve)
pve-manager: 8.4.1 (running version: 8.4.1/2a5fa54a8503f96d)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.8.12-11-pve-signed: 6.8.12-11
proxmox-kernel-6.8: 6.8.12-11
proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 18.2.4-pve3
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.0
libpve-cluster-perl: 8.1.0
libpve-common-perl: 8.3.1
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.6
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.1-1
proxmox-backup-file-restore: 3.4.1-1
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.2
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.11
pve-cluster: 8.1.0
pve-container: 5.2.6
pve-docs: 8.4.0
pve-edk2-firmware: 4.2025.02-3
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.1
pve-firmware: 3.15-4
pve-ha-manager: 4.0.7
pve-i18n: 3.4.4
pve-qemu-kvm: 9.2.0-5
pve-xtermjs: 5.5.0-2
qemu-server: 8.3.12
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve2
root@apt:~#

Code: 
root@apt:~# cat/etc/resolv.conf
search local
nameserver 100.70.80.1
root@apt:~# ^C
root@apt:~#

Code: 
root@apt:~# host -v shop.proxmox.com 100.70.80.1
Trying "shop.proxmox.com"
Using domain server:
Name: 100.70.80.1
Address: 100.70.80.1#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35503
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;shop.proxmox.com.              IN      A

;; ANSWER SECTION:
shop.proxmox.com.       900     IN      A       79.133.36.249

Received 50 bytes from 100.70.80.1#53 in 61 ms
Trying "shop.proxmox.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15182
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;shop.proxmox.com.              IN      AAAA

;; ANSWER SECTION:
shop.proxmox.com.       900     IN      AAAA    2a01:7e0:0:424::2

Received 62 bytes from 100.70.80.1#53 in 234 ms
Trying "shop.proxmox.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32174
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;shop.proxmox.com.              IN      MX

;; AUTHORITY SECTION:
proxmox.com.            679     IN      SOA     ns5.kapper.net. dns.kapper.net. 2025061101 10800 3600 604800 3600

Code: 
root@apt:~# host -v shop.proxmox.com 9.9.9.9
Trying "shop.proxmox.com"
Using domain server:
Name: 9.9.9.9
Address: 9.9.9.9#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17440
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;shop.proxmox.com.              IN      A

;; ANSWER SECTION:
shop.proxmox.com.       822     IN      A       79.133.36.249

Received 50 bytes from 9.9.9.9#53 in 35 ms
Trying "shop.proxmox.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21407
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;shop.proxmox.com.              IN      AAAA

;; ANSWER SECTION:
shop.proxmox.com.       900     IN      AAAA    2a01:7e0:0:424::2

Received 62 bytes from 9.9.9.9#53 in 27 ms
Trying "shop.proxmox.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44638
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;shop.proxmox.com.              IN      MX

;; AUTHORITY SECTION:
proxmox.com.            669     IN      SOA     ns5.kapper.net. dns.kapper.net. 2025061101 10800 3600 604800 3600

Received 88 bytes from 9.9.9.9#53 in 28 ms
 
Last edited:
tujek said:
Yes, these addresses are correct - we are a network of institutions with our own DNS servers.

Code: 
root@apt:~# host -v shop.proxmox.com 100.70.80.1 
Trying "shop.proxmox.com"
;; communications error to 100.70.80.1#53: timed out
;; communications error to 100.70.80.1#53: timed out
;; no servers could be reached
root@apt:~#
Click to expand...
So it seems the network is mis-configured on that server, as it can neither reach your internal DNS servers nor external.
Can you ping either of 100.70.80.1 and/or 9.9.9.9?

Are you sure there aren't some firewall rules blocking (at least) outgoing traffic from the problematic node?
Just because they are on the same network doesn't mean that different firewall rules can intercept traffic.

What's the network configuration (cat /etc/network/interfaces)?
I'd suggest some basic network troubleshooting, as this isn't Proxmox specific problem, but rather standard Linux networking.
 
  • Like
Reactions: tujek
Niestety, jedyną odpowiedzią na ping jest brama. Nawet systemy zainstalowane jako wirtualne na tym Proxmoxie nie reagują. Jednocześnie systemy te łączą się z Internetem bez problemu.


[KOD]root@apt:~# cat/etc/network/interfaces
auto lo
pętla zwrotna iface lo inet

instrukcja obsługi iface eno8303 inet

auto vmbr0
iface vmbr0 inet statyczny
adres 192.168.2.12/24
brama 100.70.80.1
porty mostowe eno8303
most-stp off
most-fd 0

instrukcja obsługi iface eno8403 inet

iface eno12399np0 inet instrukcja

iface eno12409np1 inet instrukcja


źródło/etc/network/interfaces.d/*[/CODE]

brama to 192.168.2.1... gdzie jest błąd?
 
Last edited:
tujek said:
gateway is 192.168.2.1... where is bug?
Click to expand...
You need to fix the gateway then in your /etc/network/interfaces file then - currently it is set to 100.70.80.1 as you can see above.

After that, you can run ifreload -a to reload the network configuration from /etc/network/interfaces.
 
  • Like
Reactions: tujek
Great!

Please just mark the thread as SOLVED by editing your first post - there is a dropdown near the title field. This helps making the forum search a lot more useful :)
 
You must log in or register to reply here.
Top Bottom