[SOLVED] Developer Workstation can't connect via SPICE

ianr-ks

Member
Aug 2, 2020
8
0
6
53
Hello all, I've installed proxmox on top of Debian as a developer workstation (so the dev workstation is running both a desktop environment and proxmox) and made this part of a cluster. All works fine and when logged into the developer workstation and running the proxmox UI, I can connect to VMs via the NoVNC method but I can't connect via SPICE. When I try, whether to locally-hosted VMs or remotely-hosted VMs I get the following error:
1597054467527.png
This only happens when I am logged into the developer workstation and trying to connect to VMs from the ProxMox UI. I've tried saving the profile file off instead of getting the browser to fire up remote-viewer itself but that changes nothing. I've also tried editing the profile file to make the connection host "localhost" or "127.0.0.1" or various other values but the best I can do so far is to get it to change to a different address other than ::1 (IPv6 localhost).

I've tried launching from Chromium and from Firefox, no change.

I can connect to the VMs from other machines such as my KDE laptop and also from Raspberry Pis using their version of Debian but I can't connect to any spice clients from Proxmox's web UI from the developer workstation using SPICE. I can however connect to a SPICE client from the command-line avoiding proxmox's UI so it's only connections triggered from the proxmox web UI on the developer workstation that fail.

Any ideas on how to fix this? The contents of my /etc/hosts file is as follows:
127.0.0.1 localhost 172.16.188.122 d01c02n02f.middle d01c02n02f # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters
 
Last edited:
Do you use IPv6? If not, try to disable it.
Otherwise try to change the /etc/hosts file and use an IPv6 address with the hostname and FQDN before the IPv4. Then restart spiceproxy.

systemctl restart spiceproxy
 
Ah OK I've done a few quick tests by editing /etc/hosts and this seems to work now so I'll just decide which of the two solutions fits my needs best, thanks for the quick reply.
 

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!