[Termproxy] failed to open socket

JonnyB

New Member
May 30, 2020
2
2
1
26
Hey everyone,

we are currently troubleshooting a error with our shell. We don't know the exact point where this error occured.
Since about two weeks we can't access out shell via the web gui (pve).


We get the following error:

1590821789043.png


While watching the logs we found this:
1590821834332.png

There should be no problem with Proxmox itself, because it's only connecting via a websocket to the xterm.js.
We have absolutly no idea how to solve this problem. We checked several things.
Port 5900 isn't blocked by any other application. There is no block in a firewall.
We are running Proxmox on version 6-2-4 (latest OVH template).

It seems like termproxy isn't able to start in all cases. We removed some arguments because they are "invalid".
Even with running only "termproxy 5900" we'll get this error.

Would be great if someone could probably help us.

Thanks :)
 
Fixed it ourself. Because there are several threads open from the past without any solution... here is ours:

Someone edited the /etc/hosts for some fancy hostnames and deleted localhost.

127.0.0.1 localhost



What was the problem? Termproxy is binding the port '5900' to localhost. With no localhost available we got this error.
Change the /etc/hosts file and add the localhost like shown above. Restart your system and you should be fine :)

Greetings.

/close
 
Last edited:

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!