Hello, I follow this tutoriel https://wiki.x2go.org/doku.php/wiki:advanced:authentication:passwordless-ssh but it does not work. I'm on Ubunut 16.04.3 LTS with kernel 4.4.0-97-generic. When I make a ssh user@my.server.com it's ok, I reach my server and connect immediatly. But when I use X2GoClient then I have a message : "Connection refused". I put the path of my private key on the field path for the sessions. I don't understand. Where did I miss a step? Best regards.
-- Jean Tinguely Awais Stagiaire why! open computing SA Rte de Renens 4 CH-1008 Prilly Phone +41 21 661 22 22 <+41%2021%20661%2022%2022> Mobile +41 76 227 01 32 <+41%2076%20227%2001%2032> <https://whyopencomputing.ch> <https://whyopencomputing.ch/fr/home/237-fairphone2.html>
I use x2go on Ubuntu, passwordless login works. I use default key so I simply clicked "Try auto login (ssh-agent or default ssh key)". If you use different key, you are probably supposed to specify it (private part!) in the "Use RSA/DSA key for ssh connection" field. I don't see "field path for the sessions" anywhere. Try default key first or post some screenshots.
--
With Best Regards, Marat Khalili
On 18/10/17 11:14, Jean Tinguely wrote:
Hello, I follow this tutoriel https://wiki.x2go.org/doku.php/wiki:advanced:authentication:passwordless-ssh but it does not work. I'm on Ubunut 16.04.3 LTS with kernel 4.4.0-97-generic. When I make a ssh user@my.server.com <mailto:user@my.server.com> it's ok, I reach my server and connect immediatly. But when I use X2GoClient then I have a message : "Connection refused". I put the path of my private key on the field path for the sessions. I don't understand. Where did I miss a step? Best regards.
-- Jean Tinguely Awais Stagiaire why! open computing SA Rte de Renens 4 CH-1008 Prilly Phone +41 21 661 22 22 <tel:+41%2021%20661%2022%2022> Mobile +41 76 227 01 32 <tel:+41%2076%20227%2001%2032> <https://whyopencomputing.ch><https://whyopencomputing.ch/fr/home/237-fairphone2.html>
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
We solved this problem a while ago on IRC.
It boiled down to IPv6 connectivity problems (remote server advertised on AAAA record, on which the ssh daemon wasn't listening) - it wasn't an authentication failure in the first place. :)
Mihai