Forum / NoMachine for Windows / NX key authentication – cannot make it work
- This topic has 2 replies, 2 voices, and was last updated 5 years, 8 months ago by shiba.
-
AuthorPosts
-
February 28, 2019 at 10:58 #21608maximnParticipant
hello, I am using last version 6.5.6 (free) on Windows. i followed this guide to enable nx key based authentication https://www.nomachine.com/AR02L00785
For some reason it is not working – all i have, just a message “authentication error” on client and “Public key not recognized” in server logs
here are my files:
1. c:\Users\nx\.nx\config\authorized.crt
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCf6vK6aZoFlYMJUiMI68hyraC4XzF9pA8aVLVOEFGaYnmPK2cnxDd1cwLkVkzdLSzR3GK0vLgxFgaUrU8NYQny5GDhtz4wgEDexgEksm/bZLJKNX5CCqrNgnYVAG5X1Vg0T+M6+YechHIOXIFggcDcMvcVBcuP2fc0omsA1u/LJUoX+F6vqIzn2wwUh0Oe5oSbJ6qnXKpZMkmVzNmsK9fdOjBwPLUjw3yUcZiM9fNcIaRuUE0whnUcF/Kes5QaRtg6pqtf224yLJveHzUmZj06ZqTFXtfxdgO3MHV5vh0V2yK0SBHYQakRSWHMxRQRyfd0CyVeROZyoFkfJX3CHeSR
2. on client there is key file
—–BEGIN OPENSSH PRIVATE KEY—–
b3BlbnNzaC1rZXktdjEAAAAABG5vbmUAAAAEbm9uZQAAAAAAAAABAAABFwAAAAdzc2gtcn
NhAAAAAwEAAQAAAQEAn+ryummaBZWDCVIjCOvIcq2guF8xfaQPGlS1ThBRmmJ5jytnJ8Q3
dXMC5FZM3S0s0dxitLy4MRYGlK1PDWEJ8uRg4bc+MIBA3sYBJLJv22SySjV+QgqqzYJ2FQ
BuV9VYNE/jOvmHnIRyDlyBYIHA3DL3FQXLj9n3NKJrANbvyyVKF/her6iM59sMFIdDnuaE
myeqp1yqWTJJlczZrCvX3TowcDy1I8N8lHGYjPXzXCGkblBNMIZ1HBfynrOUGkbYOqarX9
tuMiyb3h81JmY9OmakxV7X8XYDtzB1eb4dFdsitEgR2EGpEUlhzMUUEcn3dAslXkTmcqBZ
HyV9wh3kkQAAA9BUISj9VCEo/QAAAAdzc2gtcnNhAAABAQCf6vK6aZoFlYMJUiMI68hyra
C4XzF9pA8aVLVOEFGaYnmPK2cnxDd1cwLkVkzdLSzR3GK0vLgxFgaUrU8NYQny5GDhtz4w
gEDexgEksm/bZLJKNX5CCqrNgnYVAG5X1Vg0T+M6+YechHIOXIFggcDcMvcVBcuP2fc0om
sA1u/LJUoX+F6vqIzn2wwUh0Oe5oSbJ6qnXKpZMkmVzNmsK9fdOjBwPLUjw3yUcZiM9fNc
IaRuUE0whnUcF/Kes5QaRtg6pqtf224yLJveHzUmZj06ZqTFXtfxdgO3MHV5vh0V2yK0SB
HYQakRSWHMxRQRyfd0CyVeROZyoFkfJX3CHeSRAAAAAwEAAQAAAQByDuoWyPEA4JV4VWwF
ld3+5RXHyqWK3jOjbR1vUzZQrcHTuno1o76Gd4RthZwG+IyKFe0UybF52SLSchX7DeZBpl
/vPXoOr7sU6RaxrM8ZJOYBBcxKoD8Ymt9LtWX+IX1qujvwuT7fBJww4Auq4IDEzVjrVpnM
vQKTOPCmxaZ8NbjKEJb9ud0S6MoRihR1LxgdrquDJKtdNYBKhXAI8eCzwvdDzqdqCmMuzT
/w6U3OsqNCD9UYU6gNtUEGJ3MHPYQEgdCqzJRBzSTJg6UlTwMKut3NqfMHaHZ0biDC5dN2
wLw1s1aXiaqrcJ48k5YgFrgsaShDVfsI39s5XE+xzCDBAAAAgDCs9TDVGFVwBw+GurkSRP
8f7I93mYdinvauEML0hIupMUYDA6rKFlNG6P1ymI85aYj7kbTOl0keSHgg5fIf1+TM3SIX
RNhmySeMxONyM6uBTZ37qDTCvcBjlIuB5zoGTqAl+84ZaePsBEqqjPkfpJfFakRQSR0k6r
cboCtEx5HNAAAAgQDN+rYMQcdLttT/Kz/IRnVX5sAY29e3/mZe6x1Ghvine4izuXXXQruN
boEw6B/vbF8xpo4lSTrAfoqICuEYZ27CdE78G0lbETwrhVaWq1Y7dOjz2aZpGWiy6LBfPP
UYTU4+Fkd2Xqdg9SratHGye9RRPdWS0iQoeW/emo5PiFB+mQAAAIEAxsCwWYZ+RNRNi0vq
L2+qfiJj0+wgfqdE7D/YxfvjpulauAGuz8RgsHMC102YbOHUaZCHwwgf8E36m50zh8KXne
NyaQZsrHQvB4uk2MUj6FPuUrkgpXj+p7ZfPeDIkU7tTPJvPHcFjcM8Q0Z5TGR7wG2jQHK2
5AsJ6SWvt1SOqLkAAAAVcm9vdEBpcC0xNzItMzEtMjItMTY4AQIDBAUG
—–END OPENSSH PRIVATE KEY—–3. in server logs:
2019-02-28 12:22:37 077.790 6784 NXSERVER ERROR! Authentication with ‘NX-private-key’ from host ‘***’ failed. Error is ‘Public key not recognized’.
2019-02-28 12:38:04 884.857 6804 NXSERVER ERROR! Authentication with ‘NX-private-key’ from host ‘***’ failed. Error is ‘Public key not recognized’.
2019-02-28 12:38:06 066.925 7820 NXSERVER ERROR! Authentication with ‘NX-private-key’ from host ‘***’ failed. Error is ‘Public key not recognized’.February 28, 2019 at 16:22 #21615maximnParticipantokay, have it working after couple hours
1. if passphrase in the key file is empty, passphrase and username are never asked
2. authorized.crt must be not in “c:\users\nx\.nx\config”, but in the above users folder – “c:\users\username\.nx\config”
February 28, 2019 at 16:46 #21616shibaParticipantHello maximn,
Did you generate a new pair of keys? I ask because we have a Trouble Report for which the temporary workaround is to generate new keys
ssh-keygen -p -m PEM -f
Here is the TR: https://www.nomachine.com/TR02Q09140
Btw, we noticed that you are trying to connect as user account named “nx”. We don’t recommend it, because the nx account is needed to setup the initial stage of the client-server connection. Please use local account profiles.
-
AuthorPosts
This topic was marked as solved, you can't post.