Forum Replies Created
-
Posts
-
The logs were in previous post. Is there some problem with those, do they contain correct information?
Timok, you attached the player logs 🙂 We need the server-side logs, the logs taken from the machine you are connecting to (Settings > Server > Security > button Take logs)
In the current version, when you are logged in on the player on a computer with your Network account, you have the option to “Add this machine to your machine book” when you are in the Machine book (it’s a link on the bottom right of the player). You can then log off. Then, whenever you login again to the Network service, from whichever device it is, that MId will be in your book and you can start a connection to that machine straight from the book with “Create/run a connection”.
In version 10, we will add a panel to make it easier to add the Machine Id to your Machine book. When you are logged in already on a machine and are publishing it to NoMachine Network, a new dialog will appear showing the MId and asking whether you want to add it your Machines book. You can choose to add it, or not. (you can still add it to the Machine book later if you prefer).
The other way to add a Machine Id to your book is during the creation of the connection to a target machine. From the roster where you create your connections > Add > Add connection, insert the Machine Id, click ‘Add to your Network book’ on the bottom right.
Can you send us the server logs from the server side? On the server, go to Server > Security > Take logs, save the file and send that to us.
We’ve since released NoMachine 9.5. Can you update and tell us if you are still encountering the same problem? If you are, after reproducing, go to Settings > Server > Security, and Take logs from the headless Ubuntu server. Send us the full zip file. If you prefer to send privately, send it to forum[at]nomachine[dot]com.
Users that were encountering this issue with earlier v9 installations should make sure to update to the latest 9.5.
To make sure the NoMachine logs are preserved is to edit the node.cfg file and set the key ‘UsersDirectoryPath’ to a directory that can be accessed by everyone e.g. to the main NoMachine log directory:
UsersDirectoryPath "/usr/NX/var/log/users"then ensure the directory is available for everyone:
sudo mkdir /usr/NX/var/log/users sudo chmod 777 /usr/NX/var/log/usersthen please restart NoMachine:
sudo /etc/NX/nxserver --restartand try to connect to Login Window again and collecting logs using
sudo /etc/NX/nxserver --debug --collectHi, please update to 9.5. If you are still encountering the same problem, after reproducing, go to Settings > Server > Security on the macOS machine and click Take logs. Submit to us the whole file. You can attach it here or submit to forum[at]email[dot]com. Thanks!
Hi, could you try the latest 9.5 and tell us if you still encounter the issue?
https://kb.nomachine.com/TR03X11769 – this TR was solved in the latest update.
Can you send us the logs from the server side machine? On the server, go to Server > Security > Take logs, save the file and send that to us. You can submit it here or if you prefer, you can send it to forum[at]machine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Can you send us the logs from the server side machine? On the server, go to Server > Security > Take logs, save the file and send that to us. You can submit it here or if you prefer, you can send it to forum[at]machine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Not sure what your products is so I’ll point you to one of the Terminal Server v8 guides: https://kb.nomachine.com/DT07T00259#2.3. You’ll find all the v9 guides on our support page 😉 https://www.nomachine.com/support/documents
You can also refer to this article https://knowledgebase.nomachine.com/AR10K00698
It sounds more like something is broken on the system OS. There are references in logs to ‘/run/user/60578/’ so this directory has to be present. Maybe you could investigate the user with uid 60578?