Forum Replies Created
-
Posts
-
Hi, can we see server logs, journalctl output, and additionally xrandr output before and after the NoMachine connection?
To get NoMachine server logs, please follow the instructions here and send to forum[at]nomachine[dot]com using “Cannot restore X11/KDE resolution after disconnecting” as the title.
https://kb.nomachine.com/DT07S00243
Thanks.
Hi Nuertey, send it to forum[at]nomachine[dot]com. There must be a character in the file that is clashing with our filter.
Thanks for your report. We will investigate what can be done from our side. Have you reached out to Wacom as well?
Hi, the logs didn’t attach, please send them direct to forum[at]nomachine[dot]com. You can reply to our email which asked you to update to the most recent version of NoMachine 🙂
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.