Here's a well-structured article that incorporates the key phrase 'nomachine server' and provides a detailed description of the issue:

Troubleshooting Nomachine Server with SSH vs NX

In recent days, we've encountered an unusual issue while attempting to connect to our nomachine server using the NX protocol. Despite setting up the configuration correctly, we were met with an error message stating that no public key was found, even though the authorized.crt file exists under /home/$user/.nx/config/.

To troubleshoot this issue, we decided to switch gears and try connecting via SSH instead of NX. Surprisingly, everything worked seamlessly when using SSH, indicating that the authorized_keys file under /home/$user/.ssh/ was correctly configured.

A closer inspection of the nxserver.log revealed an error message stating 'Wrong signature' when attempting to log in via PIN. This led us to suspect that there might be a discrepancy between the public key stored on our smartcard and the one being presented by the client.

To resolve this issue, we investigated further and discovered that the Activeclient library used to read the smartcard plugged into our laptop was not accurately extracting the public key associated with the smartcard. As a result, when the nomachine server tried to verify the signature of the public key, it failed due to the mismatch.

After verifying the contents of the authorized.crt file and ensuring that it matched the public key stored on our smartcard, we were able to successfully log in using PIN authentication via NX. This experience highlights the importance of carefully configuring both SSH and NX protocols when working with nomachine servers.

By taking a step back and re-examining our setup, we were able to identify the root cause of the issue and implement a solution that ensured seamless connectivity to our nomachine server.

Nomachine server