Forum Replies Created
-
Posts
-
Please see my answer to a similar thread here:
Before changing the configuration key, you should first quit the NoMachine Player (you can do this by right clicking on the !M icon in the system tray and selecting ‘Quit NoMachine Player’.
Then re-open the Player and connect again. Sorry for not specifying that earlier.
What you sent us shows that it is this problem here, related to Nvidia drivers:
https://bugzilla.mozilla.org/show_bug.cgi?id=1758473
and not caused by NoMachine software.
On the Player computer, please edit
option key="Enable hardware accelerated decoding" value="disabled"in player.cfg.Sorry for the delay. Server logs show that whatever problem is there occurs before the session starts. However, the logs also show that debug level in node.cfg wasn’t enabled and this would be useful in order to be able to comment more specifically. Could you run
sudo /etc/NX/nxserver --debug --enable alland restart? The the nx* log entries from journalctl would be useful as well. Please see section “Logging to syslog” of the document here: https://kb.nomachine.com/DT11R00182#1 on how to extract that file.Hi, you can do exactly the same thing with NoMachine except you will have to perform those steps manually (given that Easy-GPU-PV uses a built-in script to install the other product).
You could use the /verysilent install method to install NoMachine
Hi, if you are running Wayland in a VM, try the tips here:
Connecting to a Wayland-based desktop running in a Linux virtual machine
https://kb.nomachine.com/AR04R01083You could also consider using X.org instead of Wayland like this user https://forums.nomachine.com/topic/connecting-arch-desktop-to-arch-laptop-got-error-104#post-39945
Server side seem ok. Does the session window close as soon as you connect? It could be a crash on the Player side, which would explain why there is not enough information from the Player .
Can you check for segfaults on the Player side? This article explains how to look for core files.
Could you send us the logs of the Mac server? Please follow the instructions here and send them to forum[at]nomachine[dot]com using the title of the topic as the subject of the email. Thanks!
Collect server side logs automatically
https://kb.nomachine.com/DT07S00243Can you all update to the latest NoMachine version, 8.1.2? It solves this TR:
Cannot connect to physical desktop on macOS after a system update
https://www.nomachine.com/TR10S10377Note that the fix to this Trouble Report will require giving accessibility permissions to NoMachine or nxnode one last time.
Hi, do you mean turn off the monitor if there is one attached to save power, for example? If so, this is not supported. NoMachine can still connect you to a Mac/Windows/Linux computer without a monitor attached or switched on though.
We checked on the fly with Tailscale (free version) and it works out of the box ie. we didn’t have to change any settings. Did you already try and it didn’t work?
Is the connection via NoMachine not working both ways?
Are you using the free version of Tailscale or a paid option?Without Tailscale, can you connect to your RPi? What OS is on the Raspberry?
Hi, we have attempted several times to reproduce a similar behaviour on our latest release (v8.1.2), but without success. Can you send us the logs from the Linux server?
Please follow the instructions here: https://kb.nomachine.com/DT07S00243
and submit them to forum[at]nomachine[dot]com. Please use the topic title as the subject of your email.Thanks.
Hi, We are aware of a similar behaviour that another user has reported, although we are not able to reproduce in our own environments. Please confirm the Linux Mint version and desktop environment (Mate, XFCE?).
Hi, we fixed this TR in the 8.1.2 release
Cannot connect to physical desktop on macOS after a system update
https://kb.nomachine.com/TR10S10377Note that the fix to this Trouble Report will require to give accessibility permissions to NoMachine or nxnode one last time. After that, the problem should not appear again.
Check that permissions are added. Does this help?
Hi, check that you USB is enabled on your Linux server.
What to do if USB support is disabled on Linux
https://kb.nomachine.com/AR12J00658then try again, and don’t forget to check that it loads correctly (tip in the last part of the article).
After compiling the kernel module it’s a good idea to check that it loads correctly on the machine where you compiled it. To do this start a NoMachine connection, open the Menu -> Devices -> Connect a USB device, and wait 10 seconds until available devices appear. Then, open a terminal on the host where you compiled nxusb.ko and type:
lsmod | grep nxusb
If the output is not empty, the nxusb kernel has been compiled and loaded correctly on your machine.
Does it help?
Please our notice here about iOS16.
Important notice for NoMachine users about iOS version 16
‘https://forums.nomachine.com/topic/important-notice-for-nomachine-users-about-ios-version-16’