Skip to content
DnsLister Forum

Where domain hunters compare notes

Cluster Web UI – “Could not connect to server” when accessing VM console on another node

I’m having an issue with the Proxmox web UI in a cluster and I’m trying to figure out whether this is related to my reverse proxy or the cluster configuration itself.
I have a cluster with multiple nodes (Node 1, Node 2, Node 3).
Originally, I had my reverse proxy pointing only to Node 1. When accessing the Proxmox UI through the reverse proxy, everything appears normally, including the VMs located on the other nodes.
However, if I select a VM running on Node 3 and try to open its console, I receive:
“Could not connect to server”
I initially assumed this was caused by the reverse proxy. However, I tested accessing Node 1 directly, bypassing the reverse proxy completely, and I still receive the same error when trying to open the console of a VM running on Node 3.
If I access Node 3 directly and open the same VM console, it works without any issues.
So currently:
● Node 1 UI → VM on Node 1: Works
● Node 1 UI → VM on Node 3: “Could not connect to server”
● Reverse Proxy → Node 1 → VM on Node 3: “Could not connect to server”
● Node 3 UI → VM on Node 3: Works
The cluster itself otherwise appears to be functioning normally.
Is there a particular service, port, certificate, hostname/DNS setting, or cluster communication issue I should check that would prevent one Proxmox node from proxying a VM console connection to another node?
I’m happy to provide logs or configuration details if someone can point me toward what would be useful to check.
Thanks!

Source: r/Proxmox · by /u/computerlovr1012

Leave a Reply

Your email address will not be published. Required fields are marked *