Britgirl

[Britgirl]

Hi, did you also try disabling HW decoding on the Player side? That means editing the following key in the player.cfg file option key="Enable hardware accelerated decoding" value="disabled" (see https://kb.nomachine.com/AR07U01202). It’s important to exit the player first and re-open after editing before trying to connect again.

If that didn’t help either, are you able to send us the full server-side and player-side logs so we can check them? Enable debug on the server side before reproducing the problem. Complete instructions on how to get both server and player logs are available here: https://kb.nomachine.com/DT07S00243

Attach here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Hi, are you able to send us the full server-side and player-side logs so we can check them? Enable debug on the server side before reproducing the problem. Complete instructions on how to get both server and player logs are available here: https://kb.nomachine.com/DT07S00243

Attach here to send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Hi, for sure it’s related to the server, something has changed on Ubuntu side in Google Cloud, but it’s hard to say exactly what without seeing the logs. Please follow the instructions here to enable debug in the NoMachine server. Reproduce the problem by trying to connect, then gathering the logs. 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!

[Britgirl]

Hi, at the moment maintaining the aspect ratio can be obtained keeping Control and Alt keys pressed (when ‘Fit to window is enabled’) while resizing the window. But it doesn’t currently apply to a maximized or a fullscreen window. We are planning on extending this through an option in the connection menu, so that it’s also possible to keep the aspect ratio when the window is moved to fullscreen or maximized state.

[Britgirl]

Additionally, please open a terminal on the macOS server host and provide the output of:

i) /usr/bin/install -g wheel -m 644 -o root '/Applications/NoMachine.app/Contents/Frameworks/scripts/etc/pam.d/nx' '/etc/pam.d/'

ii) ls -l /Applications/NoMachine.app/Contents/Frameworks/scripts/etc/pam.d/nx

iii) ls -ld /etc/pam.d

[Britgirl]

Hi, logs show an authentication problem related to PAM, which we’ve not encountered on macOS 15.4. But, we noticed you’re using the macOS just released (15.4.1) which we are currently testing and we’ll try and reproduce. In the meantime, please enable debug as per the instructions here https://kb.nomachine.com/DT07S00243 from the macOS server-side, reproduce the error and submit to us here or via email to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks.

[Britgirl]

Hi,
the window that pops up is the NoMachine panel showing what desktops are available. When you connect to a Terminal Server product, Terminal servers always show this panel because it asks you to select either the physical or a virtual desktops. I’m assuming you have a TS product installed, so you could try the free edition or the Enterprise Desktop product, both of which are for connecting to the physical display only. In that case, your command will connect you directly to the desktop.

[Britgirl]

If you have a vnc session running, killing it will then allow NoMachine to create the virtual xframebuffer session. After that restart the nxserver with nxserver --restart. Check what is configured in the DefaultDesktopCommand key in the node.cfg file. You could try using, for example, the same command you use on the vnc server.

If none of the above help, then we require the NoMachine logs with debug enabled from the server host. You should follow the instructions here https://kb.nomachine.com/DT07S00243, reproduce the problem, and then submit here or send to forum[at]nomachine[dot]com.

[Britgirl]

Moreover, I’m surprised at not seeing these config files

Those others you mention are related to the installation and not the configuration and the installation dir is not the scope of the --configsave command. Backing up the install path would create problems when installing on a different host if you are not using exactly the same path. What about if you want to move your configuration to a different OS? As mentioned in the article I linked, the configsave command is to 1) “preserve custom configurations, when it’s necessary to uninstall the current server for whatever reason and install it again”. Or 2) to “migrate the current server installation to a different machine, even running a different Operating System. (E.g. migrate from Windows to Linux)” or to 3) “in the case of multi-node setup, to preserve the current list of nodes and avoid re-adding and configuring them manually after a reinstall or a host migration.”

About the second question you posted, what do you mean with “some files seem to have been forgotten”? Did you try executing the configrestore command as per the article. What was missing?

[Britgirl]

Hi,

nothing has changed between NoMachine 8.4 and 8.16 in how NoMachine Free Edition works. If the server is not headless, you will connect directly to the physical desktop. On Linux, when connecting to the physical desktop which doesn’t have an X server running (e.g. it’s headless), NoMachine Free Edition is able to use its own display service (which is an embedded X server) to let a user connect seamlessly to a physical display running in the background on the remote machine. If you install it on a headless host, the following message appears:

“Cannot detect any display running, Do you want NoMachine to create a new display and proceed to connect to the desktop?”

Selecting OK will create a virtual display (NoMachine’s embedded X server). Is your Debian headless? Are you not seeing this message?

It’s worth pointing out that the free edition does not create virtual desktops like the terminal server products in the Enterprise suite. Virtual desktops are individual desktops, independent from each other that can run on the same server simultaneously and can be left running while you are disconnected. To be able to get multiple virtual desktops, you need a Workstation installed (or higher end product).

[Britgirl]

Hi, in version 9 an Enterprise Cloud Server Cluster (ECSC) is a pair of Cloud Servers that work together to maintain high available access to the centralized infrastructure. Let me sum up how it will work. This is an active-active cluster where the cluster master and slave roles can be switched between the primary and secondary servers. The master is in charge of distributing client connections and the load of session negotiation and management between itself and the slave. The primary and secondary server constantly monitor each other, hence active/active. When one of the servers loses contact with the other one, it replaces the failed server. Sessions already managed by this working server remain connected and the failover is transparent for them. The management of sessions handled by the failed server is passed from the failed server to the working server. The sessions running on the remote nodes continue to be running (they are not lost during the failover), but clients will have to reconnect to them.

[Britgirl]

Hi, we need additional logs and further information.

1. Edit ‘/usr/NX/etc/server.cfg’ file, remove the # from the key name and set the following key:
SessionLogLevel 8

2. Restart the NoMachine server:
$ sudo /etc/NX/nxserver --restart

3. reproduce the problem and upload log archive:
$ sudo /etc/NX/nxserver --debug --collect

It would also be useful to show some information about the physical session:

4. Show the X server process:
$ ps aux | grep X

5. Show the X server process environment variables:
$ cat /proc/<X server pid>/environ

6. List the user sessions:
$ loginctl list-sessions

7. Show information about the physical session (with Type=wayland):
$ loginctl show-session <session-id>

8. Show information about the session owner (parameter “User=” from the previous request):
$ loginctl show-user <user-id>

[Britgirl]

Thanks for reporting. We are currently investigating.

[Britgirl]

Yes. Install the Enterprise Client for Linux in order to connect.

[Britgirl]

We got the logs thank you, and we’ll come back to you soon about those. Do you confirm you are always getting black screen regardless of the client OS you are connecting from?

[Author]

Posts