[X2go-dev] remote proxy closed the connection

Gerry Reno greno at verizon.net
Thu Feb 3 03:35:24 CET 2011


I'm seeing the following errors trying to connect to a new machine
running server version 3.0.99 using the browser client:

Feb  3 02:20:33 newmachine su[16393]: pam_unix(su:session): session
opened for user ubuntu by (uid=0)
Feb  3 02:20:33 newmachine sudo:   ubuntu : TTY=unknown ; PWD=/ ;
USER=root ; COMMAND=/usr/bin/touch /root/firstlogin_done
Feb  3 02:20:33 newmachine sshd[16319]: Accepted publickey for ubuntu
from XXX.XXX.XXX.XXX port 51610 ssh2
Feb  3 02:20:33 newmachine sshd[16319]: pam_unix(sshd:session): session
opened for user ubuntu by (uid=0)
Feb  3 02:20:33 newmachine sshd[16320]: Accepted publickey for ubuntu
from XXX.XXX.XXX.XXX port 51609 ssh2
Feb  3 02:20:33 newmachine sshd[16320]: pam_unix(sshd:session): session
opened for user ubuntu by (uid=0)
Feb  3 02:20:33 newmachine sshd[16441]: error: bind: Address already in use
Feb  3 02:20:33 newmachine sshd[16441]: error:
channel_setup_fwd_listener: cannot listen to port: 30008
Feb  3 02:20:33 newmachine sshd[16234]: pam_unix(sshd:session): session
closed for user ubuntu
Feb  3 02:20:33 newmachine su[16393]: pam_unix(su:session): session
closed for user ubuntu
Feb  3 02:20:33 newmachine sshd[16524]: error: connect_to localhost port
30007: failed.
Feb  3 02:20:33 newmachine sshd[16232]: pam_unix(sshd:session): session
closed for user ubuntu
Feb  3 02:20:33 newmachine sshd[29561]: channel 2: open failed: connect
failed: Connection refused
Feb  3 02:20:33 newmachine sudo:   ubuntu : TTY=unknown ;
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/touch /root/firstlogin_done
Feb  3 02:20:33 newmachine sudo:   ubuntu : TTY=unknown ;
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/touch /root/firstlogin_done
Feb  3 02:20:33 newmachine sshd[16233]: pam_unix(sshd:session): session
closed for user ubuntu


The client reports:
    Resuming
    Aborting
    Error message appears:

    The remote proxy closed the connection while negotiating
    the session. This may be due to the wrong authentication
    credentials passed to the server.

    Finished

I ran a check for sessions and there is only one existing session.

I've triple-checked the credentials and logged in on command line using
them.


Regards,
Gerry







More information about the x2go-dev mailing list