I was able to perfectly access Windows VM running on Proxmox 9.0.x(older than 9.0.11 but still 9.0.x) host using Spice around month or two ago. I didn't use the Windows VM since then.
Since then I have only updated Proxmox host(which only had pve 9.0.x patch updates. I suspect one of the minor pve update caused it.
I don't recall exactly but I also updated the Windows VM yesterday too I think.
I've tried accessing the VM by clicking Console button on web UI for the Windows VM which downloads vv file. On openning, it gets stuck at 'Connecting to graphics server' followed by 'Unable to connect to graphics server <path-of-vv-file>'.
I tried on a Windows Desktop Client(remote-viewer.exe) and on Linux(Manjaro) client virt-viewer so it is not a client issue.
I faced the exact same issue yesterday and I updated host pve to 9.0.11 and rebooted the host after which above worked.
But today, I am facing the same issue again. Is this a reported bug? Just wanted to check here before I try to reboot the host again.
NoVNC works fine but I need SPICE for sound.
Update:Not exactly solved but this is not the correct question. It worked after I visited the web UI using IP not domain(resolved by local Technitium DNS).
2 issues:
1. It seems Proxmox makes vv file taking proxy from browser url.
2. virt-viewer doesn't seem to be resolving the IP correctly while browser and rest of client OS does.
Update 2:
Found the real root cause. For reasons I don't know(likely an ISP push), the IPv6 gateway(4th octet) on my router had changed which meant all IPv6 IPs set on my local network including VM and DNS server were not accessible via their IPv6 address. Changing it to new gateway IPs worked.
Since then I have only updated Proxmox host(which only had pve 9.0.x patch updates. I suspect one of the minor pve update caused it.
I don't recall exactly but I also updated the Windows VM yesterday too I think.
I've tried accessing the VM by clicking Console button on web UI for the Windows VM which downloads vv file. On openning, it gets stuck at 'Connecting to graphics server' followed by 'Unable to connect to graphics server <path-of-vv-file>'.
I tried on a Windows Desktop Client(remote-viewer.exe) and on Linux(Manjaro) client virt-viewer so it is not a client issue.
I faced the exact same issue yesterday and I updated host pve to 9.0.11 and rebooted the host after which above worked.
But today, I am facing the same issue again. Is this a reported bug? Just wanted to check here before I try to reboot the host again.
NoVNC works fine but I need SPICE for sound.
Update:
2 issues:
1. It seems Proxmox makes vv file taking proxy from browser url.
2. virt-viewer doesn't seem to be resolving the IP correctly while browser and rest of client OS does.
Update 2:
Found the real root cause. For reasons I don't know(likely an ISP push), the IPv6 gateway(4th octet) on my router had changed which meant all IPv6 IPs set on my local network including VM and DNS server were not accessible via their IPv6 address. Changing it to new gateway IPs worked.
Last edited: