Forum Replies Created
It’s look that you have different architecture than the one you have installed. You can check architecture with command:
if it’s v8 – uninstall current version
sudo dpkg --purge nomachine && sudo rm -rf /usr/NX
and install correct package.
Are you always creating a new connection file? In that case it would always show windows for “remote audio alert message” and “remote display resize message”. You can check “Don’t show this message again” and it won’t show anymore in this connection file.
There is also method to configure every host which you want to connect. Edit as administrator server.cfg and uncomment and change following key to this:
(point 2 in https://www.nomachine.com/AR11O00951).
We also recommend to update NoMachine to newest version.
Did you tried to set also
DisplayServerExtraOptions "-wlmode compositor"in the /usr/NX/etc/node.cfg? We didn’t have problems with desktop detection when Wayland is enabled. Did you use custom wayland configuration or enable some extensions? Can you try with default settings.
It looks it’s the same problem mentioned on that post:
Please try workaround from @shiba
auth include system-login account include system-login password include system-login session include system-login
and change DefaultDesktopCommand value in
DefaultDesktopCommand "/etc/gdm/Xsession 'env XDG_SESSION_TYPE=x11 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus gnome-session'"
There is workaround for this problem (https://forums.nomachine.com/topic/connection-fails-on-headless-client#post-21783):
1. Create a backup of nx PAM configuration (
sudo cp -a /etc/pam.d/nx /etc/pam.d/nx.original). Then change /etc/pam.d/nx in this way:
auth include system-login account include system-login password include system-login session include system-loginOctober 1, 2020 at 14:49 in reply to: Router on double-NAT – Can’t get external IP for remote connections #29749
Buying new router is not necessary. Just check port forwarding. In link from previous post you have instructions. just use local IP from machine with nxserver and use port 4000. Then check your external IP on https://www.whatismyip.com/ and then use that IP and port 4000 on client side to connect.September 30, 2020 at 18:24 in reply to: Router on double-NAT – Can’t get external IP for remote connections #29736
It appears that Upnp is not supported on your router.
However you could try forward port manually. To do that you should pass traffic to port 4000 (NX protocol), 22 (SSH protocol on Linux/MacOSX). Follow your router instruction to know how to configure that (guide you can also find in the internet, for example from there: https://portforward.com/apple/airport-extreme/). Your external address you can find for example there: https://www.whatismyip.com/.
Please send also backtrace to get detailed information.
sudo gdb -c [core-file-nxplayer-path] /usr/NX/bin/nxplayer.bin
Inside gdb program execute command
thread apply all bt fulland paste output here or attach in the text file.September 1, 2020 at 16:21 in reply to: Cannot connect to remote server because I need local port mapping too? #29290
Are you sure that IP is correct? Can you ping DMZ device from that network at all? Please check connection from other network to exclude tethering problems.
Can you send backtrace from the core? Instructions for your system you can find there: https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces. Please send also output of the command:
If you want to connect locally you don’t need the internet. You don’t need configure nothing in the router. Just install NoMachine. Internet is required for automatic update, which you can easily disable (https://www.nomachine.com/DT10O00149#2).
In addition, if you use NoMachine free version, Workstation or Small Business Server, you can disable UPnP, which allows external access (go to “Disabling UPnP / NAT-PMP port mapping” section on article: https://www.nomachine.com/AR11L00827).July 7, 2020 at 13:29 in reply to: Plank taskbar not opening when NoMachine creates a virtual display #28438
You need to edit /usr/NX/etc/node.cfg and change command starting virtual desktop to this:
DefaultDesktopCommand "env XDG_SESSION_TYPE=x11 /usr/bin/ssh-agent /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/budgie-desktop"
Please enable debug, restart nxserver (sudo /etc/NX/nxserver –restart) and execute those commands: sudo /etc/NX/nxserver –upnpstatus and sudo /etc/NX/nxserver –upnpmap. Send logs to forum[at]nomachine[dot]com. There is instruction how to enable and collect debug logs automatically: https://www.nomachine.com/
One other thing that I have noticed that may or may not be normal but I have NX directories in both my /etc and /usr directories.
Directory /etc/NX contains configuration files, do not remove them – it would prevent NoMachine from working properly.July 1, 2020 at 12:33 in reply to: Xfce4-panel customisation on NoMachine Terminal Server Linux #28352
This is default XFCE4 configuration and it’s not related to NoMachine.
Please use command:
sudo cp /etc/xdg/xfce4/panel/default.xml /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xmlto create default panel layout without the prompt.