I'm using x2go server 4.0.1.20 with nxagent 3.5.0.32 on OpenSuse tumbleweed.
I login with x2go client 4.1.2.2 on Windows 10.
With User 'B' I can connect fine and the XCFE seesion is started properly.
With User 'A' I get an error on the client: "The remote proxy closed the connection while negotiating the session. This may be due to wrong authentication credentials passed to the server."
On the server the session.log is:
Info: Agent running with pid '17266'. Session: Starting session at 'Fri Mar 20 13:38:52 2020'. Info: Proxy running in server mode with pid '17266'. Info: Waiting for connection from 'localhost' on port '30958'. Info: Aborting the procedure due to signal '1'. Error: Aborting session with 'Unable to open display 'nx/nx,options=/tmp/.x2go-hbs/C-hbs-58-15 84707931_stDXFCE_dp32/options:58''. Session: Aborting session at 'Fri Mar 20 13:39:52 2020'. Session: Session aborted at 'Fri Mar 20 13:39:52 2020'.
Both user use the identical x2go session settings on the client and I tried both passwort and ssh key authentication for user 'A'. The password is working fine as I can login as user 'A' with a ssh client (Bitvise). What are possible causes that the two users behave diffently? I tried identical .profile files for both users but this did not help.
Any tips? Thanks
Henrik
A few things to check:
- does the user's profile print anything to stdout or stderr during login?
- does the user have access to /tmp/.x2go-hbs (check ownership/permissions)
- does the user have access to ~/.x2go/* (check ownership/permissions)
Uli
On Fri, Mar 20, 2020 at 1:51 PM Henrik Schmidt <hbs@informatik.uni-kiel.de> wrote:
I'm using x2go server 4.0.1.20 with nxagent 3.5.0.32 on OpenSuse tumbleweed.
I login with x2go client 4.1.2.2 on Windows 10.
With User 'B' I can connect fine and the XCFE seesion is started properly.
With User 'A' I get an error on the client: "The remote proxy closed the connection while negotiating the session. This may be due to wrong authentication credentials passed to the server."
On the server the session.log is:
Info: Agent running with pid '17266'. Session: Starting session at 'Fri Mar 20 13:38:52 2020'. Info: Proxy running in server mode with pid '17266'. Info: Waiting for connection from 'localhost' on port '30958'. Info: Aborting the procedure due to signal '1'. Error: Aborting session with 'Unable to open display 'nx/nx,options=/tmp/.x2go-hbs/C-hbs-58-15 84707931_stDXFCE_dp32/options:58''. Session: Aborting session at 'Fri Mar 20 13:39:52 2020'. Session: Session aborted at 'Fri Mar 20 13:39:52 2020'.
Both user use the identical x2go session settings on the client and I tried both passwort and ssh key authentication for user 'A'. The password is working fine as I can login as user 'A' with a ssh client (Bitvise). What are possible causes that the two users behave diffently? I tried identical .profile files for both users but this did not help.
Any tips? Thanks
Henrik
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Am 20.03.2020 um 14:22 schrieb Ulrich Sibiller:
A few things to check:
- does the user's profile print anything to stdout or stderr during login? No.
- does the user have access to /tmp/.x2go-hbs (check ownership/permissions) Yes. Lots of subfolders for each failed sessions are located there like C-hbs-52-1584706777_stDXFCE_dp32
- does the user have access to ~/.x2go/* (check ownership/permissions) Yes. Links to the/tmp/.x2go-hbs session folders and an empty ssh folder are located there.
Uli
On Fri, Mar 20, 2020 at 1:51 PM Henrik Schmidt <hbs@informatik.uni-kiel.de> wrote:
I'm using x2go server 4.0.1.20 with nxagent 3.5.0.32 on OpenSuse tumbleweed.
I login with x2go client 4.1.2.2 on Windows 10.
With User 'B' I can connect fine and the XCFE seesion is started properly.
With User 'A' I get an error on the client: "The remote proxy closed the connection while negotiating the session. This may be due to wrong authentication credentials passed to the server."
On the server the session.log is:
Info: Agent running with pid '17266'. Session: Starting session at 'Fri Mar 20 13:38:52 2020'. Info: Proxy running in server mode with pid '17266'. Info: Waiting for connection from 'localhost' on port '30958'. Info: Aborting the procedure due to signal '1'. Error: Aborting session with 'Unable to open display 'nx/nx,options=/tmp/.x2go-hbs/C-hbs-58-15 84707931_stDXFCE_dp32/options:58''. Session: Aborting session at 'Fri Mar 20 13:39:52 2020'. Session: Session aborted at 'Fri Mar 20 13:39:52 2020'.
Both user use the identical x2go session settings on the client and I tried both passwort and ssh key authentication for user 'A'. The password is working fine as I can login as user 'A' with a ssh client (Bitvise). What are possible causes that the two users behave diffently? I tried identical .profile files for both users but this did not help.
Any tips? Thanks
Henrik
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Does it work with a fresh user?
On Fri, Mar 20, 2020 at 2:39 PM Henrik Schmidt <hbs@informatik.uni-kiel.de> wrote:
Am 20.03.2020 um 14:22 schrieb Ulrich Sibiller:
A few things to check:
- does the user's profile print anything to stdout or stderr during login? No.
- does the user have access to /tmp/.x2go-hbs (check ownership/permissions) Yes. Lots of subfolders for each failed sessions are located there like C-hbs-52-1584706777_stDXFCE_dp32
- does the user have access to ~/.x2go/* (check ownership/permissions) Yes. Links to the/tmp/.x2go-hbs session folders and an empty ssh folder are located there.
Uli
On Fri, Mar 20, 2020 at 1:51 PM Henrik Schmidt <hbs@informatik.uni-kiel.de> wrote:
I'm using x2go server 4.0.1.20 with nxagent 3.5.0.32 on OpenSuse tumbleweed.
I login with x2go client 4.1.2.2 on Windows 10.
With User 'B' I can connect fine and the XCFE seesion is started properly.
With User 'A' I get an error on the client: "The remote proxy closed the connection while negotiating the session. This may be due to wrong authentication credentials passed to the server."
On the server the session.log is:
Info: Agent running with pid '17266'. Session: Starting session at 'Fri Mar 20 13:38:52 2020'. Info: Proxy running in server mode with pid '17266'. Info: Waiting for connection from 'localhost' on port '30958'. Info: Aborting the procedure due to signal '1'. Error: Aborting session with 'Unable to open display 'nx/nx,options=/tmp/.x2go-hbs/C-hbs-58-15 84707931_stDXFCE_dp32/options:58''. Session: Aborting session at 'Fri Mar 20 13:39:52 2020'. Session: Session aborted at 'Fri Mar 20 13:39:52 2020'.
Both user use the identical x2go session settings on the client and I tried both passwort and ssh key authentication for user 'A'. The password is working fine as I can login as user 'A' with a ssh client (Bitvise). What are possible causes that the two users behave diffently? I tried identical .profile files for both users but this did not help.
Any tips? Thanks
Henrik
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Yes, a fresh user does work. Therefore I'm curious which user properties can cause this kind of problem. I noticed that some LD_LIBRARY_PATH settings can screw x2go, therefore I used a default .profile for the problematic user.
Can it be some of that users local ssh settings?
Am 20.03.2020 um 15:17 schrieb Ulrich Sibiller:
Does it work with a fresh user?
On Fri, Mar 20, 2020 at 2:39 PM Henrik Schmidt <hbs@informatik.uni-kiel.de> wrote:
Am 20.03.2020 um 14:22 schrieb Ulrich Sibiller:
A few things to check:
- does the user's profile print anything to stdout or stderr during login? No.
- does the user have access to /tmp/.x2go-hbs (check ownership/permissions) Yes. Lots of subfolders for each failed sessions are located there like C-hbs-52-1584706777_stDXFCE_dp32
- does the user have access to ~/.x2go/* (check ownership/permissions) Yes. Links to the/tmp/.x2go-hbs session folders and an empty ssh folder are located there. Uli
On Fri, Mar 20, 2020 at 1:51 PM Henrik Schmidt <hbs@informatik.uni-kiel.de> wrote:
I'm using x2go server 4.0.1.20 with nxagent 3.5.0.32 on OpenSuse tumbleweed.
I login with x2go client 4.1.2.2 on Windows 10.
With User 'B' I can connect fine and the XCFE seesion is started properly.
With User 'A' I get an error on the client: "The remote proxy closed the connection while negotiating the session. This may be due to wrong authentication credentials passed to the server."
On the server the session.log is:
Info: Agent running with pid '17266'. Session: Starting session at 'Fri Mar 20 13:38:52 2020'. Info: Proxy running in server mode with pid '17266'. Info: Waiting for connection from 'localhost' on port '30958'. Info: Aborting the procedure due to signal '1'. Error: Aborting session with 'Unable to open display 'nx/nx,options=/tmp/.x2go-hbs/C-hbs-58-15 84707931_stDXFCE_dp32/options:58''. Session: Aborting session at 'Fri Mar 20 13:39:52 2020'. Session: Session aborted at 'Fri Mar 20 13:39:52 2020'.
Both user use the identical x2go session settings on the client and I tried both passwort and ssh key authentication for user 'A'. The password is working fine as I can login as user 'A' with a ssh client (Bitvise). What are possible causes that the two users behave diffently? I tried identical .profile files for both users but this did not help.
Any tips? Thanks
Henrik
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Hi Henrik,
On Sa 21 Mär 2020 10:08:54 CET, Henrik Schmidt wrote:
Yes, a fresh user does work. Therefore I'm curious which user
properties can cause this kind of problem. I noticed that some LD_LIBRARY_PATH settings can screw x2go,
therefore I used a default .profile for the problematic user.Can it be some of that users local ssh settings?
Hmmm... Does the same error occur with the same server-side user
account when connecting from a Linux machine?
If so, could you install pyhoca-cli (from packages.x2go.org) and run
pyhoca-cli --server <server> --user <user> --command XFCE --libdebug
and send the complete debug output (maybe not to the list..)? I will
reply to your mail and re-Cc: the list with feedback.
Mike
DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
-
Henrik Schmidt -
Mike Gabriel -
Ulrich Sibiller