Hi,
I'm trying to set up an x2go broker using x2gobroker-wsgi, and it seems to be almost working - but fails at the last hurdle.
I have a pool of x2go servers running (that work fine individually); and listed in a pool in x2gobroker-sessionprofiles.conf (They do require an ssh proxy, which I specified in the sessionprofiles)
I have a central pgsql db successfully recording sessions for the x2go servers.
On the broker server, from the command line:
- using x2gobroker-testauth succeeds
- the load balancer seems to be working fine
- command line running x2gobroker --task listsessions shows the session configured in x2gobroker-sessionprofiles.conf
I have the x2gobroker-wsgi set up as a virtualhost. With debugging turned on, and most authentication disabled (so I'm expecting to have to log in first to the broker multiple times), I can visit in a browser to
https://broker.my.domain/plain/ (also to .../plain/inifile )
and it just says "Access granted".
If I use x2goclient, I try
x2goclient --broker-url=https://broker.my.domain/plain --debug
In x2goclient I then get a login screen, followed by a pop-up error message: "Host requires authentication"; the debug messages say: Broker HTTP request failed with error: "Host requires authentication"
The apache log file just shows successful connections.
I was expecting to get a choice among the pool of servers...
I feel like I am missing something small but critical.
--
Gilbert Laycock GnuPG key: 35B6A094 gilbert@laycock.org.uk http://www.laycock.org.uk/