Luxembourg, May 22nd, 2025

NoMachine announces the immediate availability of version 9, unveiling the highly-anticipated NoMachine Network service, which facilitates remote access and collaboration over any network. It also introduces multiple enhancements bringing improved privacy and security through the new VPN and two-factor authentication features. Additionally, for larger infrastructures, the Enterprise Cluster products are more robust and scalable than ever thanks to improved load-balancing of connection requests between the cluster peers.

Key features in this new major version are:

NoMachine Network
NoMachine Network is the new service that lets you reach your computers over the Internet without any need for IP addresses or configuring port-forwarding on the router. Install any NoMachine server product and add it to Network to create its Machine Id. To connect to a computer using its Machine Id, users require a NoMachine account and a Network Subscription.

Two-factor authentication
NoMachine 2FA is a free and optional service available to everyone giving you an additional defense layer to protect both your login via NoMachine and access to the remote computer. It works for Network connections as well as for connections over IP. To receive push notifications, users must be in possession of a NoMachine account (User Id) and have installed the latest version of the free mobile app.

Integrated VPN out-of-the-box
Create a secure VPN by NoMachine without the need for relying on third party VPN software: you will see all the remote computers as if they are in the local LAN. NoMachine VPN is a feature built-in to the Enterprise family that works out-of-the-box, just run from your player or browser a “NoMachine VPN connection” to an Enterprise server and go.

New Cloud Server Cluster and Enterprise Terminal Server Cluster 
This is an active-active cluster where the master is in charge of distributing client connections and the load of session negotiation between itself and the slave (load-balancing of connections). Cluster master and slave roles can be switched between the primary and secondary servers as in the previous versions. Additionally, a new intuitive interface facilitates set-up of the cluster peers upon installation, guiding administrators step-by-step through the pairing procedure. Customers of v8 who wish to upgrade their Enterprise Cloud Server Cluster to v9 should follow instructions at: https://www.nomachine.com/AR11V01257.

Tunnel all traffic through the Cloud Server
A new key in server.cfg, EnableCommunicationHub, defines whether the Cloud Server is the only communication hub for the NoMachine traffic, including NoMachine Network traffic. This corresponds to option 'Tunnel all the NoMachine network traffic through the server' in the UI -> Settings -> Server -> ports panel.

Unattended access to a Cloud Server's nodes for Visitor users
A new checkbox in the UI in the Cloud Server node configuration panel allows Visitors to connect also without the desktop owner's approval. Visitors (available in Cloud Server products) are guest users logged in with a valid system account on the Cloud Server who can access the nodes also without the explicit consent of the desktop owner.

Set-up rules on a per-class basis all at once
The new switch '--type all' for profile rules allow to enable/disable the given class all at once. More details about how rules work in v9 are available at: https://www.nomachine.com/AR01W01265

Custom control over the authentication process to the Cloud Server nodes
A new server configuration key, EnableNodeAuthentication, enables or disables password authentication on the cloud server node. This configuration key aims to provide administrators with control over the authentication process, allowing to restore the authentication behavior from version 8.

Integration with Public Key Infrastructure in NX protocol
Already supported for connections by SSH, it's now possible to use host certificate and key issued by Certificate Authority (CA). See https://www.nomachine.com/AR06W01292 for
some remarks.

Updated NoMachine mobile app
The NoMachine for iOS and Android application provides full support for the new features of NoMachine Network and two-factor authentication, enabling access to Network whilst adding an extra layer of security through your device, all from the palm of your hand.

Pasting credentials in authentication dialogs on mobile devices
The input fields in the app configuration interface will allow to paste text content. This is particularly useful to improve usage of the app with password managers, by copy-pasting the password from the manager database to the authentication dialog.

Accepting all together users' concurrent connection requests
When more than three users are in the notifications list waiting for approval to connect, a notification will be issued proposing to accept all of them at once.

Non-owners can be allowed to accept connection requests
Thanks to the PhysicalDesktopAcceptUsers and VirtualDesktopAcceptUsers keys in server.cfg, administrators can define which type of users (including guests) are allowed to authorize incoming connection requests, by default only the desktop owner can do it.

Configuring the UI in 'Privacy mode' to not show usernames and IPs
Administrators can hide username and IP from the UI and notification balloons by configuring the ShowNotificationInfo key in node.cfg

Swapping control and command modifiers
This new option in the Input settings of the session menu allows users to swap Control and Command modifiers when connecting to/from macOS, so that they can comfortably continue to use some of their local shortcuts inside the NoMachine session.

Screen blanking control within the session
A new item of the NoMachine menu (!M) in the system tray, allows users to instantly blank/unblank their physical screens by toggling the 'Blank physical screen' option in the 'Desktop shared' sub-menu.

Automatic detection of USB devices in the session
Once plugged-in, USB devices are immediately detected in the ongoing session, offering them for sharing at any time.

Improved sessions list from command line
Commands 'nxserver --list' and 'nxserver --connectionlist' accepts the --format switch to customize their output and obtain the required information in a structured format. Use 'nxserver --list --format' to show those items that can be used as arguments for --format, e.g. 'nxserver --list --format username,display' and their description.

Version 9 sports also some changes to the previous v8:

Changes in license validation
From version 9, subscriptions are validated online simplifying license management for administrators. To activate the server and node software, the license is installed once only and does not need replacing. Onprem license validation, which requires replacing the license keys upon expiry, continues to be available.

NoMachine Workgroup Cloud Server replaces the Small Business Cloud Server
NoMachine Small Business Cloud Server is now called NoMachine Workgroup Cloud Server. Compatibility with license v8 is preserved, but license v9 or later cannot be used with the Small Business Cloud Server v8.

Export of logs via UI
The "Take logs" button to export logs via UI has been moved from the Server status panel to the Security panel.

New name for the known hosts files for connections by NX protocol
The known hosts files for connections by NX protocol, 'client.crt' are renamed into 'hosts.crt'. The player maintains compatibility with client.crt and continues to store certificates there, if present.

Log files are renamed
The 'nx' prefix is removed from log names, for example nxserver.log is now server.log, nxusb.log is usb.log and nxusbd.log is usbd.log.

Changes to the 'classic' value for the AcceptedWebMethods key
The value 'classic' for the AcceptedWebMethods key in server.cfg is renamed into 'mjpeg'. Compatibility with the previous value 'classic', is preserved.

The EnableNetworkBroadcast key is renamed
The EnableNetworkBroadcast key is renamed into EnableLocalNetworkBroadcast in server.cfg to avoid possible disarray with NoMachine Network-related keys. This key is for enabling/disabling mDNS discovery and works in LAN.

The EnableDirectXSupport key is renamed
The EnableDirectXSupport key in node.cfg is now called EnableHardwareAcceleration. This key enables or disables support for 3D hardware accelerated applications, including games running in fullscreen mode. Default is 1, enabled.

New updates model to configuration files on server side
The upgrade procedure preserves current keys in server.cfg, node.cfg and web.cfg files and doesn't change their names. NoMachine applications preserves compatibility with old keys names. For more details and the list of changes, see: https://www.nomachine.com/AR01W01267.

Renaming of 'nxserver --connectionmonitor' process
The 'nxserver --connectionmonitor' process is renamed into 'nxserver --monitor'.

New placement of NoMachine backend DB
The NoMachine DB is moved to /var/db/ and renamed into server.db. It's /usr/NX/var/db/server.db on Linux, /Library/Application Support/NoMachine/var/db/server.db on macOS and C:\ProgramData\NoMachine\var\db\server.db on Windows. Note that the DB is not intended to be accessed manually.

Session history now stored in a text file
When the session is terminated, all session data are moved from the DB to the history.log file stored in the NoMachine log directory in order to reduce RAM usage, especially in case of large DBs.

Customizable path for the log archive
The 'nxserver --debug --collect' requires the name of the log archive and the path where the file has to be saved to be specified.

Load-average parameter is added to the Linux load-balancing custom script
The custom load-balancing script, /usr/NX/scripts/lb/nxweightedroundrobin.pl, provided as an example now also supports the load-average parameter: uuid, weight,amount of sessions, connections limit. Compatibility with previous formats is preserved.

The full list of fixes available in version 9 is:

TR05U10858 - The pam_group module is not applied when connecting NoMachine sessions by SSH protocol
TR01U10749 - Nodes groups are wrongly listed in the Clouds panel in the UI
TR01T10438 - 'Authentication failed' occurs when connecting from Windows by using ECDSA and Ed25519 and SSH protocol
TR08V11190 - Starting a transfer from the server blocks or closes the application
TR02S10082 - Cannot delete a directory inside a disk connected in NoMachine session
TR10V11224 - On overloaded systems, the session may be not cleaned up properly when the custom script fails
TR0110739 - The client switches to a wrong panel when starting the Server admin on a Cloud Server node
TR05U10856 - The mouse pointer is not visible in text editors like Powershell and Notepad++
TR04V11137 - Server with large db doesn't start and history clear doesn't work properly
TR04R09648 - An "invalid argument" error occurs when connecting from Android client on IPv6 link
TR10V11229 - Some application folders are not accessible on Android 14
TR02W11277 - In some conditions failed session does not release user limits, preventing new sessions
TR03V11103 - Sometimes the mouse pointer on the remote desktop is in wrong position
TR01V11076 - Locking the macOS screen results in the client mouse pointer being out of sync
TR01W11258 - Inconsistencies in the db of Enterprise Terminal Server due to residuals from uninstallation of v7.14
TR03V11103 - Sometimes the mouse pointer on the remote desktop is in wrong position
TR02W11281 - New virtual desktops in a multinode environment can be slow to start
TR04R09618 - During system shutdown where nxserver is running a warning is issued that "Other users are logged in"
TR0110731 - Black screen when connecting to Wayland using two monitors
TR05V11141 - Capture of the Wayland desktop by EGL doesn't work with KDE Plasma 6
TR03W11290 - Cluster option '--single-cert' is not set properly in the configuration

Supported Platforms

Windows 32-bit/64-bit 7/8/8.1/10/11
Windows Server 2008/2012/2016/2019/2022

Mac OS X Intel 64-bit 10.9 to 10.11/macOS Intel 10.12 to 15/macOS Apple Silicon 11 to 15

Linux 32-bit and 64-bit
RHEL 6.0 to RHEL 9
CentOS 6.0 to CentOS 8.5
CentOS Stream 8 to CentOS Stream 10
SLED 11 to SLED 15
SLES 11 to SLES 15
openSUSE 11.x to openSUSE 15.x
Fedora 10 to Fedora 41
Debian 5 to Debian 12
Ubuntu 8.04 to Ubuntu 24.10

Raspberry Pi 2 ARMv6/ARMv7
Raspberry Pi 3 ARMv6/ARMv7/ARMv8/
Raspberry Pi 4 ARMv7/ARMv8
Raspberry Pi 5 ARMv7/ARMv8

ARMv7/ARMv8

Important Notice
Version 8 users are invited to verify if the list of changes may impact their custom configurations or scripts.

Customers of Enterprise Cloud Server Cluster v8 willing to upgrade to v9 should read carefully instructions at: https://www.nomachine.com/AR11V01257

In case of questions, please do not hesitate to contact us via any of the available channels for assistance.

Download NoMachine Packages

You can download the latest packages suitable for your Operating System from the NoMachine Web site at the following URL:

https://downloads.nomachine.com/

Customers with valid subscriptions can log in to their customer area and download the appropriate server package(s) for their subscription(s) from the 'Product Downloads' section.

Automatic updates

The automatic check for updates is scheduled to check our repositories every two days.

To update the free NoMachine package:

• - Open the NoMachine User Interface from your Programs Menu.
• - From the Machines panel click on 'Settings', then on 'Server' and finally on 'Updates'.
• - Then click on the 'Check now' button.

To update the NoMachine Enterprise Client immediately:

• - Click on 'Settings', from the Player panel click 'Updates'.
• - Then click on the 'Check now' button.

More information about the check for automatic updates is available here:

https://www.nomachine.com/AR05M00847

Manual package installation or update

Please follow the instructions to install the package or update your installation manually:

On Windows:

• - Download and save the EXE file.
• - Double click on the NoMachine executable file.
• - The Setup Wizard will take you through all steps necessary for installing or updating NoMachine.

On macOS:

• - Download and save the DMG file.
• - Double-click on the Disk Image to open it and double-click on the NoMachine program icon.
• - The Installer will take you through through all steps necessary for installing or updating NoMachine.

On Linux:

You can use the graphical package manager provided by your Linux distribution or update NoMachine by command line by following instructions below. If you don't have the sudo utility installed, log on as superuser ("root") and run the commands without sudo.

RPM

• - Download and save the RPM file.
• - Install the package by running:
  # rpm -ivh <pkgName>_<pkgVersion>_<arch>.rpm
  or
• - Update your NoMachine installation by running:
• # rpm -Uvh <pkgName>_<pkgVersion>_<arch>.rpm

DEB

• - Download and save the DEB file.
• - Install the package by running:
  $ sudo dpkg -i <pkgName>_<pkgVersion>_<arch>.deb
  or
• - Update your NoMachine installation by running:
• $ sudo dpkg -i <pkgName>_<pkgVersion>_<arch>.deb

TAR.GZ

• - Download and save the TAR.GZ file.
• - Install the package by running:
  $ cd /usr
  $ sudo tar xvzf <pkgName>_<pkgVersion>_<arch>.tar.gz
  $ sudo /usr/NX/nxserver --install
  or
• - Update your NoMachine installation by running:
  • $ cd /usr
  • $ sudo tar xvzf <pkgName>_<pkgVersion>_<arch>.tar.gz
  • $ sudo /usr/NX/nxserver --update
• If you are installing Enterprise Client or Node run respectively:
  • $ sudo /usr/NX/nxclient --update
  • $ sudo /usr/NX/nxnode --update

Documents

Installation and configuration guides for the NoMachine products are available at:

https://www.nomachine.com/support/documents

The NoMachine Development Team