Debian 12 connection time out after 1st connection

[rfemali3]

I have a Debian 12 machine which is displaying the following behavior with NoMachine:

– After a reboot, I can connect and get the login screen. Upon entering my credentials it takes approximately 45 seconds to switch to the desktop

– Once that initial connection is terminated, if I try to connect again I just get hung on a white screen and an occasional connection time out error.

– If I log out of the Debian and try to connect, NoMachine tells me there is no desktop available

The Debian usually has an HDMI dummy plug in it, but the behavior is the same if I have a monitor connected. The Debian is also using KDE.

I am primarily connection to this machine through my Mageia 9, but the issue seems to be the same if I try to connect with my Windows 11 or RaspPi.

I tried to attached the server side logs, but I get a file size error.

Thanks.

[Britgirl]

Did you already see our article about headless Linux hosts?

Connecting to Linux headless machines with NoMachine
https://kb.nomachine.com/AR03P00973

sudo init 3

sudo /etc/NX/nxserver --restart

 

[rfemali3]

Britgirl,

Thanks for the reply. According to the article sudo init 3 should be run if your Linux does not have systemd, but Debain 12 does.

Option 2 in the article is to use a dummy HDMI dongle which I stated I do and the issue is still present after a reboot with a monitor connected.

I did try the sudo /etc/NX/nxserver --restart but that did not change the condition.

[Britgirl]

Hi, we need to see the logs from the host you are connecting to. Use the automatic procedure here: https://kb.nomachine.com/DT07S00243. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Hi, sorry for the delay in coming back to you. Logs confirmed that the issue is related to a Trouble Report already open https://www.nomachine.com/TR05V11141 and which will be fixed in the next software update. The workaround is to set
WaylandModes drm,egl,compositor in the NoMachine node.cfg file on the server.

[rfemali3]

Also, is there any reference material that would help me read the logs so I can better self diagnose?

 

 

 

[Britgirl]

The Trouble Report was solved in the following software update: https://kb.nomachine.com/SU05W00266. Please update to NoMachine 9 if you’ve not done so already. Thanks.

[Author]

Posts