Hi guys,

 

We just discovered a x2go bug today, that matches the description of this topic. I don't know whether it has already been reported, I found bugreports with the same error message, but no report described the same cause as it was in our case.

 

Symptom: When several users wanted to make a connection to the x2go server, all of them received the error message "The remote proxy closed the connection while negotiating the session. Thsi may be due to the wrong auithentication credentials passed to the server."

We don't use a proxy, so the error message is somewhat strange.

Analysis: We noticed the x2go tries to make a connection to port 30009, in the logs we found: "sshd[45829]: error: connect_to localhost port 30009: failed.". When we check with netstat, there was an unrelated, normal ssh process sitting on that given port. What is strange that the port 30009 was the source port of the ssh connection ...

Solution, we closed the ssh connection blocking port 30009, and then x2go worked again.

 

So, it seems that x2go checks whether port 30009 (no matter if it is a source or destination port) is occupied, and if yes it thinks that there is some x2go related process is sitting on it.

 

x2go-client version: 4.0.5.0 (windows)

x2go-server packages:

$ rpm -qa | grep x2go
x2goserver-4.0.1.18-5.el6.x86_64
x2goserver-xsession-4.0.1.18-5.el6.x86_64
x2goagent-3.5.0.27-1.el6.x86_64
 

Cheers,

Swizzly