I have purchased a subscription key for Proxmox Mail Gateway Community Subscription 1 year, and when trying to add it to my pmg, it always:
Connection error - Timeout.
Connection error - Timeout.
[SOLVED] Add Subscription Key Connection error - Timeout.
- Thread starter LinuxCuba
- Start date
The problem is the server resolver shop.proxmox.com with ipv6 and only set ipv4.
root@pmg01:~# ping shop.proxmox.com
PING shop.proxmox.com(shop.proxmox.com (2a01:7e0:0:424::2)) 56 data bytes
^C
root@pmg01:~# host shop.proxmox.com
shop.proxmox.com has address 79.133.36.249
shop.proxmox.com has IPv6 address 2a01:7e0:0:424::2
root@pmg01:~# ping 79.133.36.249
PING 79.133.36.249 (79.133.36.249) 56(84) bytes of data.
64 bytes from 79.133.36.249: icmp_seq=1 ttl=54 time=11.6 ms
64 bytes from 79.133.36.249: icmp_seq=2 ttl=54 time=11.6 ms
64 bytes from 79.133.36.249: icmp_seq=3 ttl=54 time=11.5 ms
^C
doing ping witch the ipv4 address, no problem.
I have forced the name in the host file only with ipv4.
root@pmg01:~# ping -4 shop.proxmox.com
PING (79.133.36.249) 56(84) bytes of data.
64 bytes from shop.proxmox.com (79.133.36.249): icmp_seq=1 ttl=54 time=11.6 ms
64 bytes from shop.proxmox.com (79.133.36.249): icmp_seq=2 ttl=54 time=11.7 ms
64 bytes from shop.proxmox.com (79.133.36.249): icmp_seq=3 ttl=54 time=11.6 ms
^C
--- ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 11.559/11.616/11.726/0.077 ms
The problem was solved.
Thansk you.
How about the IPv6 part?
A change in the subscription code (from last autumn) was that if your host has an ipv6 address (and route ) configured connections to shop.proxmox.com will be tried on ipv6 (only)
A change in the subscription code (from last autumn) was that if your host has an ipv6 address (and route ) configured connections to shop.proxmox.com will be tried on ipv6 (only)
@Stoiko the server does not have a rerouting ipv6, which can reach the internet with ipv6, so it detects it, but it is not able to reach the store that way. Only has internet ipv4. I'm sorry for the delay. Thank you very much for helping to clarify. I think this problem can occur on many servers that have an ipv6 IP, not rerouted. Scope should be checked before forcing the use of ipv6 in the subscription mechanism.
Greetings.
Best regards.