- This topic has 1 reply, 2 voices, and was last updated 2 weeks, 3 days ago by
.
-
Posts
-
Hi,
I’m trying to run NoMachine in a docker container and to connect to it.My host is Ubuntu 22.04.5 LTS, container the same. Docker is 27.5.1-1. NoMachine in the container is 8.16.1-1 Workstation.
When I try to connect to NoMachine to a virtual display from a Windows 10, i get the following errors:
/usr/NX/var/log/nxserver.log:
…9989 9989 2025-03-05 21:29:03 642.806 NXSERVER Connected from remote machine ‘xxx.xxx.25.174’ using protocol ‘NX’.
Info: Handler started with pid 9989 on Wed Mar 5 21:29:03 2025.
Info: Handling connection from xxx.xxx.25.174 port 42330 on Wed Mar 5 21:29:03 2025.
9989 9989 2025-03-05 21:29:11 713.663 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –isadmin nomachine’ with pid ‘10020/10020’ finished with exit code 1 after 0,010 seconds.
9989 9989 2025-03-05 21:29:11 715.817 NXSERVER User ‘nomachine’ logged in from ‘xxx.xxx.25.174’ using authentication method NX-password.
9864 9864 21:29:11 820.337 Redis: 1 changes in 900 seconds. Saving….
9864 9864 2025-03-05 21:29:16 413.498 NXSERVER WARNING! Cannot retreive nxnode PID for virtual server FC0962656809D88FA46DC9A5EE70B169.
9989 9989 2025-03-05 21:29:16 414.192 NXSERVER ERROR! Cannot start node to create session
9864 9864 2025-03-05 21:29:16 414.897 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –node –user nomachine –priority realtime –mode 0 –pid 49’ with pid ‘10026/10026’ finished with exit code 1 after 0,009 seconds.
Info: Connection from xxx.xxx.25.174 port 42330 closed on Wed Mar 5 21:29:16 2025.
Info: Handler with pid 9989 terminated on Wed Mar 5 21:29:16 2025.
9989 9989 2025-03-05 21:29:16 441.400 NXSERVER Remote machine ‘xxx.xxx.25.174’ disconnected.
9989 9989 2025-03-05 21:29:16 441.761 HostDescriptorClose: WARNING! Descriptor FD#25 is invalid.
connection from the client says:
NX> 105 Listsession –status=”disconnected\054connected” –type=”all” –shadowable=”yes”
NX> 127 Session list of user ‘nomachine’:Display Type Session ID Services Depth Screensize Status Session name Username Platform Users Create Node
——- —- ———- ——– —– ———- —— ———— ——– ——– —– —— —-
NX> 148 Server capacity: not reached for user: nomachine
NX> 105 Setsession –type=”unix-xsession-default”
NX> 595 Server could not establish communication with local node.session:
Info: Starting NoMachine version 8.9.1.
Info: Loading settings from ‘D:\Users\bernd.lentes.SCIDOM\.nx\config\player.cfg’.
Info: Loaded translation files for ‘English’.
17608 20328 2025-03-05 22:29:04 171.455 Main: Creating the client session.
17608 20328 2025-03-05 22:29:04 171.455 ClientSession: Initializing session at 0x0000000003b13850.
17608 20328 2025-03-05 22:29:04 291.259 ClientSession: Initialized session at 0x0000000003b13850.
17608 20328 2025-03-05 22:29:04 294.260 ClientSession: Starting session at 0x0000000003b13850.
17608 20328 2025-03-05 22:29:04 297.261 ClientSession: Going to start session ‘D:\Users\bernd.lentes.SCIDOM\Documents\NoMachine\nomachine-desktop.nxs’.
17608 20328 2025-03-05 22:29:04 349.295 Connection: Initializing connection at 0x0000000006908900.
17608 20328 2025-03-05 22:29:04 354.431 Connection: Initialized connection at 0x0000000006908900.
17608 20328 2025-03-05 22:29:04 354.431 Connection: Starting connection at 0x0000000006908900.
17608 20328 2025-03-05 22:29:04 354.431 ClientDaemonConnector: Starting a new connection to host ‘bioinformatics-mcd-01.scidom.de’ on port ‘4020’.
17608 20328 2025-03-05 22:29:04 355.479 Connection: Started connection at 0x0000000006908900.
17608 20328 2025-03-05 22:29:04 367.489 ClientSession: Started session at 0x0000000003b13850.
Info: Connection to 146.107.25.27 port 4020 started at 22:29:04 369.488.
Info: Slave server running with pid 17652.
Info: Listening to slave connections on port 44520.
17608 20328 2025-03-05 22:29:04 377.616 Main: Entering the GUI event loop.
17608 12164 2025-03-05 22:29:05 223.555 ClientSession: A valid certificate for this server was found.
17608 836 2025-03-05 22:29:08 125.043 ClientUpnp: WARNING! Mapping of port ‘4365’ failed after ‘3834’ ms.
17608 20328 2025-03-05 22:29:13 138.856 ClientSession: Going to query the server for available services.
17608 20328 2025-03-05 22:29:17 748.888 ClientSession: Selecting the destination node.
17608 20328 2025-03-05 22:29:17 792.527 Connection: Connection at 0x0000000006908900 failed.
17608 20328 2025-03-05 22:29:17 792.527 ClientSession: Runnable at 0x0000000006908900 caused the session at 0x0000000003b13850 to fail.
17608 20328 2025-03-05 22:29:17 792.527 ClientSession: Failing reason is ‘The session negotiation failed.’.
17608 20328 2025-03-05 22:29:17 803.732 ClientSession: Stopping session at 0x0000000003b13850.
17608 20328 2025-03-05 22:29:17 806.735 ClientSession: Destroying display client.
Info: Connection to 146.107.25.27 port 4020 closed at 22:29:17 816.177.
Info: Slave server running with pid 2196.
Info: Listening to slave connections on port 58613.
17608 20328 2025-03-05 22:29:17 821.718 Connection: Stopping connection at 0x0000000006908900.
17608 20328 2025-03-05 22:29:17 821.718 ClientDaemonConnector: Stopping the current connection.
17608 20328 2025-03-05 22:29:17 821.718 Connection: Stopped connection at 0x0000000006908900.
17608 20328 2025-03-05 22:29:17 837.428 ClientSession: Stopped session at 0x0000000003b13850.
17608 20328 2025-03-05 22:29:17 837.428 Connection: Stop reading because of parser request.
Thanks for any help.
Bernd
Hi, I removed your public IP from the log excerpt for privacy reasons. Is there a specific reason for using version 8.9 to connect? Have you considered updating it? This would narrow down the issue so that we aren’t investigating older versions to find out that the problem was being caused by something already fixed.
That said, we would need the server-side logs so we can check them. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. It’s important to enable debug, reproduce the error, then zip up the logs.
Also the player logs would be useful as well. (instructions are in the same document)
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
You must be logged in to reply to this topic. Please login here.