Page 1 of 1

x2go connection issue

PostPosted: Dec 24th, '20, 17:21
by cmorning
I'm not sure if this is the correct forum to use, but I have tried searching others with no luck. Any suggestions where to turn to for help would be appreciated.

I just installed x2goclient and server on my mageia 7 systems. When I try to start a connection, I get an error message such as:

Connection failed. Cannot create remote file ~colin/.x2go/ssh/key.ttBlvN - SCP: Warning: status code 1 received: scp: ~colin/.x2go/ssh: No such file or directory


I feel there must be a simple solution to this. It is not a file permission problem, etc. as far as I can tell. The version I have installed (for the client) is
x2goclient-4.1.2.1-2.mga7
The server machine has the following installed
x2goserver-4.0.1.20-3.mga7

Re: x2go connection issue

PostPosted: Dec 24th, '20, 22:24
by doktor5000
Is x2go actually running on the system where you installed the server ? The output as root of
Code: Select all
systemctl status x2goserver.service -al -n250
would be helpful.

Re: x2go connection issue

PostPosted: Dec 25th, '20, 00:06
by cmorning
The output on the server system is as follows:

Code: Select all
x2goserver.service - X2Go session cleanup
   Loaded: loaded (/usr/lib/systemd/system/x2goserver.service; disabled; vendor preset: disabled)
   Active: active (running) since Thu 2020-12-24 16:56:56 EST; 40s ago
  Process: 17285 ExecStart=/usr/sbin/x2gocleansessions (code=exited, status=0/SUCCESS)
 Main PID: 17290 (x2gocleansessio)
    Tasks: 1 (limit: 4915)
   Memory: 13.2M
   CGroup: /system.slice/x2goserver.service
           ΓΆΓΆ17290 /usr/bin/perl /usr/sbin/x2gocleansessions

Re: x2go connection issue

PostPosted: Dec 25th, '20, 18:31
by doktor5000
Can you check the same again for the ssh server? As root
Code: Select all
systemctl status sshd.service -al -n250

And can you try to manually to connect to the x2go server box as a regular ssh client ?

From what I can tell, this might be occuring since a security update to ssh earlier this year.
Others mentioned that this should be fixed with x2go 4.1.2.2 although I don't know if this also needs an update of the server portion.
You might need to wait for someone else who's using x2go to see if they can confirm this issue.

See also https://bugs.debian.org/cgi-bin/bugrepo ... bug=947129