Forum Replies Created
-
Posts
-
Hello Alexander,
Are there differences between running it on one server and two or more servers?
NoMachine Cloud Server provides multi-node support with load balancing. By adding the remote nodes we can balance CPU usage between hosts.
Does NoMachine provide something to help lock down the linux environment in a way that locks the user into that particular application (so that the user is not able to run other commands)?
NoMachine does not provide a way to lock down a user on the system. It provides however some methods to disable certain features (e.g. copy&paste and file transfer). It’s also possible to use users’ profiles for implementing a solution that can be suitable for your purposes.
By defining a set of rules you can define which application each user is allowed to run on that host. The connected user will be then able to run only this program via NoMachine.Is there a way to automatically shut down a session if some timeout happens (e.g. no mouse is moved and the application is not performing any time-consuming task)?
NoMachine does not provide such solution. We actually want to preserve user session as long as possible to make them accessible in any time. We have Feature Request that should be released soon, that will terminate ‘long disconnected session’: https://www.nomachine.com/FR07D01435
Also you could configure NoMachine Server to terminate session right after user is disconnected.How does it work with the new high-DPI monitors?
I am not aware of any issues with new high-DPI monitors. But please check this Feature Request ‘Adding an option
to use native resolution on High-DPI displays’:
https://www.nomachine.com/FR02M02864Hello Ravi,
We will need debug NoMachine server logs to investigate further. Please follow the instructions here:
https://www.nomachine.com/AR07K00677
Send them to issues[at]nomachine[dot]comAfter enable debug logs on problematic machine please execute:
/etc/NX/nxserver --restart
and after that try to reproduce the issue.Additionally please provide files from the server machine:
/Applications/NoMachine.app/Contents/Frameworks/etc/server.cfg /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfghello ravikanthuppu,
Please check the following keys:VirtualDesktopSharing PhysicalDesktopSharingin file:
/Applications/NoMachine.app/Contents/Frameworks/etc/server.cfgBoth keys should be enabled to provide access to physical session.
Hello bmanning81,
We will need debug NoMachine server logs to investigate further. Please follow the instructions here:
https://www.nomachine.com/AR07K00677
Send them to issues[at]nomachine[dot]comPlease execute:
/etc/NX/nxserver --restart
before reproducing the issue.Hello Maurice,
Thank you for your logs. We found that we the problem lies with
connecting NX application directly to session display. We need
NX application working directory to investigate further.The logs are stored in /sdcard/.nx directory. Extracting logs
mostly depends from tools installed on the device. You can enter
in the last R- directory under /sdcard/.nx and for example share
the files, or compress the directory and share the archiveHello vstubbs,
Thank you for sending the logs. We found serious issues with installation reported from both machines. Some of them are:Subscription file /usr/NX/etc/server.lic has wrong permissions. Correct permissions are 0400 Cannot open lock file '/usr/NX/etc/nodes.db.lock': Permission denied Initialization: Cannot open file /usr/NX/etc/server.cfg: No such file or directoryWe suggest to uninstall NoMachine software, remove the /usr/NX/ directory and proceed with a fresh install.
Hello Maurice,
Thank you for your logs. Unfortunately I did not find where exactly issues is.To investigate further, the nxagent directory is required. Please go back to
previous debug logs request and before reproducing the issue make sure that
key ‘SessionLogClean’ is set to 0 in node.cfg. In your <home directory>/.nx/
directory will appear directories with name beginning with: T-C-.Than please send full set of logs to issues[at]nomachine[dot]com again.
Hello jxg134630,
It is not possible to reboot multi-node server machine without disconnecting users. But if session was created on the remote node machine then user will be able to reconnect to the session after reboot.Hello joe.gly,
We have identified this issue and have opened a Trouble Report:
https://www.nomachine.com/TR01M04875As a temporary workaround please remove your remote node and add it again:
/etc/NX/nxserver --nodedel <remote node> /etc/NX/nxserver --nodeadd <remote node>Hello ponch,
NoMachine require associating local IP address 127.0.0.1 with localhost hostname.
Please check if you can (temporarily) set the value for localhost to ‘127.0.0.1’ in ‘/etc/hosts’ file on the troublesome server.
Then after restart of nxserver it should be possible to establish sessions.If the issue persists please gather debug information following the instructions here:
https://www.nomachine.com/AR07K00677
Send them to issues[at]nomachine[dot]com with your ‘/etc/hosts’ file.Hello maurice,
We will need debug NoMachine server logs to investigate further. Please follow the instructions here:
https://www.nomachine.com/AR07K00677
Send them to issues[at]nomachine[dot]comHello joe.gly,
We have identified the issue and have opened a Trouble Report:
https://www.nomachine.com/TR01M04838
Please also check the latest release. A patch was included.Hello dhfx,
To investigate further we need output of command:
/etc/NX/nxserver --history
and debug logs gathered by following the instructions here:
https://www.nomachine.com/AR07K00677
Send them to issues[at]nomachine[dot]comPlease execute:
/etc/NX/nxserver --restart
before reproducing the issue.hello omsi,
Attached logs show issue with NoMachine license but not on machine that you are trying to connect to, but on local host.You can verify this issue by executing:
nxserver.exe –subscription
nxserver.exe –versionIf you need some help with finding the reason of that issue send us logs from local machine. Please follow the instructions here:
https://www.nomachine.com/AR07K00677
Send them to issues[at]nomachine[dot]comAbout the issue with connecting to remote machine:
NoMachine nxplayer failed to connect to ’5.9.39.150′ and returns error: Connection timed out. It could be due to issue with accessing port 4000 on that machine. In this case you should check router configuration if port 4000 is forwarded to the proper machine.The NoMachine server logs from Windows would be useful.
Please follow the instructions here:
https://www.nomachine.com/AR07K00677
Send them to issues[at]nomachine[dot]comIt seems to be the same issue already reported in this TR: https://www.nomachine.com/TR10L04643.
You can sign up to receive notification of the patch when it is released (most likely in the next update).