Forum Replies Created
-
Posts
-
Hi, the name of the product can be obtained either by running from command line
nxserver --versionor from the /etc folder which contains the server.lic file (which will show you the name of the installed product).It was working in the morning & early afternoon and suddenly stopped working.
Please update to the latest version and if the issue reoccurs, submit the logs from the NoMachine server side. Send them to forum[at]nomachine[dot]com.
We were able to reproduce similar behaviour and have opened an internal Trouble Report for the moment. The problem appears on Squid3 configuration on newer systems (reproduced on Squid configured on Ubuntu 20.04 and Redhat 8) and can be reproduced with both NX and SSH protocols. Settings without username and password authetication work fine. The exact same Squid3 proxy with password configuration set on Ubuntu 12.04 works fine with NoMachine. The fix will be made available in the upcoming v8.
We are not aware of similar issues on Debian 11.
The “S-log” excerpts you pasted are not from NoMachine. If you have an NX legacy or derivative installed on that machine, or had it installed, I would suggest to uninstall NoMachine and remove all traces including the home, reinstall NoMachine and start again, making sure that you’ve also removed any trace of what other product you might have had (even inadvertently) on that machine.
sudo dpkg --purge nomachine sudo rm -rf /usr/NX /etc/NX /var/NX .nxThen reinstall the NoMachine product of your choice.
You should check server-side logs (which are in /usr/NX/var/log) – not client.
For your reference:
Collect server side logs automatically
https://kb.nomachine.com/DT11R00182or
Collect server and client logs manually
https://kb.nomachine.com/DT11R00181Default Ubuntu 20.04 installs and works out-of-the-box in our labs.
Are you running Wayland and is it a VM? If so, take a look at this article and follow the tips there:
Connecting to a Wayland-based desktop running in a Linux virtual machine
https://kb.nomachine.com/AR04R01083You could also log out and then log in, but to a X.org desktop. This will show whether the problem is Wayland or not.
Send the logs by all means, we can take a look and see what’s going on. Please send them to forum[at]nomachine[dot]com making sure to put the title of your topic as the subject of your email. Thanks!
The output shows that PulseAudio libs are present but not that PulseAudio is installed and being used. Fedora 36 now adopts Pipewire instead of PulseAudio and it is likely that it is using those libraries.
https://fedoraproject.org/wiki/Changes/DefaultPipeWire
Support for Pipewire in NoMachine will be added in v8.
So first install PulseAudio:
sudo dnf install pulseaudioFedora will ask you to remove Pipewire and replace it with PulseAudio. Then you can install NoMachine again or use command from installation output:
/usr/NX/scripts/setup/nxnode --audiosetup <path>to configure PulseAudio with NoMachine.
Hi, thanks for reporting this. We’ve also reproduced it on the iPadOS 16 beta. We will queue up for fixing in our next mobile release.
Can you please submit the screenshots as separate attachments? They won’t be accepted if you try to paste them in to your reply. Thanks.
Hi, please check this topic here which deals with the same message.
First, can you check that the correct permissions are set on the Mac computer? Here you can find some further hints: https://knowledgebase.nomachine.com/AR09S01139. In some cases, after a OS update, it might be necessary to remove (uncheck) the permissions and grant again.
If that doesn’t help, it could be the same issue we are already aware of and will be fixed in the next software release, version 8. A restart of the nxserver on the Mac machine can sometimes help.
After you’ve tried this, what happens?
Hi, the available resolutions in the Display settings of the connection menu are those which are supported by your OS’s system configuration. Therefore, and provided I’ve understood what you are trying to achieve, what you need to do is change the orientation on your Windows machine to allow NoMachine to show the content in portait mode.
See this page on the Microsoft website:
https://support.microsoft.com/en-us/windows/change-screen-orientation-f7ab1ff8-971d-58a5-b8ee-bc113bbf3acb#WindowsVersion=Windows_10Does this help?