![native access waiting for connection native access waiting for connection](https://assets-global.website-files.com/63e4f18529ade514137147bd/65ddfdd4ccf59aa099681025_DEFI_DARP_BlackBG.png)
With what you provided it is clear that there is something wrong. The same thing happens if I use the other user’s credentials for NX login in the client.Īs I wrote, the only solution to the problem is to setĪs I wrote before, as there was not enough information to make any reasonable guess, this is how this key is supposed to work. In the logs I don’t see any obvious problem. Session: Session started at Fri May 29 16:39:07 2020. Info: Display server started with pid 1417.
![native access waiting for connection native access waiting for connection](https://assets.telecomtv.com/assets/telecomtv/swisscom-source-swisscom-17940.jpg)
Info: Audio client started with pid 1416. Info: Audio server started with pid 1415. Info: Listening to slave connections on port 12001. Info: Slave server running with pid 1400. Session: Starting session at Fri May 29 16:39:06 2020. Info: Accepting connections from any host with encryption enabled. Info: Listening for connections on any interface on port 4000. Info: Handler with pid 1674 terminated on Fri May 29 16:40:49 2020. Info: Handler started with pid 1674 on Fri May 29 16:40:35 2020. Here are the NX log records I found about the session (after logged in via SSH): The login to the NX server was successful but then the client displayed “Waiting for the desktop user to authorize your connection” although there was no desktop user logged in. It is running the free version of NoMachine for Linux 6.10.12.Īfter rebooting the machine I tried to connect to it with NoMachine Enterprise Client 6.10.12. I’ve done some more testing on the Ubuntu 20.04 machine which has only two ordinary users (with UID >= 1000).