Console not working when using round-robin domain

voydus

New Member
Apr 21, 2023
1
0
1
Hey everyone

We are having this issue since I've joined my org and none of us have a clue

Our Setup:
- Three node cluster (pve01.domain, pve02.domain and pve03.domain)
- Round-robin dns pve.domain which returns all three IPs
- We use yubikeys with webauthn, which forces us to use the round-robin domain

Problem:
- Trying to open the console fails with "Failed to connect to server"
- System logs show: pveproxy[1297551]: connect to 'localhost:5901' failed: Connection refused at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 541.

When I access the cluster through one of the direct domain names, it works and I see this in the journal:
Code:
pvedaemon[1523719]: starting vnc proxy UPIDve01:some-numbers:that-i-dont-know:if-they-are-secret:vncproxy:102:my.user@pve:
pvedaemon[1157582]: <my.user@pve> starting task UPIDve01:same-numbers-again:vncproxy:102:my.user@pve:

This is not really too bad, but it's annoying and I fear it might be indicative of some misconfiguration that could affect more things.

We're (sadly still) using VE 7.1-8
 
Last edited:
Hey everyone

We are having this issue since I've joined my org and none of us have a clue

Our Setup:
- Three node cluster (pve01.domain, pve02.domain and pve03.domain)
- Round-robin dns pve.domain which returns all three IPs
- We use yubikeys with webauthn, which forces us to use the round-robin domain

Problem:
- Trying to open the console fails with "Failed to connect to server"
- System logs show: pveproxy[1297551]: connect to 'localhost:5901' failed: Connection refused at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 541.

When I access the cluster through one of the direct domain names, it works and I see this in the journal:
Code:
pvedaemon[1523719]: starting vnc proxy UPIDve01:some-numbers:that-i-dont-know:if-they-are-secret:vncproxy:102:my.user@pve:
pvedaemon[1157582]: <my.user@pve> starting task UPIDve01:same-numbers-again:vncproxy:102:my.user@pve:

This is not really too bad, but it's annoying and I fear it might be indicative of some misconfiguration that could affect more things.

We're (sadly still) using VE 7.1-8
I have exactly the same problem.
 
DNS round-robin unfortunately won't work, due to the way the API works.

I'd suggest using a proper reverse proxy like e.g. nginx or haproxy, which can handle these situations (keyword: sticky sessions).
We have some documentation for that: https://pve.proxmox.com/wiki/Web_Interface_Via_Nginx_Proxy
HAProxy works too, the config can be easily adapted from the nginx example.
 

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!