[SOLVED] spice currently is IPv4 only

hk@

Renowned Member
Feb 10, 2010
247
7
83
Vienna
kapper.net
well, trying to get spice to work - and it always failed to connect to the server....

finally ending up tcpdumping on the host for port 3128...

and there we got it: IPv6 calls are not answered, while after changing to IPv4 all is fine.

probably because of this:
tcp 0 0 0.0.0.0:3128 0.0.0.0:* LISTEN 1880/spiceproxy

could we get this to ":::3128" please?

thx!
 
  • Like
Reactions: fr3d3r1c
could we get this to ":::3128" please?

You should be able to get this to work by changing /etc/hosts so that the nodename resolves to the IPv6 public (or LAN, if only locally reachable) address of that node. After that restart the "pveproxy" and "spiceproxy" services to bring the change in effect. With that the node should listen on :: for all public facing sockets and thus accept both IPv6 and IPv4.
 
You should be able to get this to work by changing /etc/hosts so that the nodename resolves to the IPv6 public (or LAN, if only locally reachable) address of that node. After that restart the "pveproxy" and "spiceproxy" services to bring the change in effect. With that the node should listen on :: for all public facing sockets and thus accept both IPv6 and IPv4.

thx!

the trick is to put _hostname_ in /etc/hosts, not the FQDN of the host, but the hostname part only - now spiceproxy is dual-stack reachable.
 
Last edited:
  • Like
Reactions: fr3d3r1c

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!