Forum Replies Created
-
Posts
-
Are you referring to https://kb.nomachine.com/TR05V11141? It has not yet been fixed.
Hi, the link is correct. Can you tell us the exact steps you took to install the package? Did you run in CLI:
$ sudo dpkg -i nomachine_8.16.1_1_amd64.debHave you tried unticking the box “Secure mode” and using the Network:Default option in the Ubiquiti firewall?
Hi, check in the mac’s Accessibility, Screen Recording and Full Disk Access that NoMachine and nxnode (a component of NoMachine) have been correctly added in the Privacy panel. Remove and add again if necessary. This article shows the panels to check: https://kb.nomachine.com/AR11Q01061. Restart the nxserver. Does that help?
Hi, it sounds very similar to this bug report.
Cannot login by NX protocol and private key when option ‘Import the private key to the connection file’ is checked
https://kb.nomachine.com/TR05S10271As a temporary workaround, do not check option ‘Import the private key to the connection file’ in the UI.
The latest 8.16 provides a patch for this. Please update your software.
Here is the Trouble Report documenting the issue: https://kb.nomachine.com/TR01W11266
The temporary workaround is to prevent the monitor from entering the sleep mode:Â open System Settings -> Lock Screen and set: ‘Turn display off when inactive’ to ‘never’. We have a patch already lined up for release and we’ve scheduled a release for this week.
Hi,
the connection windows remains white and closes in few seconds
Try disabling hardware decoding on the computer you are connecting from in the player.cfg file. To do that follow the instructions here: https://kb.nomachine.com/AR07U01202. In your case, you should choose completely disable, so option 3 (). You must quit the player first before making this change from the !M in the system tray. Then try connecting again.
Hi, closed because it is a duplicate of https://forum.nomachine.com/topic/external-ip-missing.
Hi, when connecting to a virtual Linux desktop, supported in any of the NoMachine Terminal Server products, you can maximize the session window to all monitors or one of the monitors on the client side. To enable it:
– Open the NoMachine menu panel inside the session (ctrl+alt+0 or click on the page peel in the upper right corner of the window)
– Click on ‘Display’
– Click on ‘Resize remote display’ then on ‘Fullscreen on all monitors’It’s not possible, however, to dedicate 2, 3, or 4 displays to the NoMachine session window. We could evaluate the possibility of implementing said functionality, but this would need careful consideration, so what I suggest for now is that you reach out to us through the website with some more details.
The workaround we provided is to disable Wayland, and fall back to X.org. That LabWC requires Wayland if I am not mistaken, so enabling it when you’ve disabled Wayland could cause further issues? I would not switch if I were you.
Hi, can you check whether the workaround in this Trouble Report helps?
Thanks to everyone’s comments and the logs that have come in (BerndG, nxmac, Brian). We’ll be taking a look and will come back to you if we need anything else. We’ve also reproduced the issue since I last wrote and will compare our findings with what info and log information you have all submitted, so that a fix can be found and released as soon as possible, and we can eliminate the need for …. ehem 🙂