Forum Replies Created
-
Posts
-
Here is the link to the Trouble Report which you can monitor to know when the fix has been released.
Hi, an update on this. You sent us the logs and you also told us you were already using open source drivers. The logs show that the capture method fails with the same errors that we have seen when proprietary drivers are in use. Can you tell us more about the open source drivers you are using? And also confirm whether the server is running in a VM or not.
It might be. As I mentioned earlier, the issue is triggered by a strange case where all sockets get into an error state at the same time. This is for sure something occurring at the system level and not dependent on NoMachine. We don’t know the specific reason, but the point is that NoMachine doesn’t fail cleanly in this particular case and an infinite loop starts, spamming the log. We detected the problem and a fix will be available in the next release. If you want, we can send a patched library.
A fix will be available in the next release for mobile. Please use the following link to track its status: https://kb.nomachine.com/TR10V11229.
We have released an update so you should download the latest package for your architecture and try that. You can disable Wayland by doing the following:
sudo raspi-configAdvanced Options -> Wayland -> X11 -> OK -> Finish -> Yes (to reboot)If you are still encountering the issue, please submit the NoMachine logs from the Raspberry Pi device. 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!
Is it possible you have a double NAT (if your IP address that you are using to connect does not match what is showing on whatismyip.com, it could be an indication of two routers)? UPnP doesn’t support the double NAT scenario, so you would need to enable port-forwarding on both routers.
At the moment there is no option on the client side BUT we are going to add a “disconnection option” in the player GUI to handle the situation when a session may become inactive. Similarly for the server side, we will also add an option to disconnect the connect in the GUI so that users can avoid interacting with the cfg files. We don’t have an ETA, but it’s definitely something we are going to do.
For your question about player.cfg options, take a look at the following document: https://kb.nomachine.com/DT07S00240.
Did you already take a look at the following article?
How to connect over the internet to NoMachine behind a NAT router
https://kb.nomachine.com/AR10R01099“Failed to map the port on gateway” suggests that the port you used in the port-forwarding rule on your router could already already be in use. Go back to your router and change the external port number to something else, then restart the nxserver (NoMachine settings -> Server -> Status -> Restart) . For safe measure also restart UPnP.
Is it possible there is a double NAT in place? If so, you will need to map the ports on both routers. So Router A must map to Router B and Router B to the computer you want to access.
Hi,
can you verify that the Local Network privacy in macOS is granted for NoMachine? If it is, uncheck and check the permission box again. Does that help?
(please ignore my previous reply, it was an error on my part, hence I have removed it)
To add the node, run
sudo /etc/NX/nxserver --keyadd /home/user/node.localhost.id_rsa.pub. We create /var/NX/nx/.nx/config/autorized.crt during the nodeadd procedure. It seems you were writing your last reply whilst I was writing mine, so take a look at the article I linked and follow the instructions there.Hi, it’s impossible given that NoMachine encrypts all traffic end to end, including X11 protocol when used. You can take a look at the following article which explains how NoMachine handles security and encryption, https://kb.nomachine.com/AR04S01121. Some other pointers can be found in this article https://kb.nomachine.com/AR11K00745 published at the time we transitioned away from our legacy version.
Gary, you did not submit the logs from the server side, i.e the Ubuntu machine. Enable debug on the Ubuntu machine, reproduce the problem, then gather the logs (https://kb.nomachine.com/DT07S00243).
Journalctl logs would be helpful as well.
Try changing the DefaultDesktopCommand key in node.cfg on the server by adding the
--disable-acceleration-checkoption to the gnome-session command, e.g.:DefaultDesktopCommand "dbus-launch –exit-with-session gnome-session –session=ubuntu --disable-acceleration-check"In general, when adding a node to the cloud server, you don’t have to copy any key, the procedure to add the node will propagate the key for the node to use. To do that, you need the admin credentials on the node, the Terminal Server host in your case.
However, when you don’t have admin permissions on the node you want to add, for example there are two separate administrators for both machines, you can indeed pass the CS public key to the admin of the TS Node, and they can place it in the appropriate directory. On Linux, the public key can be found in the directory, for example in /usr/NX/etc/keys/node.localhost.id_rsa.pub. You, the CS admin, can then proceed to add the node to the Cloud Server with sudo /etc/NX/nxserver –nodeadd IP_of_node –node-name name_of_node.
See the article here: https://www.nomachine.com/AR11V01258.