SSH problems since update to v1.6.2

Operating System ZimaOS
1

I updated ZimaOS to version 1.6.2 and since that I have been unable to SSH into it from my Fedora terminal. I get this:

Received disconnect from 192.168.0.50 port 22:2: Too many authentication failures
Disconnected from 192.168.0.50 port 22

and

ssh: connect to host 192.168.0.50 port 22: Connection refused

Since the latest update hardened SSH, I think it may have something to do with that.
I updated it a few days ago, and ran into this issue the very next day when I tried SSHing into it.
I can login to the ZImaOS Dashboard. The SSH toggle is turned ON.

I can ssh from Developer Mode > Web-based terminal though. The issue only happens from a normal terminal. how can I fix the above?

2

I had to turn off ssh on the zima box, reboot, then turn it back on, then flushed the key on the Linux machine so it would get a new client key, even though it didn’t give me a token error.

On my Ubuntu machine I executed ssh-keygen -R 192.168.1.50 being 192.168.1.50 was the zima box.

Then when I executed ssh on the ubuntu machine I got a new private key.

3

Hey, I was able to ssh again by using this option:

ssh -o IdentitiesOnly=yes user@192.168.0.50

I created an alias in .bashrc

4

I have the same issue, but after updating to v1.7.0. Previously it worked perfectly!

I can login with the user root and the password from the Developer Mode > Web-based terminal.

immagine
immagine530Ă—163 3.12 KB

If I try the same with SSH from Linux or Putty in Windows:

[~] # ssh root@192.168.0.31
root@192.168.0.31's password:
Permission denied, please try again.

The same with RabidRabbit suggestion:

[~] # ssh -o IdentitiesOnly=yes root@192.168.0.31
root@192.168.0.31's password:
Permission denied, please try again.

How can I fix that?

5

Just updated to v1.7. I can login normally to my user with my fix. I think there is a timeout though, so I gotta wait a bit to reconnect if end the ssh connection.

Do you run into the same issue when trying to login to a user account rather than root?
Maybe root logins are disabled in the new updates.

1 Like
6

Yep, they set PermitRootLogin to “no” with the update. Reverting to “yes” solved the problem.

7

This is a security-related fix. We believe that enabling root login by default poses some unnecessary security risks. Therefore, we have decided to disable it by default. We apologize for any inconvenience caused by this change.

8

It’s not an issue, but next time please make a sticky post here so it’s easier to find the solution especially because when you’re logging in there’s not a clear message that kicks you off, it seems the password is wrong but it is not :wink: