Hi Mike,

-----Original Message----- From: Mike Gabriel [mailto:mike.gabriel@das-netzwerkteam.de] Sent: Samstag, 22. November 2014 15:16 To: Herbst, Sebastian Cc: x2go-dev@lists.x2go.org Subject: Re: [X2Go-Dev] Failure negotiating the session in stage '7'

Hi Sebastian,

On Fr 21 Nov 2014 18:54:14 CET, Herbst, Sebastian wrote:

...

HI all,

thank you for your work on x2go. It is a great tool.

Unfortunately there is one single server. I can't connect to. It is installed just like another one (same packages different hardware), that is working, so it surely's got all necessary packages. XForwarding over ssh is working. As my other machines work well with each other, I am positive that this is an issue on the server.

I tried to debug this, by increasing the log level on the server, but nothing suspicious showed up.

The only hint is the client output: "Error: Failure negotiating the session in stage '7'. Error: Wrong version or invalid session authentication cookie." However none of the hints I googled worked for me.

Also in IRC nobody was able to help me.

I don't how to proceed. So I figured you could perhaps help me narrow down the problem. It is there any documentation describing the interaction of the server parts?

If this is the wrong list to ask, please excuse me.

Regards

Sebastian Herbst

Have you tried connecting from several client machines?

Could you try to remove /var/lib/x2go/x2go_sessions (make a backup first) and the run "sudo x2godbadmin --createdb"? Does that fix your issue? If it does, I'd like to see that x2go_sessions file.

Mike

Thanks, but this didn't do it. However, I was able to solve the issue, as I finally had some more time to look into it. It will explain the problem here, for the unlikely case, somebody else runs into it:

I had two entries in my /etc/hosts file that were named localhost, the usual 127.0.0.1 and an IP I added for testing some qemu stuff: 127.0.1.1. One part of the software expected a connection on 127.0.0.1 (hardcoded IP) whereas the other part tries to connect to localhost (by name), which was resolved as 127.0.1.1. Or maybe it was the other way round. Obviously this could not work and so it failed with this rather unhelpful error message.

Best regards

Sebastian