I've setup a HAProxy balance roundrobin on the PVE HVs and I'm getting the following error after logging in successfully. Anyone has a successful config?
Actually, I've noticed that an authenticated session actually persists across different nodes.
Anyway, I've also managed to find a workaround for the ticket issue, I've ditched HAProxy and setup a nginx roundrobin reverse proxy with keepalive 1.
Better late than never. I registered just to leave the solution to this here since this is the first thread that appears when searching for this problem.
Please note that I configured this in OPNSense so it may not be exactly like your case but it should at least provide some guidance:
Navigate to the Services menu, and then click on HAProxy.
Switch to the Real Servers
Configure the Real Server (server address and server port), on the Common Options enable SSL!
Switch to the Backend Pools in the Virtual Services tabs
Create a new backend and configure it with the following settings:
Name: Enter a descriptive name for the backend (Proxmox_Backend).
Mode: Select "HTTP (Layer 7)" from the dropdown list.
Balance Algorithm: Select "Static Round Robin" from the dropdown list.
Server: The real server you created previously
Enable HTTP2/S
Save
Scroll down to the "Advanced settings" section (there's a toggle button on the top left corner for enabling advanced mode).
In the "Advanced pass thru" text box, add the following line (this is basically the keepalive 1 in NGinx):
http-reuse always
Switch to the Public Services on the Virtual Services tab
Add your servers to the frontend (Public Service) by with the following settings:
Name: Enter a descriptive name for the server (Proxmox_Frontend).
Listen address: Enter the "IP address : port" or "hostname : port" (without the spaces) of the server, in my case this is a Virtual IP that I created to access Proxmox from other subnet.
Type: HTTP / HTTPS (SSL Offloading)
Default Backend Pool: Proxmox_Backend
Enable SSL Offloading
Choose a Certificate (could be any of the existing ones)
Enable HTTP/2
Save
Navigate to the top of the HAProxy page and click on "Apply changes" to apply the new settings and restart the HAProxy service.
Now, HAProxy will use a round-robin balancing algorithm and reuse connections for multiple requests and it should no longer show the "Connection error 401: No ticket" error.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.