Unable to Connect because Specified Key cannot be loaded

ThinLinc
,
1

After updating my ThinLink client I cannot connect to my AWS server using ThinLink. I’m getting an error message that the specified key cannot be loaded. Has anyone experienced this problem? If so, how do I fix this problem?
Thanks in advance for any guidance provided.
Alan

2

Hello @alanjs5924

That error is a bit generic and doesn’t really tell much what is wrong with the key.
1.Are you able to logon with this key with ssh from the command line ?

ssh -i /path/to/private.key user@host

2.What version of ThinLinc did you upgrade from, and what version are you running now.?
3.Which client operating system are you using?
4.Did that key work before the upgrade, or has there been more changes made other than just upgrading the client.
5. Could you invoke the client in debug mode and try to connect, then share the log file with me?
From command line:

tlclient -d5
Then produce the error and attach/share the ThinLinc client log file

Kind regards,
Martin

3

Martin,
Thank you for your reply. Here’s what I get when I tried to logon from a command line (1).
C:\Users\alanj\Downloads>ssh -i keypair-ajs.pem bbj@ec2-3-19-48-91.us-east-2.compute.amazonaws.com
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions for ‘keypair-ajs.pem’ are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
Load key “keypair-ajs.pem”: bad permissions
bbj@ec2-3-19-48-91.us-east-2.compute.amazonaws.com: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
2. I’m not sure what version of ThinLinc I was on before the upgrade. I know it was initially installed back in 2019.
3. I’m trying to launch the client on my Windows 10 laptop.
4. Yes, the key did work before the upgrade.

4

I was able to successfully launch ThinLinc using another keypair.
Thanks for your help.
Alan

5

Hello @alanjs5924

Happy to hear that you managed to work around it. It seems like the problem was not related to ThinLinc, but has to do with permissions on your .pem key being too open.

Kind regards,
Martin