XTerm.js fails with 500 Timeout waiting for port 5900

P

prototypeshogun

New Member
Jan 2, 2021
3
1
1
45
Since upgrading to 6.3-3 all containers are unable to start xterm.js. I have since created a new container with a freshly downloaded template and the issue persists there as well.

I do not have firewall enabled or iptables configured on the datacenter, node or container. Also not part of a cluster.


When running the command notated in the error log myself "/usr/bin/termproxy 5900 --path /vms/300 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole300 -r winch -z lxc-console -n 300 -e -1" I get a response of "failed waiting for client: Cannot assign requested address (os error 99)"
 
is anything listening on port 5900?
Code: 
ss -tanp | grep 590
 
prototypeshogun said:
When I run "ss -tanp | grep 590" as root on the container itself or the node I find nothing at all.
Click to expand...
termproxy runs on the PVE installation, not on the container - so the output from the PVE node is relevant.

hmm - could you please post the /etc/hosts of your pve-node?
 
Thanks, that was exactly it. After putting my /etc/hosts to "127.0.0.1 localhost" and cleaning up the contents of "/var/lib/rrdcached/db/pve2-"{node, storage} it's all better. It always seems to be a case of "what did you do recently" so I started down that path with that mention. Thanks again.
 
  • Like
Reactions: Stoiko Ivanov
Glad that worked out :)
please mark the thread as 'SOLVED' - this helps others who run into a similar problem

Thanks!
 
You must log in or register to reply here.
Top Bottom