On Sun, 2012-07-29 at 13:15 -0400, senrabdet@aol.com wrote:

To Whom It May Concern:

We are trying to get x2go to work with a Vserver instance but cannot connect. We've done some looking at x2go posts into the error, but we're not sure the responses apply to using Vserver and are still looking for some help (apologies if we should have been able to find this on our own).

The error is first:

"X2go-51 The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication credentials passed to the server." The window includes an "OK" button.

If we press the OK button, we get to the x2go login screen where you can enter a password...if we enter the password, we get:

"Error Connection failed channel_open_session failed - Writing packet: error on socket (or connection closed): Broken pipe."

On the client, in the "sessions" file we see:

Loop: PANIC! The remote NX Proxy closed the connection. Loop: PANIC! Failure negotiating the session in stage '7'. Loop: PANIC! Wrong version or invalid session authentication cookie.

In both the client "options" file, the cookie looks to be the same as the cookie in the server

FYI - we can ping the Vserver instance, and we can ssh into the Vserver successfully, ping 8.8.8.8 from there etc. Also, initially when this wouldn't work, we though maybe we had issues with how we had set up desktops in the Vserver (which is still possible: we're using gnome, gdm) but when we spun up another Vserver and set up VNC, it serves the desktop correctly so at first blush this seems to be a networking/ports/firewall/sshd/routing type of issue.

However, we're still having trouble getting a regular X session to run over SSH.....but are assuming at the moment (possibly incorrectly) that the X2go errors we're getting are an issue on their own, possibly in addition to running an X session on a Vserver. <snip> If you are having problems running X over SSH, you probably won't be able to run X2Go - at least that's my guess. Is your /etc/ssh/sshd_config set up to allow X? You may wish to try the following settings:

X11Forwarding yes X11DisplayOffset 10 X11UseLocalhost no

Good luck - John