Forum Replies Created
-
Posts
-
Hi JayMac, please check your inbox for an email from me. I have sent you a debug package with further instructions.
Hi,
does the screen that you see remain frozen forever?
Can you send us the full set of logs? Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Follow the instructions here: https://kb.nomachine.com/DT08U00298#1
Hi, multi-monitors are supported but it’s not possible to limit access to view only one. When the server has two or more monitors, an icon in the client UI (player or web player) lets the user choose which remote display to show. For example, if there are two remote monitors, the icon will let the user select whether to show the first remote display, switch to the second, or show both remote displays (more about multi-monitors is available here: https://kb.nomachine.com/AR06U01201).
My bad. I should have mentioned that after disabling egl you should logout and log back in or reboot the system. Please try that if you didn’t do that already.
Sorry Timo, I missed your last question. The fix will not be a “quirk”. We are currently working on adding full support for virtual desktops for Wayland.
Not being able to resize in this case is not caused by NoMachine. NoMachine shows you the available resolutions which are those supported by the graphics cards and the remote OS.
Hi, are you able to send us the full set of logs from the Mac machine so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298#1.1 and setting the log level to 9 (Debug) and restart the server. Reproduce the problem as per your steps, then take the logs. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hi, are you able to send us the full set of logs from the Windows machine so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298#1.1 and setting the log level to 9 (Debug) and restart the server. Reproduce the problem, then take the logs. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hi, thanks for the client side logs. Can you send us the logs from the server as well? You can get them through the UI on the Rocky server: Settings > Server > Security > Take logs, reproduce the problem first and then click Take logs.
Hi, just so it’s clear for us, if you take out Zerotier completely, are you able to connect from PCs 2 and 3 to PC 4 at all? We’ll check out ZT again in any case.
In the meantime, what you could try is, in the server.cfg file, to set the IP address which has to be broadcast by uncommenting the following key:
#
# Specify the network interface where the NX service will be bound.
# Populate the field with an IP address or a domain name.
#
#NXdListenAddress “”Restart the nxserver after making the changes.
Logs show that the older libnxegl is being loaded. Did you reboot after updating? Logging out and logging back in on the physical desktop can work as well, but a reboot can fix it.
If after rebooting you still get the white screen, we’ll need new logs.
Good to know it’s working. We got the logs, but the agent logs were missing. If it happens again, send us new logs. First, set ‘SessionLogClean 0’ in /usr/NX/etc/node.cfg to avoid they are automatically cleaned up.
Can you tell us if it was the reboot that worked, or did you have to set “
--eglcapture no“? It would also be useful to know, for our internal investigation, which apps were problematic. Thanks.Hi, can you send us the logs from the server machine? Set the log level to debug, restart the server, reproduce the problem, then gather the logs. Please follow the instructions here: https://kb.nomachine.com/DT08U00298#1.1. Send them to forum[at]nomachine[dot]com using the title of this topic as the subject of your email. Thanks!