Forum Replies Created
-
Posts
-
To add the node, run
sudo /etc/NX/nxserver --keyadd /home/user/node.localhost.id_rsa.pub. We create /var/NX/nx/.nx/config/autorized.crt during the nodeadd procedure. It seems you were writing your last reply whilst I was writing mine, so take a look at the article I linked and follow the instructions there.Hi, it’s impossible given that NoMachine encrypts all traffic end to end, including X11 protocol when used. You can take a look at the following article which explains how NoMachine handles security and encryption, https://kb.nomachine.com/AR04S01121. Some other pointers can be found in this article https://kb.nomachine.com/AR11K00745 published at the time we transitioned away from our legacy version.
Gary, you did not submit the logs from the server side, i.e the Ubuntu machine. Enable debug on the Ubuntu machine, reproduce the problem, then gather the logs (https://kb.nomachine.com/DT07S00243).
Journalctl logs would be helpful as well.
Try changing the DefaultDesktopCommand key in node.cfg on the server by adding the
--disable-acceleration-checkoption to the gnome-session command, e.g.:DefaultDesktopCommand "dbus-launch –exit-with-session gnome-session –session=ubuntu --disable-acceleration-check"In general, when adding a node to the cloud server, you don’t have to copy any key, the procedure to add the node will propagate the key for the node to use. To do that, you need the admin credentials on the node, the Terminal Server host in your case.
However, when you don’t have admin permissions on the node you want to add, for example there are two separate administrators for both machines, you can indeed pass the CS public key to the admin of the TS Node, and they can place it in the appropriate directory. On Linux, the public key can be found in the directory, for example in /usr/NX/etc/keys/node.localhost.id_rsa.pub. You, the CS admin, can then proceed to add the node to the Cloud Server with sudo /etc/NX/nxserver –nodeadd IP_of_node –node-name name_of_node.
See the article here: https://www.nomachine.com/AR11V01258.
Propagation of EnableDirectConnections to all of a Cloud Server’s nodes is not currently possible. I’ve already passed this request on to our R&D team in the meantime.
If you are connecting to the physical desktop of the remote machine, you can set the following key in the in the node configuration file (/usr/NX/etc/node.cfg) on the server side to auto-disconnect after a specific amount of time.
DisplayAgentExtraOptions “-timeout 600”
For reference, check this article: https://kb.nomachine.com/AR01H00551
Are you able to send us the logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. It would be useful to have both the client (step 4 in the document) not just server side logs.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
We had a similar report a while back, you could be encountering the same problem. It is Raspberry which is reporting the wrong information. In checking the latest image of Raspberry Pi OSarmv7 (Bookworm), there is a 64-bit kernel. This is why uname -m command shows aarch64. However, the libraries in Bookwork are for armv7 and so you could try installing a NoMachine package for armv7.
Hello, we already do. Supported key types in NX and SSH connections are RSA, DSA, ECDSA and ED25519. For web connections, the RSA key type is supported.
Hi, are these all Mac machines? It would help to know the exact OS version of the computer you are connecting from when you experience this and to which OS version you are trying to reach.
Q1- Where can I find the fingerprint on the server to check it ?
openssl x509 -noout -sha256 -inform pem -fingerprint -in /usr/NX/etc/keys/host/nx_host_rsa_key.crt
Q2- Could you confirm all is OK with this manual procedure ?
Yes, it is a standard procedure to pre-configure client’s hosts.
Understood. The name given there is actually the name of the session file. In the current version, the name of the connection is displayed in the caption instead of the hostname or the name of the node. This is the standard default behaviour across all products. To distinguish among the nodes you could create one connection for each node, give it the node name and save it. Be sure to check the ‘Save the selected node in the connection file’ option.
For a future version we already have planned the possibility to add the option to display the node name in the client window caption with Cloud Server set-ups. On the basis of your requirements, should it be optional or should it be the default standard?
The caption could be something similar to this:
<session name> (<node name>) - NoMachine <session name> (<node name> via <CS name>) - NoMachine (for multi-level only, show node parent name)I imagine this would this satisfy your requirement, but if you have another idea, by all means we will be happy to evaluate your suggestion.
NoMachine is not a password manager. Stored credentials are scrambled and you can read more about this in the following article: https://kb.nomachine.com/AR01C00125