Authentication fails after NoMachine replaces SSL certificate

[aakerberg]

Windows 10 NoMachine client (latest version) connecting to RHEL 9 linux server Gnome desktop (I believe running Enterprise Desktop).

Periodically when attempting to connect, a message pops up when attempting to connect to a certain server:   “Remote host identification has changed…. Do you want to proceed anyway and replace the old SSL certificate in the list of known hosts?”  (screenshot attached)

However, when I allow it to proceed.  I then get an “authentication failed” error.  From that point on, NoMachine will not connect to that server – AND I can no longer connect with any other method (have tried various SCP and SSH clients I have available to me)

I have tried updating to the latest version of the client as well as completely uninstalling and re-installing the Windows client.

The only thing that works is to wait some period of time – usually a few days – and after a few re-boots of the windows machine, NoMachine will once again give the me “Remote host identification has changed…”  message and then when I allow it to replace the SSL certificate this time, everything works again (including my other SSH and SCP clients) for a few days… until that message pops up again and the cycle starts all over again.

I am reasonably sure the Linux server identification has not actually changed.  No other users that connect to this server are having this issue.  The problem is unique to my Windows 10 machine.  It seems that for some reason, NoMachine thinks the SSL cert has changed, installs the wrong one which breaks everything… and then later puts the right one back in again.

 

Attachments:

1. 

   Host_identification_changed.png
   

[Author]

Posts