Is sshd running on the server side?
There is a way to purge the old settings in ~/.ssh/know_hosts client side, how I don’t know.
I remove this file (I don’t have that many ssh connections)
on the host to which you send a request.
Systemd is listening the requests on port 22 through this socket. If needed, it launches sshd. When the connexion is closed, sshd is stopped.
Without knowing exactly what to do I decided to experiment the service sshd.socket because it was your first mention and because this was running at the laptop side, the one that was already accepting ssh.
I did,
systemctl enable sshd.socket
systemctl start sshd.socket
Then I checked for sshd.socket and it was OK and the ssh from laptop to the desktop was possible.
I’m still wondering how sshd.socket got stopped at first place, if sshd.socket will be started next boot and what, if any, are the vulnerabilities of having sshd.socket running in all OMV 3.0 installations.
guarantees that sshd.socket will start at next boot? If so, there is something wrong in the desktop side since I had to restart sshd.socket after boot. What could be wrong?
I don’t really know.But as the hosts were upgraded from 2014.2, I imagine that there was not exactly the same config in both. You could check the hypothesis from an eventual backup.
The update 2014.2 => 3.0 was done in both computers but only the last one, the desktop, seems not to start sshd.socket at boot. Anyway, I still have to confirm the problem …