Forum Replies Created
Indeed, I had NoMachine (latest release) working fine on macOS Catalina, and started having issues after I upgraded to Big Sur.
I wasn’t expecting the change in permissions after the upgrade, which caused me to wrongly assume there could be an interoperability issue between the latest NoMachine and Big Sur, but after I made the changes I described in my original post, it all started working again.
I did follow the steps in https://knowledgebase.nomachine.com/AR11Q01061 but ultimately what resolved the issue for me was to stop the server service and then restart it, which triggered the requests for permission for nxnode.
Thanks to the community and the NoMachine team for the wealth of information that put me in the right direction.GusParticipant
I had the same issue. What fixed it for me was to go to:
Server Settings > Status > Restart the Server
Once the server was restarted, a pop-up came up requesting permissions for “nxnode” to access Screen Recording. I allowed that and it all started working.
Worth noting that “NoMachine.app” was already listed as allowed for Screen Recording, which was triggered either during installation or first time run, I can’t recall at the moment. But “nxnode” was only triggered after I restarted the server.
Lastly, for our good folks at NoMachine to evaluate, everything had been working well for me on Big Sur and all of a sudden it stopped working. I manually added “nxnode” to Accessibility permissions too, again in addition to “NoMachine.app”, but what did the trick was restarting the server and allowing Screen Recording for nxnode.
Hope this helps!!