Forum Replies Created
June 4, 2014 at 09:27 in reply to: Unable to add nodes NX protocol – Cannot authenticate #3800
if it is possible, can you send to us the previous pair of keys? We would like to investigate further in order to prevent a similar situation arising in the future.June 3, 2014 at 15:49 in reply to: Unable to add nodes NX protocol – Cannot authenticate #3793
Hello, we suspect that problem is related to authorization on the remote node with the public key
Can you please check if the issue persists also when you generate a new pair of keys?
Rename the original keys to preserve them:
and generate a new key-pair by running on the server host:
# export LD_LIBRARY_PATH=/usr/NX/lib
# /usr/NX/bin/nxkeygen -k /usr/NX/etc/keys/node.localhost.id_dsa -p /usr/NX/etc/keys/node.localhost.id_dsa.pub -t dsa
Ensure that the new keys have proper permissions and ownership
and update the node:
# /usr/NX/bin/nxserver –nodeupdate <node>
Instructions are available also here:
- This reply was modified 6 years, 8 months ago by Haven.
Hello, thank you for reporting this issue.
We have just inserted a new Trouble Report
To investigate it further we will require the full set of logs:
from both servers: main and remote node.
From what you have written, we can see that a connection to the remote node with protocol NX is created, but it is then lost. The host certificate on the client side cannot be read, and the server cannot see the client version.
Please check your firewall setting if connection on 4000 port is somehow being filtered or blocked.
nxserver –list is the command to use in order to see the sessions on all remote nodes.
Please send us both /usr/NX/var/ directories from the main server and from the server node where session was created and not reported to main server.
Submit them here or send to issues[at]nomachine[dot]com