Forum Replies Created
-
Posts
-
I am able to get a desktop connected with NoMachine if I use a barebones local user account. If I use my Active Directory login with sssd, it doesn’t work. So it could be something related to my AD user configuration, or something with sssd specifically.
This seems to be a different problem to the original one and we don’t understand how the two could be related without investigating further. This might warrant a separate topic so as not to confuse the thread. But first the original issue of not being able to create a display…
For some reason Gnome is failing and to understand why we would need to see the journalctl log of the server. Run (without the ‘grep’)
sudo journalctl -xMaybe you didn’t uninstall NoMachine as expected (as in the guide). You just removed /usr/NX directory which is not the correct way. If you do that our uninstall scripts can’t clean the system. Do the following:
1) sudo rm -rf /usr/NX /etc/NX /var/NX
2) install NoMachine by rpm -i nomachine….rpm
3) uninstall NoMachine by rpm -e nomachine…..Hm, possibly a misconfiguration still? It you want video and audio, then WebRTC needs to be enabled.
We are not able to report your exact same error, but there is a similar issue which is reported here but related to the Moonlight theme: https://kb.nomachine.com/TR01U10758 which is linked in the topic from those listed above (https://forum.nomachine.com/topic/ubuntu-22-04-1-lts-authentication-failed-when-asked-for-admin-password).
What you could check is whether installing zenity helps,
sudo apt install zenity. If that doesn’t help, update to NoMachine 8.9 and let us know if the problem persists.If the server is headless, then NoMachine will create a virtual display. We run the virtual desktop only if we can’t find any physical session running, so at a glance it seems something on the system.
This system worked flawlessly until last week
What changed last week? Did you update something? NoMachine, the OS? Or maybe change a setting or something?
What desktop environment is it?The logs might show some hints as to what is happening. Please check the instructions in the following article, making sure you reproduce the problem before gathering the logs from the server. Submit them to forum[at]nomachine[dot]com making sure to reference the title of your topic in the email subject. Thanks!
Does the server have a monitor? If so, are you able to check it locally when the issue occurs? Is the local screen also grey?
The logs might show some hints as to what is happening and if NoMachine is the cause, even though it seems more on the system side than in the NoMachine software. Please check the instructions in the following article, making sure you reproduce the problem before gathering the logs. Submit them to forum[at]nomachine[dot]com making sure to reference the title of your topic in the email subject. Thanks!
Are you able to submit a screenshot?
Just so we have your setup clear: your client is Mac and the server side is Windows in a virtual machine? Can you provide more details such as OS version on the client side and details of the server setup as well?
Hi, thanks for notifying us.
The problem is that we haven’t been able to reproduce even after many attempts. What we do produce is the cursor not changing shape, but clicking in the right spot, the window does resize. But that “right spot” is a single pixel-wide so it can be difficult to find. It is possible that you are not finding the correct spot? It can take several clicks and nudges of the cursor.
The part I don’t understand is why you are forwarding the ports to the nxserver in order to use WebRTC when in fact you use WebRTC to not have to forward the ports. But it doesn’t matter 🙂
Let’s come back to the WebRTC setup…
You’ve set up your own TURN and also google’s STUN. So, we made some further tests when using google’s STUN server. We got the same errors. Apparently the STUN servers from Google work only with Google and with the Google powered WebRTC services, for reasons we don’t know. How can we investigate more? I doubt Google is going to show us their STUN servers’ configuration. We’ll be updating the documentation accordingly.
What to do? Remove Google’s STUN and try using coturn’s STUN. Coturn can be configured as both a STUN and TURN server and it works. See point 8 of the article AR07N00894. Let us know how you get on.
Hi,
server logs show:
1260 1260 2023-10-04 22:14:25 642.149 NXSERVER WARNING! Node 559f7dda-f4cc-4302-8617-351ef916b26b from session B44E42017A62285DD8CAEFCD8CC2E8E1 reported: Session with pid '1138' terminated unexpectedly.We would need logs with debug enabled to understand more clearly.
https://kb.nomachine.com/DT07S00243
Please follow the instructions in the document for the server side at the link above. When you’ve enabled debug, reproduce the same 104 error and zip up. Send them directly to forum[at]nomachine[dot]com making sure to use the title of the topic as the subject of your email. Thanks!
I would say that it is quite normal. That’s 75-80% of a single CPU core, which is possible, especially if the remote screen resolution is high.
I don’t understand. You say “There is an ubuntu server VM which has ports 3478 TCP and UDP, and UDP 49152 – 65535 forwarded to it”. Do you want to use, do you plan to use WebRTC, and so the TURN, STUN servers or not? As I said, you can connect directly to the nxserver in question, if you have the ports being forwarded to it. But if you want to use WebRTC, you must not forward the ports, and instead use the TURN, STUN servers, configuring these into the server.cfg as we said. Please, don’t forward the ports, don’t open the ports on your router, do the nxserver.cfg configuration as I said and tell us if WebRTC works.
If I understand correctly, a peer to peer connection requires open ports on both ends, which would be an issue as most people can’t open ports on their routers.
Here is where STUN kicks in, by allowing the “hole punching”, so even if there are no ports, opened beforehand, on the routers.
However, couldn’t a TURN server be bypassed entirely by having the ports open on the server and setting up WebRTC as a client-server model where only ports would need to be opened on the server?
Well, the TURN server is used when the “hole punching” fails to work, as it can happen with some routers and some router configurations. Here is where the user needs this TURN server. If you open the ports on your router, beforehand, you of course don’t need STUN (no “hole punching”, since the ports are already open) and you don’t need TURN (since the connections can be “direct” and so no need for the relay), but if you do so… Why the need to use WebRTC??? You could directly connect the browser to the NX server on the other side and connect through the opened ports! Clear the reason you need WebRTC, STUN and TURN? To not have to open the ports on your router!
Looking at your server.cfg, it does not show TURN as configured. What’s missing is this part:
Section “TURN”
Host
Port
User
PasswordEndSection
Take a look at the article “How to configure NoMachine servers to use WebRTC “.
https://kb.nomachine.com/AR07N00892Please do the configuration of WebRTC as documented there. You have the STUN server as you need, you have the TURN server as you must have, you miss nothing! It should work! Let us know 🙂