qertset.blogg.se - Nx nomachine nx publickey authentication fail

#Nx nomachine nx publickey authentication fail install#
#Nx nomachine nx publickey authentication fail password#

#Nx nomachine nx publickey authentication fail install#

Install the client on your local machine.

Check if your user will work: sudo /usr/NX/bin/nxserver -usercheck ''youruser''.Restart services sudo /etc/init.d/ssh restart.It may be necessary to remove a line in SSH's your known host file for your user on the server, or remove it all together(reset it): sudo rm /home/$USER/.ssh/known_hosts.If you have restricted SSH with AllowUsers you need to add nx to the list: We can do this by editing SSH configuration: sudo vi /etc/ssh/sshd_config

#Nx nomachine nx publickey authentication fail password#

You might need to enable password login into SSH.Sudo mv /usr/NX/home/nx/.ssh/authorized_keys2 /usr/NX/home/nx/.ssh/authorized_keys -Īdditional Potential Steps for Consideration Sudo chmod 0644 /usr/NX/home/nx/.ssh/authorized_keys2 With the default Ubuntu SSH setting this is not neccessary, but someone might have changed it to e.g.: authorized_keys Sudo cp /usr/NX/home/nx/.ssh/authorized_keys2.tmp /usr/NX/home/nx/.ssh/authorized_keys2Ĭheck that the name conforms to the filename given in the /etc/ssh/sshd_config file.

Sudo rm /usr/NX/home/nx/.ssh/authorized_keys2 Sudo cp /usr/NX/home/nx/.ssh/authorized_keys2 /usr/NX/home/nx/.ssh/authorized_keys2.tmp Amazon ec2, then NX's hard link between authorized_keys2 and the default.id_dsa.key will create problems when bundling AMIs.

Change the owner of the nx user public key on the server sudo chown nx:root /usr/NX/home/nx/.ssh/authorized_keys2.

Regenerate new SSH key for NX user as the default is common for all others sudo /usr/NX/bin/nxserver -keygen.

First copy it, otherwise it will be deleted after the importation). WARNING: Don't directly import the file /usr/NX/etc/keys _dsa.pub.

Import localhost key sudo cp /usr/NX/etc/keys/_dsa.pub /tmp/_.

This is OK, but if you want added security, generate your own unique key as follows.Ĭaveat: You'll have to modify your NX client wherever you're connecting from to use the custom key.

Install the packages all at the same time: client, node, server sudo dpkg -i nxnode_3.5.0-3_b nxserver_3.5.0-4_b nxclient_3.5.0-7_bīy default, the SSH key is a shared key amongst all NX clients.

Launch Ubuntu desktop or the server edition and install ubuntu-desktop sudo aptitude install ubuntu-desktopĭownload the Nomachine NX packages for Ubuntu ( ) (versions as of ) wget.

Setting up Nomachine NX packages on Ubuntu is now quite easy:

Additional Potential Steps for Considerationīeware that the following packages are not free but if you're facing problems with the freeNX packages, it may be a good solution:.