Britgirl

[Britgirl]

Hi, are you able to send us the full server-side logs so we can check what’s happening? You can extract them using the instructions 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!

Additionally, any journalctl output (sudo journalctl -x |grep -i gdm) and the output of ps -ef.

[Britgirl]

Hi Zak, can you submit a new topic so that we handle this issue separately?

[Britgirl]

I forgot to post the link to the Trouble Report https://kb.nomachine.com/TR05V11159. You can use that to track when a fix has been released.

[Britgirl]

Can we send you a debug version?

[Britgirl]

We checked the logs and confirm that the problem is the same as the one reported here: https://forum.nomachine.com/topic/nomachine-not-using-gpu-for-encoding#post-47274 related to specific nvidia driver versions. We are currently investigating workarounds, but for the time-being you should try downgrading to an earlier driver version (535.129.03 appears to be ok) or continue to use software encoding.

[Britgirl]

We don’t have an official date for the release yet, but we are working hard to make it available by this summer.

[Britgirl]

Some clarifications to your comments…

… won’t allow NoMachine to become visible to the distant computer.

NoMachine hosts are visible to other NoMachine clients when they are all on the same LAN (i.e in Machines computers on the same LAN show with a pipe icon).

Distant computer user entered the host’s local LAN IP ’cause presumably that’s the way NoMachine works

When the user is on the same LAN as the computer you want to connect to, the local LAN IP is used. When connecting over the Internet, you use the public IP address of computer. For most users, this is the IP address of the router that sits in front of the computer you want to access.

Did you already see https://docs.netgate.com/pfsense/en/latest/nat/port-forwards.html#figure-port-forward-example (for the Pfsense port forwarding configuration)?

[Britgirl]

Hi, we checked the logs and we see that encoding fails at a very early stage, at a point where it seems unlikely that it can be a NoMachine issue. Can you confirm in any way that the other apps you mention are using HW encoding and not a SW fallback? How have you checked that they are using HW encoding?

[Britgirl]

Hi, can you send us the logs from the OS you are connecting to (i.e the NoMachine Windows server).  Please use the following instructions:

https://kb.nomachine.com/DT07S00243
To enable debug on Windows, open a CMD console as administrator:

> %ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --enable all

Start a session as usual and then gather the logs:

> %ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --collect

The log archive is named as: NoMachine-log-.zip (e.g. NoMachine-log-2018.09.27-11.44.01.zip) and stored in: %PROGRAMDATA%/NoMachine/var/log/archives on Windows 10/11. Send them to forum[at]nomachine[dot]com. Thanks!

[Britgirl]

😀 ok, thanks for updating us. Happy nomachining!

[Britgirl]

Strange. This sounds more like a network problem. When you see that error, can you ping or ssh in to the Pi?

[Britgirl]

Did you install FF via snap? Make a test of audio in the virtual desktop, with any app not installed by snap, e.g vlc player. Does sound work?

Install FF this way: https://www.omgubuntu.co.uk/2022/04/how-to-install-firefox-deb-apt-ubuntu-22-04

Then connect to the virtual desktop.

[Britgirl]

You can try with “custom scripts”, they’re also supported in the free version. Take a look at the following article:

Server Automation Interface: some examples to use custom scripts triggered on server/node events
https://kb.nomachine.com/AR02L00787

and any of the guides of the Enterprise products. Here’s the link to the Enterprise Desktop guide (like the free version but with more features) https://kb.nomachine.com/DT10R00171#11.3.

You could use, for example, UserScriptAfterSessionStart (in node.cfg) executed as user, not as user nx. Prepare your script and run it at disconnection to restore the previous monitor configuration.

#
# Specify absolute path of the custom script to be executed after the
# session start-up. The script can accept session ID, username, node
# host and node port as its input.
#
#UserScriptAfterSessionStart “”

or

#
# Specify absolute path of the custom script to be executed after
# the session is disconnected. The script can accept session ID, user-
# name, node host and node port as its input.
#
#UserScriptAfterSessionDisconnect “”

[Britgirl]

3093 3093 2024-05-23 15:28:39 406.174 NXSERVER Read 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n' 78 from FD#16.

There are some permission denials occurring when NoMachine attempts to create the .nx directory in the user’s home. Check that user DV9G49 has rights to create it.

An option is to set the path by using the key below, in node.cfg
#UsersDirectoryPath ""

# Specify a different path to the default home to create the .nx
# directory for storing session files and user's logs. This doesn't
# apply to the nx user, the NoMachine reserved user necessary for
# internal operation. If it doesn't exist yet, a sub-directory is
# created for the user who's starting a session, named as username.
# The .nx directory is created under that sub-directory. E.g. if this
# key is set to /tmp/nxdir/, when user nxtest runs the first session,
# the /tmp/nxdir/nxtest/.nx will be created. The directory specifed
# in the UsersDirectoryPath key should be writeable for all users or
# alternatively, the administrator should create a directory with
# proper ownership and permissions, named as username, for each of
# the users who need to start sessions there.
#
#UsersDirectoryPath ""

[Britgirl]

Thanks for the screenshots. I was not clear in what I wrote yesterday, sorry for that. When I wrote “You can check if file-transfer is enabled by going to Server settings from the !M icon on the remote desktop > Security > Scroll down to “File transfers” and check that the boxes are ticked.” – you need to do that on the Red Hat host you are connecting to, not on the Mac. The settings panel you showed us are the server settings for your own Mac (so if you were to connect to your Mac from another client, those settings control the upload and download of files from and to your Mac as a server).

If you are not the administrator and can’t access the NoMachine server settings, you need to make a request to who is responsible for that machine. It is likely that file-transfer has been disabled in the configuration files of the server by whoever is (i.e the FT key has been set like this: EnableFileTransfer none in the node.cfg.)

[Author]

Posts