Forum Replies Created
to control NX server behaviour in that case, please use server’s configuration key:
The meaning of that value, and also other possibilities to set are below
# # Configure the NX Server behavior when the maximum number of allowed # connections is reached. An already connected user can be asked to # accept or refuse to disconnect to make room for the incoming user # (this is the default), or can be automatically disconnected or # never disconnected. # # 0: Disabled. The server prompts the connected user to accept or # refuse to disconnect for making room for the incoming user. If # no choice is made, the user is automatically disconnected. # # 1: Enabled. The server automatically disconnects the connected user # to make room for the connecting user. No message is issued to # the already connected user. # # 2: None. The server prompts the connected user to accept or # refuse to disconnect for making room for the incoming user. If # no choice is made, the server doesn't disconnect the user and # advise the incoming user that the maximum number of allowed # connections is reached. # # 3: Silent. The server never notifies desktop owners about incoming # users, incoming users are informed that the maximum number of # allowed connections is reached. # #AutomaticDisconnection 0
did you try the last one as set key PhysicalDisplays to value “:900” in /usr/NX/etc/node.cfg on server,
and then restart it (sudo /etc/NX/nxserver –restart) ?
Please share new logs, config files if you modified them also.
Your logs from version 6 and version 7 show the different behaviours of the two versions: Nxserver v6 was not able to find a physical session, so its started a frame buffer session.
In the case of V7, you have access to the normal physical session, and there is no reason for NoMachine to start a frame buffer session.
To have the same behaviour as you had with V6, you have a wide range of possibilities, as you can configure your desktop manager to automatically log you in to the physical desktop – or disable the desktop manager at all.
You can also set the PhysicalDisplays key to value “:900” in the node configuration file, to make sure that the nxserver will not be able to find a physical desktop. It will then start a frame buffer session as it does in V6.
the main difference is that
run daemon and then is waiting for it to be ready.
/etc/NX/nxserver --startupinstead of other commands
you will be sure that sleep is not needed anymore.December 21, 2020 at 17:22 in reply to: Performance issue –> reboot necessary + CredentialsStoring Bug? #30839
in case of limits per user, questions are for kernel and operating systems. NX user and any other users are under kernel control. I think processes
are not simply counted as they can have many threads, and every thread is counted as well.
Resource limit is controlled by kernel, so when you have issue try to find which process has a lot of files in use, which one has a lot of threads etc
There are system tools which can help as lsof or ps.
We have a guide available at:
which contains for example answers for your question regarding where limits are set for user nx if not in limits.conf
Systemd limits are set in the following files:
For default configuration file, during installation, setup is checking what kind of system it is, what tools are available among those required etc so there is no one default config key.
If you need clear one, uninstall nx, remove .cfg and install again.November 4, 2020 at 13:43 in reply to: Disabling the creation of a new desktop but enabling the connections to existing #30202
im not sure, but maybe its enough to set limit for virtual sessions?
Its available to set in server configuration file:
# Set the maximum number of concurrent virtual desktops.
Hello, I think it’s not possible. Connection owner has always rights to his own connection – and it’s important as a network connection can be interrupted.
It seems like you are looking for a ‘guest’ feature which is already available. That way every connection is assigned to different user and the same nxplayer will be able to recognize sessions started by a specific ‘guest’.October 26, 2020 at 18:01 in reply to: Users can’t login in. Error: Not enough X resources #30069
Every session requires a set of free ports which are calculated based on DISPLAY. Increasing the display limit should increase the pool available and can avoid such problems as the on you are describing. Please, edit server.cfg (/usr/NX/etc) and set value for DisplayLimit key.
No nxserver’s restart is required. New connections will use new value.
# Set the maximum number of displays reserved for NX sessions.
If such value as 400 is not enough, and there are still problems, maybe it’s worth checking what ports are in use and change the display range. Another useful key is DisplayBase.October 26, 2020 at 17:49 in reply to: ERROR: Not enough X resources to start another session #30068
please increase display limit in server configuration file. No nxserver’s restart is required. New connections should work just after save new value in server.cfg.
# Set the maximum number of displays reserved for NX sessions.
you send logs of nxclient – .nx from userhome which is not enough to find a reason of problem appearing on your host,
please send to us logs of nxserver of the affected computer, the procedure and paths are here:
1.4. Server on Windows
[…]September 11, 2020 at 11:14 in reply to: Always create a new display on this server – allows any user to lock down system #29438
it should be noted that this ‘create display’ feature should be intended as a fallback for those cases when it is not possible to detect a graphical session running on the server.
Having a Desktop Manager installed and running correctly should make this fallback unnecessary.
As for the “Always create a new display on this server” checkbox, we agreed that such choice should be remembered on client side (and for the specific user) without causing any modification
of the cfg file on the server. Related FR: https://www.nomachine.com/FR09R04022September 7, 2020 at 08:16 in reply to: Session Negotiation Failed/Cannot create a new display #29370
there is an article about that kind of problem:
How to solve ‘session negotiation failed, application terminated prematurely’
If you’re still having issues, install ‘xterm’ and run it as desktop command (instead of gnome-session).
Then from such xterm try to run your environment command, and you should see errors or warnimg.
/bAugust 6, 2020 at 07:07 in reply to: Hostnames 32+ characters long broke SSH authentication forwarding for me #28887
there is also in node configuration file
# Specify hostname for the NoMachine node.
please set here something short and it will be used instead of long domain name.
RegardsAugust 5, 2020 at 09:33 in reply to: Hostnames 32+ characters long broke SSH authentication forwarding for me #28871
this seems to be SSH limitation rather then NX, anyway You can change #UserNXDirectoryPath in node configuration file and this way shorten path a little.