Forum Replies Created
-
Posts
-
Hi, USB on Android devices is not currently supported. That’s not to say we will never add support for USB on mobile đ It’s just we’ve not considered it a priority in our development roadmap.
Try the following:
1. Quit the Player and disable hardware decoding on Pop in the player.cfg ->
option key="Enable hardware accelerated decoding" value="disabled". Restart the Player. Try connecting again. If that doesn’t help, go to point 2.2. Disable hardware encoding on Fedora ->
option key="EnableHardwareEncodingâ key to 0in node.cfg on the server side. Restart the server.If that doesn’t help, it would be useful to see logs. Please check here on how to extract them and then submit them via email (or here if they are not too big) to forum[at]nomachine[dot]com: https://kb.nomachine.com/DT07S00243
Can you provide an example of the Host filled be completed using a DDNS address rather than a Public IP address?
Maybe you should show us how you are configuring your NoMachine connection. Please submit a screenshot so we can see.
Indeed, a fix is scheduled for a later release. So it is still “open” as you can see from the Trouble Report I linked above đ
A NoMachine connection uses either the hostname/domain name or the IP address. You cannot use an email address in the host field.
I understand that if you use the IP address, you can connect with NoMachine? Or do you have problems there? If so, what error are you seeing?
With the other product are you connecting to an email address?
What kind of model router do you have?
Adding such a feature, i.e to allow the monitor to be switched off, would be counterproductive in that turning off the display when connected may cause display or performance problems because the graphics card can stop working.
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.