can't connect from outside network with SPICE

[vigilian]

Hi,

So I have a strange problem, this proxmox server si inside a LAN.
1/ I can connect from inside the network. I even not have to configure the firewall of the datacenter to accept the spice connection but maybe that's a logical behaviour but in opposite, I had to open the new ssh port in the firewall of the datacenter.
2/ I can't connect from outside the network. It's very strange because I have an edgemax router so I can see in real time the stat of accessing each port number, and there is no incrementation of this stat, so no request on this port is made.... Is there another port where the request is made? or virt-viewer isn't working in windows or am I missing a point somewhere?(tested on windows 7 and 10)
anyway the error message is :
Error sending data: Une requête d’envoi ou de réception de données n’a pas été autorisée car le socket n’est pas connecté et (lors de l’envoi sur un socket datagramme en utilisant un appel sendto) aucune adresse n’a été fournie.
so in substance, no address has been supplied,socket not connected etc
sometimes the error message change and give my that has been a socket I/O error to the adresse IP .... (which is the external adress ip of my server)

 

[JNL]

I have the exact same problem, can conect using a VPN and a local ip, but when loging to pmve using the public ip adress of the server Spice gives me those 2 errors. i tryed forwarding port 3128 to the local ip of the pmve server and to the local ip of the VM.

Help would be appreciated.

 

[redactedhosting]

I wanted to provide my solution in case someone may have had this issue in the future.

For me I installed a new router on another subnet for example -> Servers are on 192.168.2.0/24 and home devices are on 192.168.3.0/24 and I have e another router from 192.168.3.0/24 -> to a secure subnet ... In proxmox I could ping the VM I wanted to connect to and CANNOT ping the proxmox address... looking at the vv config I pinged the proxmox node address and was un able to reach it...

The solution was inside my firewall settings for inbound connections on my clusters, I did not update he inbound traffic for the new 192.168.3.0/24 address.. So when the traffic was going from "Secure subnet -> to 192.168.3.0/24 to 192.168.2.0/24 it detected a collision since 3.0 subnet was new and not on the allowed list, thus blocking the connection to the VM.

Solution: edit node 1 and node 2 inbound rules to allow your subnet from the subnet your other routers are on.

 

[klx]

My simple solution was to use Chrome Remote Desktop, I did not open any ports, all I need to do is get into one server from there I can ssh into other network devices. Also I have an IP to one of the magement nodes as a book mark in Chrome so when I remote in I can also access the proxmox cluster site. You have to have a VM with Chrome installed...and access the vm with a matching Chrome account..