Ssh issues after os change

Hi,

Recently moved from windows 11 to kubuntu. I tried to ssh using my private key to my hestia server and kept getting a libcrypt error and wouldn’t connect.
Now my IP address seems to be blocked, how long hestia fail2ban settings ban an IP for.

This private key worked using ssh on windows but will not work on kubuntu. I have no hard console access either as contabo does not have a console.

Hi @cloudknight

If it’s the first time, 10 minutes.

I’m assuming that the path where the private key is located is /home/cloudknight/.ssh/ and the private key name is private-key (replace them by the actual path and key name)

What’s the ssh command you are using?
Where is located the private key?
What are the perms of that private key?

namei -mo /home/cloudknight/.ssh/private-key

Edit I wrote name instead of namei

What’s the type of private key?

head -n1 /home/cloudknight/.ssh/private-key

Hi sahsanu,
It’s been more then 10 minutes and I still cannot connect to ssh server now so my IP must be completly blocked.

my working directory is:

root@******-allseries:/home/*******/.ssh# ls
hestiacp  known_hosts
root@******-allseries:/home/******/.ssh#

type of key is:

root@*-allseries:/home//.ssh# head -n1 hestiacp
-----BEGIN OPENSSH PRIVATE KEY-----
root@-allseries:/home//.ssh#

permissions:

root@****-allseries:/home/*****/.ssh# ls -lash
total 16K
4.0K drwx------  2 ***** ***** 4.0K Feb 28 23:03 .
4.0K drwxr-x--- 16 ***** ****** 4.0K Feb 28 23:01 ..
4.0K -rw-------  1 **** *****  426 Feb 28 23:03 hestiacp
4.0K -rw-r--r--  1 ***** ****  142 Feb 28 22:47 known_hosts
root@*****-allseries:/home/*****/.ssh# 

I’m concerned I cannot connect now due ip block.

And the ssh command you are using?

Also, if we can’t solve it and you trust me, you could send me a private message with the private key and the ip of your server so I could try to connect (of course, you will have to change the key after that).

ssh -i hestiacp [email protected]

I have sent you a private message.

1 Like

For the record, the issue was that the private key file had Windows line endings. Once it was converted using the dos2unix command, it was able to connect without any problems.

1 Like

Like to say a big thank you to Sahsanu for helping with this.

2 Likes

And here’s my shiny new linux desktop:

I love Linux.