Forum Replies Created
-
Posts
-
Hi, thanks for submitting your feedback. The connection links in the !M in the tray were present in earlier versions, preceding v7. When we released NoMachine 7 we redesigned the interface in order to make the opening of, and access to, multiple sessions faster because this is the most common use we have found amongst our users and what our users asked us for more frequently. The connection links were removed from the systray to put these recent connections in the Machines panel which can be reached in two clicks (one click on the monitor, one click on ‘Main window’). This, by the way, also allows us to declutter the !M icon: a space that we need as we move forward with our development roadmap.
Hi, I’m assuming you have the latest NoMachine packages on both sides, player and server. An issue on Mac and related to external keyboards was fixed a few releases ago.
You can read more about it here:
Some keys are not correctly mapped on a Macbook external keyboard
https://kb.nomachine.com/TR02V11091If you are experiencing the issue on an external keyboard, the workaround is to change the following key in the player.cfg:
<option key="Ignore the keyboard physical layout" value="true" />. Exit the player first, make the change, save and then reopen the player and start your connection.NoMachine removes the public key when node/server (with nodedel/serverdel) are removed provided one can reach the other. For example, when the node is removed from the server, but that node is unreachable, the public key of the server will be left on the node host. The node will still be deleted. In the case of inverse connection, the
nxserver --serverdelwill connect to the server and remove the node’s public key, but if the server is unreachable when the command is run, then the public key will not be removed. The server will still be deleted. When I say “unreachable” it can mean the server/node is missing or stopped, or the connection between the two has been interrupted for whatever reason.All connections are encrypted using SSL, you can read more about this in our detailed article about security: https://kb.nomachine.com/AR04S01121
Hi, everything works correctly in our labs and following the same steps you took. Are you sure you are not connecting to a different machine?
It could be related to the NoMachine USB drivers. Please disable them using the instructions here
https://kb.nomachine.com/AR12O00955.Does that help?
DefaultDesktopCommand "/usr/bin/startxfce4"works for us.You could be having issues with dbus. Try this instead:
DefaultDesktopCommand "/usr/bin/dbus-launch --exit-with-session /usr/bin/startxfce4"Hi, we need to see the logs from the host you are connecting to. Use the automatic procedure here: https://kb.nomachine.com/DT07S00243. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
The logs were not from the server unfortunately which is what we need in this case.
First, please try disabling hardware decoding on the computer you are connecting from when you encounter this issue. The instructions on how to do that are here: https://kb.nomachine.com/AR07U01202 but I will paste them here for convenience.
Exit the Player by going to the !M icon in the system tray and selecting “Quit NoMachine player”.
Edit the player.cfg file in the user’s home on the client side.
This file is:
$HOME/.nx/config/player.cfg on Linux and macOS and %USERPROFILE%\.nx\config\player.cfg on Windows.Edit the “Enable hardware accelerated decoding” key and set the value to ‘disabled’.
For example:
<option key="Enable hardware accelerated decoding" value="disabled" />Then open NoMachine again and connect to the problematic Linux host. Is there any change?
If that does not help, then we will require the full logs from the problematic server side with debug enabled. If I’ve understand you correctly, this is the Linux Mint 21.3 host. You can extract them using the automatic procedure here: https://kb.nomachine.com/DT07S00243. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Strange, the workaround works for us using Brave. – xset r off must be set locally on the side you are connecting from, not inside the session.
Hi, in the logs you provided there were no agent logs which would have been useful.
Please enable debug level using the automatic procedure before reproducing the issue and gathering a new full set of logs. Instructions on how to do this are available here: https://kb.nomachine.com/DT07S00243
The nx* log entries in the syslog would also be useful. There were no *nx entries in the journalctl you attached.
journalctl -b -0 | grep -i "nxserver\|nxnode\|nxwebplayer" > journalctl.extractor:
grep "nxserver\|nxnode\|nxwebplayer" /var/log/SYSLOGFILE > syslog.extractwhere SYSLOGFILE is the system log file.
Send everything to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.
just to clarify, by installing one Enterprise Desktop on a host, unlimited connections can connect to its physical display. Purchasing a pack of ED gives you 10 subscriptions, one subscription per machine you want to access. Unlimited connections to each of the ED hosts.
We don’t provide an SDK to do what you are describing. What you could try is to explore the OS and framework API to look for a way to grab windows content and paint it on your application, maybe?
In theory you should be able to connect because you stated that you are actually logged in. If you had locked it and logged out, it would be impossible to connect. What is the error (or errors) you are seeing by NoMachine when you try to connect?
Also logs from both machines would be useful. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243 and gather the logs. Please submit them to forum[at]nomachine[dot]com.