Britgirl

[Britgirl]

We assume you are using the latest version 9. We have not been able to reproduce this. Please tell us the desktop environment you are connecting to on the Ubuntu VM. Does it happen when pasting to all Ubuntu applications or with specific ones (which ones)?Are you using NoMachine free edition both sides?

[Britgirl]

So you can reproduce it when you connect from on Win 11 (any NM version) to NoMachine v9  on Windows Server 2025? What NoMachine product is installed on the NoMachine server side?

[Britgirl]

Just to update you, we have received your email with your User Id details and will come back to you with our findings soon.

[Britgirl]

A quick update on this. The bug that was reported here was not fixed as I previously wrote. In the next maintenance of v9, there will be a fix, so please follow us for updates 🙂

[Britgirl]

Check your emails 🙂

[Britgirl]

To avoid investigating the same problem twice, in your case poi101 I suggest to go through the support channel.

[Britgirl]

Hi,

we haven’t recently tested although we did in the past and had no problems. What specific Cloudflare product are you using?

I wonder if making the solution (add DisplayServerExtraOptions “-eventdelay 0” to the config file) shouldn’t be the default; it produced no downside in my other two remote machines.

NoMachine’s default behaviour is always to give precedence to the input events from the local user over the ones from the remote user, so that the local user will always have the possibility to re-take control of the session.

[Britgirl]

Now that version 9 is out, it makes sense for you to update to that and provide feedback. The forums are for problems on the latest version. Problems with NoMachine 8, which is still of course supported, can be investigated through a support ticket. So, please let us know if you are both still able to reproduce this problem of “service stops running” on the latest release. If you can please, submit the logs. We have new instructions and a much easier way to get the logs with NoMachine 9. Please see the steps here: https://kb.nomachine.com/DT08U00298#1. The server logs will provide all logs that we need.

[Britgirl]

The logs that we received did not reveal a specific reason for audio being muted. What we suggest is you update to NoMachine 9 and report back. That release implemented some internal improvements related to audio in general.

[Britgirl]

The logs show there is no virtual frame buffer running at all, and what’s more they appear to be very old,

Info: Connection from 192.168.4.3 port 54578 process 687051 closed on Sun Feb 23 17:39:53 2025.

The last connection in nxd log is February.

What I suggest you do is update to v9, set debug level, restart nxserver, reproduce the problem and take the logs, there is a new and easier way to gather the logs: https://kb.nomachine.com/DT08U00298#1.1.

[Britgirl]

Hi, that key is for when a user starts a new virtual desktop. If users are reconnecting to previously started virtual desktops, the message will not show.

# Specify the message to be shown to the user every time the user
# starts a new virtual desktop on this host.
#
NodeLoginGreeting "Welcome to your NoMachine session

If users are reconnecting and you want to show a custom message, you need something similar to this:

https://knowledgebase.nomachine.com/AR02L00787 – example 2.

There is more info about user scripts in the installation and configuration guides, for example: https://knowledgebase.nomachine.com/DT11R00174#11.5)

[Britgirl]

Hello,

the NoMachine server starts the ‘nxnode’ process for each physical session it can find. And if the ‘nxnode’ process dies, the NoMachine server starts a new one.

From the logs we received, we can confirm that the ‘nxnode’ process was terminated multiple times:

 
14900 14900 2025-06-11 12:50:35 740.766 NXSERVER AE4FDAF35DE9F6D1158D8979474C505F nxnode died with exit code 0.
...
14900 14900 2025-06-11 12:50:35 817.165 NXSERVER NXNodeProcess: Creating nxnode process for login 'tester'.
...
14900 14900 2025-06-11 12:50:36 425.110 NXSERVER 0186C0AD42B2738F9DC006E3B3A88C1C nxnode died with exit code 0.
...
14900 14900 2025-06-11 12:50:36 439.917 NXSERVER NXNodeProcess: Creating nxnode process for login 'tester'.
...
14900 14900 2025-06-11 12:50:46 272.184 NXSERVER 3160688611DC8279340DEFFE0E4BBAFD nxnode died with exit code 0.
...
14900 14900 2025-06-11 12:50:46 291.072 NXSERVER NXNodeProcess: Creating nxnode process for login 'tester'.

…

The reason why the server starts the process specifically for user ‘tester’ is that during this entire time the following were running:

– an active systemd session for user ‘tester’:

 
14900 14949 2025-06-11 12:50:35 748.672 NXSERVER ServerPhysicalSession/ServerSetSessionDataFromSystemd: Systemd session '9' uid '19036' active '1' type 'x11' seat 'seat0' display '0'.

– a running Xorg process for user ‘tester’ on the display ‘0’:

14900 14949 2025-06-11 12:50:35 749.430 NXSERVER ServerPhysicalSession/ServerGetXSessionProcessForDisplay: Found X server process 'Xorg Xorg /usr/bin/Xorg -br :0 vt7 -nolisten tcp -auth /var/lib/kdm/AuthFiles/A:0-bxumbb'.

Can you confirm that the owner of the Xorg process is ‘tester’ user?

[Britgirl]

Hi, we are not aware of a similar problem. Please send us the logs from the NoMachine client device that you are connecting from.

Reproduce the problem, and keep the session window open. Open the menu panel (ctrl+alt+0 or click on the page peel in the top right corner of the window) click Connection and click on ‘Take the logs’.

You can upload them here. Thanks!

[Britgirl]

That’s correct. On Windows and Mac NoMachine connects you to the physical display of the target host. When connecting to a computer that has multi-monitors attached, you can switch between them. NoMachine automatically detects that multiple physical displays are available on the server side : https://www.nomachine.com/support/documents/switching-the-view-between-multi-monitors-during-a-remote-desktop-session

[Britgirl]

Hi, did you try with a different browser to see if audio is missing also with a different browser?

We are a aware of a similar problem, reported in web sessions. As a solution for audio in web sessions with server v9, it should be enough to set in server.cfg:

AcceptedWebMethods webrtc

or (if you want a failover in case the browser doesn’t support webrtc):

AcceptedWebMethods webrtc,mjpeg

(Remove the prepending # from the key name, if present).

Then connect a new web session. You can track the fix for this issue using the following link: https://kb.nomachine.com/TR06W11399.

[Author]

Posts