Forum Replies Created
We checked in our labs here, and we have no problem with connections when NordVPN is also running. Did you try the connection to the correct IP? The MDNS port might be blocked so broadcasting host in the network won’t work in the player, but it is still possible to connect using IP address.
Logs indicate that you are trying to use VirtualGL. There are instructions how to enable it on the NoMachine: https://kb.nomachine.com/AR05P00982. After enabling VirtualGL please set default command in node.cfg:
DefaultDesktopCommand "env XDG_SESSION_TYPE=x11 /bin/dbus-launch --exit-with-session gnome-session --session=gnome"
We were able to reproduce the problem on Chromium on physical display (on x.org desktop) without NoMachine which means that this is not a bug in NoMachine.
It looks like you are trying to connect over the internet to the server host. Port 4000 can be used in local connections, but if you want to use it in the connection from external network – you need to open that port on the router manually. More info about how to connect over internet you can find there: https://kb.nomachine.com/AR10R01099
We couldn’t reproduce such problem. What OS is on client side? Which NoMachine version is installed on both sides? What resolution is on server host? Is this connection to the physical desktop? Is there “Resize remote display” option enabled in the player? Did you change some display options in the player during connection?
According to the RPi documentation – dtoverlay option requests the firmware to load a named Device Tree overlay – a configuration file that can enable kernel support for built-in and external hardware (https://www.raspberrypi.com/documentation/computers/configuration.html#part3.1).
Try to set the older driver:
and let us know if you see the difference.
why can’t I update the NoMachine server on a remote desktop anymore?
It has never been possible to run the software updates in a virtual desktop session. Software updates need to download new files and run the procedure to activate them. Part of this procedure consists in shutting down the nxserver, applying changes, restarting the nxserver. This could not work in a virtual desktop, when shutting down the server the session would be closed and the procedure would break.
On a headless machine the same conditions apply. With no X server running or detected, NoMachine start it’s own virtual display. Updating the nxserver, it must shut down and therefore the session is interrupted.
You can download and update NoMachine via command line with those commands:
wget https://www.nomachine.com/free/linux/64/rpm -O nomachine_7.10.1_1_x86_64.rpm sudo rpm -U nomachine_7.10.1_1_x86_64.rpm
Everything you need to know is the following document in our knowledge base which gives multiple examples of what and how to configure specific items of the player.cfg and session file. Please see:
Additional information about storing the password is available here. https://kb.nomachine.com/AR01C00125
<option key="SSH Client" value="/usr/bin/ssh" />can be used to change the path to the native client. So if you want to change the env, you can create a script to do this and then spawn the ssh process by using the path of the script as the value.
First of all close all nxplayer processes with button “Quit NoMachine player” which you can find by clicking on NoMachine icon on the system tray. This is needed to save changes in player.cfg. Configuration file you can find in
~/.nx/config/player.cfg. Key which you are looking for is “SSH client mode”. Change value from “library” to “native”. The line should look like this:
<option key="SSH client mode" value="native" />June 13, 2022 at 09:24 in reply to: Cannot find the default enviroment when running without a GPU or display-manager #38850
Hi, as you probably read in the article you referenced, NoMachine is able to detect when the X server is not running and run its own virtual display, which is an embedded X server. If you don’t have an integrated graphics card or VGA port, NoMachine cannot detect an X server and thus launches its own “virtual desktop”. If there is a GPU, and so a physical X session is already running, NoMachine doesn’t need to run its own display to launch the desktop environment.
That said, Ubuntu 22.04 doesn’t make available by default the command used by NoMachine to launch the desktop inside our virtual display. We will be making the necessary adjustments in an upcoming software update. In the meantime, please check one of these methods and let us know if it helps:
I) install dbus-x11 package:
sudo apt install dbus-x11
II) set /usr/NX/etc/node.cfg key?
DefaultDesktopCommand “dbus-run-session gnome-session --session=ubuntu”
What is your username for the computer you are accessing? This “username” is what you should write here: C:\Users\HERE\.nx\cache
Folder “.nx” is hidden, you can set File browser to show hidden items or just paste C:\Users\PASTE-HERE-USERNAME\.nx\cache path in navigation bar in the File browser.
Also in the home directory – C:\Users\your_username\.nx
You don’t have to change IP manually. It will change automatically after few seconds. Problem is that it looks that you already entered IP manually and it’s saved permanently in connection file now. You can remove that change with editing .nxs (probably last file in the:
~/.nx/cache/) on client side. Find line with key “Server host” and delete IP value like here:
<option key=”Server host” value=”” />
Is NoMachine currently do not use systems-login daemon?
NoMachine don’t use systems-login daemon.
If there is a need we could propose some custom script that would set Idlehint=yes, for example with this command:
dbus-send --system --print-reply --dest=org.freedesktop.login1 /org/freedesktop/login1/session/c21 "org.freedesktop.login1.Session.SetIdleHint" boolean:true
(where c21 is ID of your session).
You should revert changes – it looks it’s indeed script, not a file with keys. Are you using physical desktop? If yes – agent forwarding won’t work. Agent forwarding option can be used on virtual and custom sessions (even already existed).