[X2Go-User] Can't access X2go through router

[Paul Borowicz]

Bill, could this be your problem?

https://wiki.x2go.org/doku.php/doc:faq:start

Known Issues

Can't login to x2goserver with an ECDSA key

Currently, older versions of the ssh library used by X2Go called libssh are
unable to work with ECDSA keys. However you may use an RSA key - if you
need to - or go with the SSH default authenticating method using the remote
user's password.

SSH Login issue

If you already use OpenSSH to get a shell on your x2go server, you may get
this message when trying to connect with x2go:

The host key for
this server was not found but an othertype of key exists. An attacker
might change the default server key to confuse your client into thinking
the key does not exist
This is related to the ECDSA host key (related to the previous FAQ entry -
although there is a subtle difference between host and client keys.) To
solve this issue, you can disable ECDSA keys on your OpenSSH server
configuration, by commenting the following line in /etc/ssh/sshd_config
file:

#HostKey /etc/ssh/ssh_host_ecdsa_key
Then restart the SSH service. Now you should not get the error message
anymore.
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] Can't access X2go through router

[Bill Damage]

The error is exactly as here: [X2Go-User] X2Go Client: Kex error : no match for 
method server host key alog: server [ssh-rsa], client [ssh-ed25519]

| 
| 
|  | 
[X2Go-User] X2Go Client: Kex error : no match for method server host key...


 |

 |

 |



However, I have some more information which suggest the server isn't the 
culprit.When I use the current Windows client on a LAN, I get in OK. When I use 
the same from linux on the LAN, I get in OK. It's only when i've tried to port 
forward 2249 -> 22 from the WAN that it fails with this message from either 
client. Even stranger, if I SSH in from the WAN on port 2249 I get in OK. So 
the usual suggestions of regenerating keys etc don't seem to help, even though 
I did that anyway.
Server I'm trying to access is Ubuntu 16.04.3 root@mojo:~# 
x2goversionx2goagent: 3.5.0.32x2goserver: 4.0.1.20x2goserver-extensions: 
4.0.1.20x2goserver-xsession: 4.0.1.20root@mojo:~#
Linux and Win clients are 4.1.0.0
Here's the last twist - this is a VM. I have also port forwarded 22 to 22 on 
the host, which is Fedora 26 and the main server actually running these VMs 
(KVM), and that lets me in via X2Go no problem. So the router itself can work 
if it's not going to a VM. I also tried disabling the firewall on the VM but 
still got no joy. At that point I knew I was plumb out of ideas so came here 
;-) Thanks.

___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user