May 17, 2019 at 08:25 #22350
After a recent update on Linux Ubuntu 18.04 LTS, I am no longer able to connect to my machine via NoMachine. Or rather, I can connect but am instantly disconnected. It is an error 54 on my iPhone and an error 111 on my Chromebook running the Android client. I have attached log files for the client (session) and the server (nxd…). Please advise.
Thank you!May 17, 2019 at 08:33 #22354
Hello, what NoMachine product and version are you connecting to on the server side?
Any logs can be sent to forum[at]nomachine[dot]com making sure you reference the title of your topic in the subject.May 21, 2019 at 16:27 #22402
The logs didn’t reveal much. Can you tell us the server-side version of NoMachine you are connecting to?
Also, do you see the desktop, even for a moment, before you get disconnected?
Server-side logs with debug enabled are useful. Please follow the instructions here in order to enable them, making sure you reproduce the problem before gathering up the logs.May 27, 2019 at 07:53 #22435
I forwarded logs as described for the server. I did update to 6.7.6, but no change. Connect, no screen, attempted reconnect, and then a disconnect error message. On the server side, I do see my client user connecting twice, though neither time was for more than a fraction of a second.May 29, 2019 at 11:21 #22467
we received the logs but unfortunately you enabled them when some of the processes were already running. So I have to ask you to restart the nxserver reproduce and send logs again (restart can be achieved by executing /usr/NX/bin/nxserver –restart). Thanks!May 30, 2019 at 08:04 #22477
Thank you. I restarted the server as directed and duplicated the issue. Hopefully the logs I sent will be more helpful. I do appreciate the time you are spending to help me figure this out!May 30, 2019 at 11:29 #22487
Hi, thanks for the new set of logs.
They show us that there is a sudden termination of nxnode upon connection, but unfortunately they don’t provide useful hints as to why that is happening. So, I need to ask you to send us some additional information.
Please check for core files and then send us a backtrace (after having reproduced the problem again). To do that, follow the instructions here: https://www.nomachine.com/AR09L00810
You can attach the files and send them to us directly as you did last time. Thanks for your collaboration 🙂May 31, 2019 at 08:17 #22499
Thank you. I have forwarded outputs for both the node and server bin files. Crossing my fingers this proves helpful!June 3, 2019 at 11:55 #22533pellisukParticipant
I have the same problem, the connection was working last week, updated NoMachine on the target machine this morning and now just get ‘Connection reset by peer’. Would it be useful to you to have my logs too?June 4, 2019 at 09:32 #22546
@pellisuk can you send system (
/var/log/syslog) and NoMachine logs to forum[at]nomachine[dot]com? Please enable debug, restart nxserver (
sudo /usr/NX/bin/nxserver –restart) before you reproduce problem. Instructions about debug and collecting logs you can find here: https://www.nomachine.com/DT07M00098#1.
@dlp_1 can you send just the
We would also like to send a debug library with further instructions which would eventually help us with the investigation. Let us know if you’re interested.June 5, 2019 at 11:52 #22559
I have sent the syslog and am interested in figuring out what is going on with my rig. Currently I am approximating remote access with AnyDesk and sorely miss the speed, simplicity, and utility of NoMachine across my devices! 🙂June 14, 2019 at 15:34 #22666June 14, 2019 at 22:22 #22669
Yes, thank you. I did get the file, but have not had time to gather logs. I will spend some time on it this weekend. Thank you for your attention!August 7, 2019 at 12:29 #23225
@dlp_1 at the beginning of July we sent you a link to download a patched package. Can you confirm that the issue is now fixed?October 7, 2019 at 12:42 #23898
All users are invited to update the latest version.
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.