No Machine stopped after launching EC2 instance into new VPC - solved
The Error
If you get this error from your No Machine Client Desktop
NX> 500 Authentication failed
NX> 500 Remote host identification has changed
NX> 500 Offending key in /usr/NX/home/nx/.ssh/known_hosts
NX> 999 Bye.
NX> 280 Exiting on signal: 15
NX> 500 Remote host identification has changed
NX> 500 Offending key in /usr/NX/home/nx/.ssh/known_hosts
NX> 999 Bye.
NX> 280 Exiting on signal: 15
Solution
I solved this by doing:
Find file usr/NX/home/nx/.ssh/known_hosts which includes old keys used by your ssh daemon. Remove your old key(s) by commenting out the lines.
Create new connection into host using No Machine Wizard.
Thanks to this post
Comments
Post a Comment