NX service instantly stops

[bunnicus]

Hi,

New to NoMachine. Both systems are running openSUSE Tumbleweed, my client is running the Enterprise client from Flatpak and my server is running the tarball from the website. Both machines are on version 9.0.188.

Whenever I install NoMachine on the server, I get systemd errors. The service file copies into /usr/lib/systemd/system fine, but fails to start. The error stems from selinux, and I’m able to circumvent it by running sudo chcon -t systemd_unit_file_t /usr/lib/systemd/system/nxserver.system. After that the service file becomes visible to systemd, but trying to start it fails. sudo systemctl start nxserver returns no output, but systemctl status nxserver reveals that it fails to start. Systemd doesn’t give me much insight, but if I try to run /usr/NX/nxserver --daemon (the command that the service file tries to run), I get: 500 ERROR: Invalid command: 'daemon'. Commands /usr/NX/nxserver --restart and --start hang for a while, then end up returning that all of the services have been disabled.

This behavior is reflected in the NoMachine GUI, as when I try to start the NX service, the status briefly changes to Starting before changing back to Not running.

I have rebooted both systems, and my server’s firewall is configured to allow port 4000 via TCP and UDP. Any help would be appreciated!

[Britgirl]

Can we see the logs from the server side machine? Go to Settings > Server > Security, set log level to 9, reproduce the problem, then “take logs “. For full instructions see this document:  https://kb.nomachine.com/DT08U00298. Send us the complete file, you can either attach here or send directly to forum[at]nomachine[dot]com, making sure to reference the title of the topic as the subject of your email.

[bunnicus]

Server-side logs are attached to this post. Notably, the daemon log is completely empty.

Attachments:

1. Desktop-logs-2025-07-12-18.56.28.zip

[Britgirl]

What you sent us is from the player side.

192 192 2025-07-12 18:56:21 028.117 ClientSession: Failing reason is ‘No route to the network or to the host ‘172.xx.x.xxx’ was found. The issue could either be caused by a wrong server address or by a networking problem. Please verify your connection and try again.’.

On the server host you want to connect to (172.xx.x.xxx), go to the settings>server>security and set debug level 9, restart, reproduce and click take logs.

[bunnicus]

This is definitely the logs from the server system (I know because the client is a laptop, and the server is a desktop). Unless I need a different software suite for the server, then this is the server’s logs. My client can ping the server just fine, so there shouldn’t be a routing error here (unless the routing isn’t correct on the server only?). I’ve tried again today and nothing is different in the logs, I would upload them but they now exceed the max file size on the forums–is there a way to clear the old logs?

Thanks again for the help :3

[Britgirl]

You can send to forum[at]nomachine[dot]com.

[bunnicus]

Done

[Author]

Posts