June 3, 2019 at 08:57 #22524
I have a NoMachine server on a Ubuntu 18.04 machine which I connected successfully several times with the client on my Windows 8 machine (both are Free 18.104.22.168). However, when I cut the connection either via killing the process on the client side or by switching the user on the server side, the connection stays on the server side.
When I check on the server side physically, I can see that NX server thinks that there still is a user logged in and doesn’t let me log in with the same user with the client. More curiously, nothing happens when I click the disconnect button on the server side and I could only let the server reset the users by killing and restarting the server.
While the server is in this state, connecting to the server with the same user is impossible. Instead of NoMachine taking the control of this existing user, it stays in the “connecting to xxx” screen after password validation if the password is correct. However, if the password is not correct (for the same user), it returns with a credential error. For a different user, it “waits for the desktop user to author…” since the other users are configured that way.
What can I do to prevent this from happening?June 5, 2019 at 12:21 #22569
Hi, this is a currently know issue https://www.nomachine.com/TR05Q09329.
We can send you a patched package for further testing. If you’re interested, please write to us at forum[at]nomachine[dot]com and we’ll send you a link.July 12, 2019 at 07:30 #22904
Was this resolved? I see the trouble ticket is still open. I have the same issue on an OpenSuse Leap server connected via Windows 10. Just wondering if there is a patch I missed somewhere…
Thanks!July 12, 2019 at 07:32 #22910
The patch hasn’t officially been released yet. See my reply above 😉July 22, 2019 at 13:33 #23005
Hi @britgirl can you send me the patched version? I will help you test in Ubuntu 16.04 and Ubuntu 18.04
Can you provide with info on which log files and dumps you would be interested in getting back from me?
Thanks!July 23, 2019 at 11:56 #23017
The patch has been sent to you by e-mail.
Please follow the standard procedure to gather logs from the server: https://www.nomachine.com/DT10O00163
To set debug level, please set
Then after the issue occurs upload the logs, and send them via e-mail.August 2, 2019 at 14:55 #23151
Hi Bilbotine, after installing the patch you provided I haven’t experienced again the problems to reconnect. The patch solved the problem!August 5, 2019 at 07:55 #23161
Hello, I have the same issue. Can you send the patch to me as well, please. For Ubuntu 64 bit.
Will I be able to install it, having only NoMachine access to the server?
SergeyAugust 6, 2019 at 15:41 #23210
Hello Sergey Slizovskiy,
Generally you can install a package with the patch having only NoMachine access.
If you are attached by NoMachine to physical session – the session is visible on physical screen. You can run terminal and install update package. You will be disconnected but after several minutes, when update finished you should be able connect again.
If you are not sure that you are running physical session or you are running virtual NoMachine session, you can install ‘screen’ program:
sudo apt update sudo apt install screen
then run screen session -> execute in terminal:
and in the screen session run NoMachine update:
sudo dpkg -i nomachine_6.7.6_41_amd64.deb
you will be disconnected, and after update finished you can connect by NoMachine again.
As safe as updating NoMachine is, there is a risk that something totally unexpected could happen. This could affect the possibility of connecting via NoMachine.August 7, 2019 at 11:16 #23221
Thank you, I have successfully installed a patch, but I am not in a position to intentionally test it until I am back from vacation.
You must be logged in to reply to this topic.