Britgirl

[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.

[Britgirl]

Hi, if you are referring to whether you can use the host certificate for different protocols, then yes, it’s also possible to use the same certificate with all of them.

[Britgirl]

Hi lmvdr, we have not received any email requesting the debug version. But not to worry, your comment is enough as proof. Thanks for confirming, the package is being prepared.

[Britgirl]

Please update to NoMachine 9, a fix was released for the issue you reported when using the external keyboard.

Hardware keyboard stops working on iOS after opening session menu
https://kb.nomachine.com/TR03W11295

Please start a new thread if you continue to have issues.

 

[Britgirl]

Firstly we recommend to update your client 7 because you are using an unsupported version. If possible also update to the latest 8.17, or version 9.  Logs would be useful to investigate further. A similar topic was handled here: https://forum.nomachine.com/topic/blurry-coloured-font-on-version-7-6-2.

[Britgirl]

We don’t offer a service monitoring because there is specialized software to do that. We could possibly evaluate doing something in future, but we don’t have any short term plan. Something that is not strictly related with what you asked for, but that can still be useful, is a new “Machine info” context menu entry in the machines roster that connects to the server and gets the statistics. This will be available in one of the 9.x maintenances.

[Britgirl]

Hi,

1) screen blanking is still not available with KDE due to missing support in the D-Bus API

2) it’s not possible to show a login screen because NoMachine shows exactly what is shown on the physical display, while RDP creates a virtual desktop (virtual desktops are available also with NoMachine in the Terminal Server products). One possible way to regain access to the local system is logging in from a different player (even from a phone) and disconnecting the current connection.

[Britgirl]

Hi, have you activated scaling in the Window’s own system settings?

Open the session menu (Ctrl-Alt-0) and increase the Display quality. Does that help?

If not, try disabling hardware encoding on the target Windows computer, and then also hardware decoding on the Mac.

To disable HW encoding on the Windows machine, open the NoMachine Settings there, go to Server > Performance  > and make sure the option “Disable hardware encoding” (https://kb.nomachine.com/DT05U00288#3.7) is enabled.

To disable decoding on the Mac, during the session open the session Menu > Display > Change settings > Modify and select “Disable client side hardware decoding”.

[Britgirl]

As promised, here is the article

How to use custom host certificates with NoMachine v9 (Host, Client, and CRL Configuration)
https://kb.nomachine.com/AR06W01292

[Author]

Posts