- This topic has 1 reply, 2 voices, and was last updated 1 year, 9 months ago by
.
-
Posts
-
Quite frequently I have to restart NoMachine servers via ssh in order to restore a connection that has been interrupted for some reason or other. Sometimes (not very often, I give you that) this is required even after a clean ending of a remote session. So much so, that I am actually thinking of scripting this to do a remote NoMachine server restart via ssh every time before I need to launch a NoMachine remote session.
Why is that so? Am I doing anything wrong?
Servers are on Ubuntu 22.10 boxes, latest NoMachine SW.
This is not something we have encountered in our labs. Testing on the fly we can confirm that on Ubuntu 22.10, everything works out of the box with default manufacturer settings, so we have not idea what you could be doing wrong.
What you didn’t mention is what desktop environment you have on these hosts, what display server is it (Wayland or Xorg?) and the typical steps to reproduce this problem. For example, you say that it happens when the connection has been interrupted for some reason or another: what is the reason for the “interruption”?
What errors, if any, does NoMachine show when you try to reconnect after this interruption?
Logs of the server side would also be useful so we can check what is happening. Follow the instructions in the document here and then send them to forum[at]nomachine[dot]com
https://kb.nomachine.com/DT11R00182. Make sure you enable debug first, reproduce the problem and then extract the logs.
Thank you.
Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.