Britgirl

[Britgirl]

The key-pair that you generated would be useful for our own tests, but we’ll take a look at the logs in the meantime and come back to you.

[Britgirl]

Hi, I was just about to reply to you asking you to send the logs, but then you seem to have resolved the issue.

What I was going to mention was to not edit the AvailableSessionTypes key, since it should not be necessary – if you remove physical-deskop from the key, this will prevent you from connecting. So restoring the original cfg cofiguration was a good idea.

You mention GDM, so now we know you are connecting to a Gnome desktop. It would have been useful to know which command is used in the NoMachine node.cfg file. You can run the following to find out: grep DefaultDesktopCommand /usr/NX/etc/node.cfg.

But next time it happens and you can reproduce it, we need to see the logs with debug enabled from the Debian host you are connecting to. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

I’m not sure to understand how exactly !M works

As I mentioned earlier NoMachine Free Edition lets you connect to the physical display, installs out-of-the-box and should not require configuration of node/server cfg files. On Linux when it can’t find an xserver running e.g the video card is turned off, NoMachine creates its own to let you access the desktop all the same. (see more about this here: https://kb.nomachine.com/AR10K00700). About the resolution, take a look at the following article: https://kb.nomachine.com/AR02M00836. I’m not sure what changed suddenly that now means you connect correctly and see the display at the proper resolution, but it’s most likely due to the desktop configuration or system. As I said if it happens again, logs and also screenshots would be useful.

[Britgirl]

ECS provides internal loadbalancing of the connections between the primary/secondary server of the cluster pair. It does not loadbalance between separate ECS gateways. To do that, you can use any tool that load-balances at the router level e.g HA Proxy.

[Britgirl]

One other possibility is to change a key which can be used to change the screen grabbing method in the node.cfg file on the Macbook Pro server host. Look for the DisplayServerExtraOptions "" key, remove the prepending # and change it to this: DisplayServerExtraOptions "-nosckgrab". Restart the NoMachine server. Then try to reproduce the black screen issue.

[Britgirl]

Thanks for letting us know.

[Britgirl]

Good to know that resolved it!

I’d like to update my earlier response where I suggested to edit the player.cfg. My apologies for not suggesting it first. In your case, you could actually disable HW decoding on the fly for that session from the connection menu (the libraries are still loaded but are not used).  Open the NoMachine menu panel inside the session by Ctrl+Alt+0 or click on the page peel at the top right corner of the window. Then click on Display -> Change settings. In that panel click on the Modify button to open the advanced display settings.  Click on ‘Disable client side hardware decoding’ to disable it.

If possible, would you be able to send us the logs from the Player reproducing the error? It would mean reverting your edit to the cfg file.

[Britgirl]

When you say “when using Windows”, which specific Windows version is it? What iOS and macOS versions do you reproduce it on?
Could you send us the logs from the macOS server? Please enable debug and reproduce the problem following the instructions here: https://kb.nomachine.com/DT07S00243

You can submit them 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]

I should have been more specific, apologies for that. Run those commands again as root in a terminal.

[Britgirl]

Hi, can you generate a fresh pair of keys (public/private), so that we can test them? Also logs from the tablet would be useful to start off with.

If you can connect your iPad to a Mac, you can select it among Locations in Finder, then drag and drop the folder ‘nx’ in Files > NoMachine after reproducing the issue.

Alternatively, you can open the Files application, select Browse > NoMachine, then compress and share the folder ‘nx’

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

[Author]

Posts