Forum Replies Created

Viewing 15 posts - 16 through 30 (of 70 total)
  • Author
  • zaq

    Hello david555

    Probably your problem is related to SELinux. To check this you can:

    1) temporally set permission mode

    sudo setenforce 0

    2) run NoMachine:

    sudo /etc/NX/nxserver --restart

    3) try to reproduce the problem,

    4) set SELinux’s enforce mode:

    sudo setenforce 1

    if you aren’t able to reproduce the problem, then we check deeper
    SELinux logs.

    Anyway a standard set of logs will be helpful. Gather them like is
    described in:

    and send to forum[at]nomachine[dot]com.

    in reply to: Nxserver is always disabled on SLES12 #25580

    Hello coco_jie

    We are not able to reproduce the problem in our laboratory. Could you
    give us more info please.

    Send output from commands:

    1) /etc/NX/nxserver --version

    2) ps aux | grep nx

    3) sudo /etc/NX/nxserver --startup

    and also set of logs in the way like it’s described:

    in reply to: Cannot install latest version ( on Ubuntu 16.04 #25464


    The problem is related to ‘install’ command.
    Probably the standard command was replaced by a link/wrapper to apt.
    Could you run:

    /bin/install --help

    It should looks like this:

    $ install --help
    Usage: install [OPTION]... [-T] SOURCE DEST
    or:  install [OPTION]... SOURCE... DIRECTORY
    or:  install [OPTION]... -t DIRECTORY SOURCE...
    or:  install [OPTION]... -d DIRECTORY...
    This install program copies files (often just compiled) into
    destination locations you choose........

    The default location of original ‘install’ program in Ubuntu 16.04 is:


    in reply to: Server status is not running #23277

    Hello Carlos,

    During detecting name of Administrator’s group something went wrong.
    Do you use ActiveDirctrory/LDAP/domain users?

    To investigate the problem I need output from these commands:

    net localgroup

    net user nx

    and a file adminGroup.txt from this:

    "C:\Program Files (x86)\NoMachine\bin\nxdisplay.exe" --admingroup > adminGroup.txt

    You can send the outputs and the file to forum[at]nomachine[dot]com.

    in reply to: Cannot reconnect after logout #23210

    Hello Sergey Slizovskiy,

    Generally you can install a package with the patch having only NoMachine access.

    If you are attached by NoMachine to physical session – the session is visible on physical screen. You can run terminal and install update package. You will be disconnected but after several minutes, when update finished you should be able connect again.

    If you are not sure that you are running physical session or you are running virtual NoMachine session, you can install ‘screen’ program:

    sudo apt update
    sudo apt install screen

    then run screen session -> execute in terminal:


    and in the screen session run NoMachine update:

    sudo dpkg -i nomachine_6.7.6_41_amd64.deb

    you will be disconnected, and after update finished you can connect by NoMachine again.

    As safe as updating NoMachine is, there is a risk that something totally unexpected could happen. This could affect the possibility of connecting via NoMachine.

    in reply to: How to remove NoMachine NX server? #23204


    I assume, that you have now uninstalled NoMachine.
    Please run this commands and preserve output of them:

    sudo systemctl stop nxserver.service
    sudo systemctl disable nxserver.service
    sudo rm /etc/systemd/system/nxserver.service
    sudo rm /usr/lib/systemd/system/nxserver.service
    sudo rm /etc/init.d/nxserver.service
    sudo rm /etc/init.d/nxserver
    sudo systemctl reset-failed nxserver.service

    After executed this commands if you still get the same error, please
    show us the commands output.

    in reply to: How to remove NoMachine NX server? #23173

    Hello Amivaleo

    Looks like really something went wrong during uninstallation. I think that the quickest way to solve your problem is to install again and uninstall NoMachine following the regular procedure. Please follow these steps:

    1) remove leftover dirs:

    sudo rm -rf /usr/NX /etc/NX /var/NX

    2) install again:

    sudo rpm -i nomachine_6.7.6_11_x86_64.rpm

    3) uninstall:

    sudo rpm -e nomachine

    in reply to: Cannot create the home directory for the nx user #22869


    Most possible is that you had corrupted default user profile (point 4). When you have this issue you can create a new user
    account but you can’t log in:

    in reply to: Cannot create the home directory for the nx user #22774

    Hello oussama abd

    The problem happens during creating a profile of nx user – during the first login. The system error:

    ‘NtRights: ERROR! User login failed. Error is 1385.’

    During installation preexistence of user nx wasn’t detected.
    Also he doesn’t belong to domain/Active Directory.

    1. Do you have set up any restriction related to creating and login as
    a new user?

    2. Have you changed anything in Group Policy?

    3. Do you have enabled network logon?

    4. Are you able to create and login as a new user by standard Windows
    interface? If not it can be caused by a corrupted default profile.

    5. Do you use domain/Active Directory/LDAP users profiles?

    • This reply was modified 2 years, 5 months ago by zaq.
    • This reply was modified 2 years, 5 months ago by zaq.
    • This reply was modified 2 years, 5 months ago by Britgirl.
    in reply to: NoMachine can’t open #21519


    I assume you are using Linux because you posted in the Linux forum.
    Could you tell which distro you have installed (Ubuntu, Debian, RedHat, other)?

    *.deb packages you should use for Debain, Ubuntu and similar.

    *.rpm packages are intended for: Red Hat Enterprise, SLED, SLES, Open SUSE, Mandriva, Fedora.

    *.tar.gz packages you can use for systems like Arch and others which don’t support *rpm and *deb packages.

    Is it your system headless – without graphical environment like GNOME or KDE?

    To check which package x32 or x64 you should use run this command:

    uname -a

    If in the output you got ‘x86_64’:

    Linux bee 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

    please use packages x86_64 or amd64.

    If in the output you got ‘i686’:

    Linux ubuntu-1704-32bit 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:03:14 UTC 2017 i686 i686 i686 GNU/Linux

    you should use i686 or i386 installation packages.

    In your situation I think that the best solution is completely reinstall:

    1) remove installation:

    for *.deb:

    sudo dpkg -P nomachine

    for *.rpm:

    sudo rpm -e nomachine

    for *.tar.gz

    sudo /usr/NX/scripts/setup/nxserver --uninstall

    2) removing all leftovers:

    sudo rm -rf /usr/NX /etc/NX /var/NX

    3) install again:

    *.deb x32:

    sudo dpkg -i nomachine_6.4.6_1_i386.deb

    *.deb x64:

    sudo dpkg -i nomachine_6.4.6_1_amd64.deb

    *.rpm x32:

    sudo rpm -i nomachine_6.4.6_1_i686.rpm

    *.rpm x64:

    sudo rpm -i nomachine_6.4.6_1_x86_64.rpm

    *.tar.gz x32:

    Click on Download and save the TAR.GZ file in the /usr directory.
    Extract the TAR.GZ archive by running from command line:

    sudo tar zxvf nomachine_6.4.6_1_i686.tar.gz

    Install NoMachine by executing:

    sudo /usr/NX/nxserver --install

    *.tar.gz x64:

    Click on Download and save the TAR.GZ file in the /usr directory.
    Extract the TAR.GZ archive by running from command line:

    sudo tar zxvf nomachine_6.4.6_1_x86_64.tar.gz

    Install NoMachine by executing:

    sudo /usr/NX/nxserver --install

    After that you should be able to see symbol of NoMachine in your
    system’s tray. In applications menu should be !M entires. Also
    NoMachine’s processes should be running:

    $ ps ax | grep nx
    7188 ? S< 0:00 /usr/NX/bin/nxexec –node –user john –priority realtime –mode 0 –pid 14
    7193 ? S<l 0:13 /usr/NX/bin/nxnode.bin
    7223 ? Sl 1:00 /usr/NX/bin/nxclient.bin –monitor –pid 2182
    20887 ? Ssl 5:50 /usr/NX/bin/nxserver.bin –daemon
    20998 ? Sl 0:00 /usr/NX/bin/nxd

    You can find more details here:

    If you don’t see NoMachine processes you can gather logs:

    and send them to forum[at]nomachine[dot]com.


    Hello Richcmwang,

    Looks like the error message can be triggered by adding or changing
    any *.desktop file. It isn’t caused by error in *.desktop file. You
    can easily trigger this message by changing date:

    sudo touch /usr/share/applications/firefox.desktop

    In syslog I’ve found other type of error messsages:

    gnome-software[3456]: Failed to find one package for NoMachine-base.desktop, /usr/share/applications/NoMachine-base.desktop, [0]

    You can disable them by adding to:


    these lines:


    in reply to: Enterprise Client requires admin privileges #20400


    Please download again. There was a slight hitch with the package online
    and it’s now been fixed. Sorry for any inconvenience.

    in reply to: What is the NX User account? #19878

    Looks like everything is ok. User nx is created and used by NoMachine. Also this user shouldn’t be visible in login window. Do you have other doubts?

    in reply to: What is the NX User account? #19812

    Hello Fastidious,

    Nx user is needed for proper working. You can find more in:

    However if you see user nx as available user in Login Window then please let us know and check using following command:

    sudo /usr/bin/defaults read /Library/Preferences/ HiddenUsersList

    In this case helpful will be nxinstall.log, nxupdate.log from:

    /Library/Application\ Support/NoMachine/var/log/

    Log files please send to forum[at]nomachine[dot]com.

    • This reply was modified 3 years, 1 month ago by zaq.
    in reply to: Installation fails: missing ssh keyfile #19530

    Hello Marty39

    Looks like you have Mint 64 bits and you installed a package for 32 bits:

    1. Download the x64 package:

    2. Uninstall current package:

    sudo dpkg -P nomachine

    3. Remove all leftovers:

    sudo rm -rf /usr/NX /etc/NX /var/NX

    4. Install new package:

    sudo dpkg -i nomachine_6.2.4_1_amd64.deb

    To check architecture of your machine you can use this command:

    uname -m

Viewing 15 posts - 16 through 30 (of 70 total)