Forum Replies Created
February 10, 2020 at 12:25 in reply to: Cannot install latest version (188.8.131.52) on Ubuntu 16.04 #25552
We will need your node.cfg file so we can verify if file is complete. You can find it at
/usr/NX/etc/node.cfg, then send those information to forum[at]nomachine[dot]com, please.
Also please verify if your default desktop command is set properly. First check what is the path to startxfce4 by using command
which startxfce4and then navigate to /usr/NX/etc/node.cfg and check if DefaultDesktopCommand key is set to path you got from
whichcommand. It should look similar to this:
DefaultDesktopCommand "/usr/bin/startxfce4"February 7, 2020 at 17:12 in reply to: Cannot install latest version (184.108.40.206) on Ubuntu 16.04 #25530
I was able to reproduce the issue and unfortunately previous problem caused installation damage and it is hard to fix without reinstalling NoMachine.
To completely reinstall NoMachine you need to use command
sudo dpkg --purge nomachinethen remove leftover catalog by command
rm -rf /usr/NX/and install it again. This should fix the problem with authentication.February 5, 2020 at 16:59 in reply to: Cannot install latest version (220.127.116.11) on Ubuntu 16.04 #25500
NoMachine setup is using command
installfor copying and setting files. As
installis replaced on your machine files are installing incorrectly. Please rename /bin/install to for example /bin/inst (by command
mv /bin/install /bin/inst) and try to install NoMachine again.February 4, 2020 at 16:57 in reply to: Cannot install latest version (18.104.22.168) on Ubuntu 16.04 #25476
As you can see your
installcommand is replaced by some script that is trying to use
installis a basic command used on all linux distributions for copying files and should not be replaced. To fix this issue you need to check if install command is not replaced by alias (
alias | grep installand if it’s on the list
unalias install). If it’s not replaced by alias please change name of /bin/install file and try to install NoMachine again.
install --helpcommand should look 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. If you want to download and install a ready-to-use package on a GNU/Linux system, you should instead be using a package manager like yum(1) or apt-get(1). In the first three forms, copy SOURCE to DEST or multiple SOURCE(s) to the existing DIRECTORY, while setting permission modes and owner/group. In the 4th form, create all components of the given DIRECTORY(ies). Mandatory arguments to long options are mandatory for short options too. --backup[=CONTROL] make a backup of each existing destination file -b like --backup but does not accept an argument -c (ignored) -C, --compare compare each pair of source and destination files, and in some cases, do not modify the destination at all -d, --directory treat all arguments as directory names; create all components of the specified directories -D create all leading components of DEST except the last, or all components of --target-directory, then copy SOURCE to DEST -g, --group=GROUP set group ownership, instead of process' current group -m, --mode=MODE set permission mode (as in chmod), instead of rwxr-xr-x -o, --owner=OWNER set ownership (super-user only) -p, --preserve-timestamps apply access/modification times of SOURCE files to corresponding destination files -s, --strip strip symbol tables --strip-program=PROGRAM program used to strip binaries -S, --suffix=SUFFIX override the usual backup suffix -t, --target-directory=DIRECTORY copy all SOURCE arguments into DIRECTORY -T, --no-target-directory treat DEST as a normal file -v, --verbose print the name of each directory as it is created --preserve-context preserve SELinux security context -Z set SELinux security context of destination file to default type --context[=CTX] like -Z, or if CTX is specified then set the SELinux or SMACK security context to CTX --help display this help and exit --version output version information and exit The backup suffix is '~', unless set with --suffix or SIMPLE_BACKUP_SUFFIX. The version control method may be selected via the --backup option or through the VERSION_CONTROL environment variable. Here are the values: none, off never make backups (even if --backup is given) numbered, t make numbered backups existing, nil numbered if numbered backups exist, simple otherwise simple, never always make simple backups GNU coreutils online help: <http://www.gnu.org/software/coreutils/> Full documentation at: <http://www.gnu.org/software/coreutils/install> or available locally via: info '(coreutils) install invocation'January 21, 2020 at 16:47 in reply to: Cannot install latest version (22.214.171.124) on Ubuntu 16.04 #25336
We have been unable to reproduce this problem. From logs you sent to us we have some conflicting information. One log says there are all files and have proper permissions set. Another log says that installation can’t find those files. Logs appear to be from two different machines, e.g one set from the connecting client, the other from the server. Also we did not received
/usr/NX/var/log/nxupdate.logwhich are essential to reproduce the problem in our lab.
You can also create detailed debug file which should tell us everything about the problem. You can do it by executing command
sudo sed -i '20s/^/set -x\n/' /usr/NX/scripts/setup/nxnode && sudo /usr/NX/scripts/setup/nxserver --update > nxlog.txt 2>&1 && sudo sed -i "/set -x/d" /usr/NX/scripts/setup/nxnodefrom your terminal and then send us
nxlog.txtwhich will be in the place you executed command above.
Please note that the logs must be from the machine where you are having installation problems.January 14, 2020 at 10:13 in reply to: Cannot install latest version (126.96.36.199) on Ubuntu 16.04 #25224
Unfortunately we will need some additional information. Those should tell us where the real problem is. Please collect
/usr/NX/var/log/nxupdate.log(if it exist) files. Output from commands
ls -ltr /usr/NX/etc/and
uname -awill be very useful. Send those information to forum[at]nomachine[dot]com, please.
@rshuck We’ve prepared a package with debug. Package will be passed to you by a private message. Please update your existing NoMachine installation, collect file
/Library/Application\ Support/NoMachine/var/log/nomachine_preinstall_logs.logand send those to forum[at]nomachine[dot]com, please.
Additionally we have a method to install NoMachine package directly from the command line. You can find instructions in article.
@rshuck Please check md5 sum of your downloaded nomachine package. You can do this by command
md5 <location of your package>from your terminal (for example:
md5 ~/Downloads/nomachine_6.8.2_1.dmg) and compare it to md5 sum from our site (f5804414e2fe7b820437c90edc4012ff).
Please check also if package is not blocked because of downloading it from internet. You can do this in “System Preferences -> Security and Privacy -> General” by allowing NoMachine.pkg to open and try to install it again.
@rshuck unfortunately we will need some additional information. Those should tell us where the real problem is. Please collect
/Library/Application\ Support/NoMachine/var/log/nxupdate.log(if it exist) files and send those to forum[at]nomachine[dot]com, please.
We test NoMachine with many flavours of Linux, there are hundreds out there, unfortunately we can’t test with all of them 🙂
The main reason is that Alpine Linux is shipped with musl instead of glibc. We are trying to figure out if there are more problems with it and checking if it’s possible to run NoMachine on Alpine at this time
Also we will need some additional information. Please collect /usr/NX/var/log/nxinstall.log and /usr/NX/var/log/nxupdate.log (if it exist) files, send those information to forum[at]nomachine[dot]com, please.June 17, 2019 at 16:04 in reply to: Is it possible to uninstall the USB Devices NoMachine installs ? #22703
For now there is an option to disable installation of nxusb drivers by installation from CMD only. We are planning to add skipping installation for other drivers in the future.
To install NoMachine without nxusb drivers you need to install it from windows command line with additional parameter /usbinstall=”0″.
nomachine-packageName_packageVersion.exe /usbinstall=”0″ /silent
nomachine-packageName_packageVersion.exe /usbinstall=”0″ /verysilent
You can find complete guide of installing and uninstalling NoMachine from command line here: https://www.nomachine.com/AR07K00682
You can also uninstall and disable nxusb drivers on existing NoMachine: https://www.nomachine.com/AR12O00955
- This reply was modified 8 months, 1 week ago by hawk.
NoMachine creates a hidden account, the nx user, used for internal operations of the NoMachine server only. This user, however, should not appear in the list of available users on login screen, as it’s hidden. It cannot be used to log-in to the Mac also. We cannot disable “Other Users” option in NoMachine installation process but you can do it yourself by using command in your terminal.
To disable “Other Users” option please type:
sudo defaults write /Library/Preferences/com.apple.loginwindow SHOWOTHERUSERS_MANAGED -bool FALSE
If you want to enable it back use:
sudo defaults write /Library/Preferences/com.apple.loginwindow SHOWOTHERUSERS_MANAGED -bool TRUE
However we think that ‘nx’ user on the list in “Users and Groups” preferences need more investigation and we will take a look what we can do with it.
Hi, there are two ways to disable automatic update in NoMachine.
One way is to edit /Library/Application\ Support/NoMachine/var/db/update file. Just change number in second section to 0. You can do this by running command: sudo sed -ie ‘s/:[0-9]*:/:0:/‘ /Library/Application\ Support/NoMachine/var/db/update from your terminal.
Second way is to open Server Preferences -> Updates from your NoMachine Player Settings and uncheck Automatically check for updates checkbox.
- This reply was modified 1 year ago by hawk.