Forum Replies Created
-
Posts
-
Hi, setting the key to 60s should be enough. If it’s not it could suggest something is wrong with your configuration. Additional debugging can be done but not via the forums. One of the team will contact you to provide further instructions.
Please update to the latest maintenance release:
https://forums.nomachine.com/topic/nomachine-8-1-2-now-available-for-download
NoMachine 8 is a universal package for both Intel and M1.
Please update to the latest maintenance release:
https://forums.nomachine.com/topic/nomachine-8-1-2-now-available-for-download
Please update to the latest maintenance release:
https://forums.nomachine.com/topic/nomachine-8-1-2-now-available-for-download
I’m looking forward to this being corrected
Although we will be releasing a maintenance shortly (keep your eyes peeled for that) the change we mentioned will be in one of the next upcoming updates.
When you are speaking about UPnP you are speaking about the mapping of the port to the router via UPnP (just to clarify for other users who might be reading 🙂 )
When the nxserver starts up and it makes the request to the router according to how you’ve set up port-mapping, it can some time before the router responds. In our tests, there were some specific models that can take up to 9 minutes before responding back to the server. In the current version, during this time, the player asks the server to confirm the upnpstatus but the nxserver is still waiting for the router to answer. You will probably see that if you leave the Ports panel open, it will update itself after a few minutes (because the nxserver has received a response from the router).
In the next update we will change this behaviour between server and player. The server will tell the player that the setting is activated (or not) even though it is still waiting for the router to respond. This should remove the need to have to manually change it every time.
https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Client
From the Menu of the website -> Download -> NoMachine Enterprise Products Evaluation -> Scroll down to the product you are looking for 🙂
We received the output and logs that we requested. Thanks for those.
From that we can see there is a crash of Xorg and looks similar to an issue we saw on version 7 which was related to how X server “goes offscreen”, not caused by the NoMachine software itself.Just to make sure it indeed is that, can you try disabling the blanking of the screen on the Ubuntu server?
open the NoMachine UI on the remote host -> Settings -> Server -> Security and uncheck the ‘Blank the physical screen when somebody connects’ option.Also, we see that you have lock screen at disconnection disabled. Confirm that indeed it is (it’s in the same Security panel as above).
Hi, this happens because NoMachine no longer has accessibility permissions. If you’ve updated from version 7 to version 8 of the NoMachine software, you will need re-enable permissions in the macOS security and privacy section.
Open macOS Settings -> Security & Privacy -> Privacy and add ‘nxnode’ to the list of applications allowed in the accessibility list. If nxnode is already listed, remove and re-add it.
Please submit the logs as requested.
How to gather debug logs for support requests
https://kb.nomachine.com/AR07K00677It would also be a good idea to update to the latest version of NoMachine if you are still on v7.
Edit: Topic about sound is solved. A new topic is required if another issue is found.
Hi,
we are aware of a similar issue and a possible workaround (which will be released in the next available maintenance) is to start the client with the following Terminal command:
DISPLAY=localhost:0.0 open -a NoMachineLet us know if this helps.
Hi,
it looks like
nexexec --authis timing out. Try extending the timeout in the following key available in the server.cfg file#
# Set for how long the server will wait for the authentication phase
# to be completed on the system. By default timeout is set to 30
# seconds. Increase this value when the authentication process on
# the system takes longer. This setting applies also to two-factor
# authentication.
#
#AuthorizationTimeout 30