This article applies to NoMachine v7 and previous versions.

For NoMachine v8, please use: https://www.nomachine.com/AR08V01244

Message "No subscription information found" is given when any of the license files, server.lic and/or node.lic, (a) are not in the proper place or (b) are not in the suitable format or (c) are corrupted.

In this case, starting the server will provide a message like:

/etc/NX/nxserver --startup

NX> 611 No subscription information found. Please visit the
NX> 611 NoMachine web site at http://www.nomachine.com/
NX> 611 to acquire a valid subscription.
NX> 611 The NX server can't perform the requested operation.
NX> 999 Bye.

A similar message is issued also when checking the version (nxserver --version) or the subscription status (nxserver --subscription).

In case of b) or c), you can get the following message when trying to activate the license files via UI:
Cannot activate NoMachine Server, please ensure that server.lic is a valid subscription and is not corrupted.
or
Cannot activate NoMachine Server, please ensure that node.lic is a valid subscription and is not corrupted.

(a) License files are not in the proper place

Ensure that both server.lic and node.lic are in the 'etc' directory under the NoMachine server installation path.

On Linux: /usr/NX/etc

Ensure also that these files have the proper ownership and permissions.

Please note that the NoMachine Terminal Server Node has only one license file, node.lic:
 

More detailed intructions to install licenses:

for NoMachine server v7 https://www.nomachine.com/AR11R01100

for NoMachine server v6  https://www.nomachine.com/AR11O00942

(b) License files are not in the suitable format

Licenses are  'ASCII'  text  files in UNIX format. Copying their content from a local editor to the server host may lead to a conversion of the file format.

To make sure that files have not been accidentally converted to DOS format, run (on Linux):

# dos2unix /usr/NX/etc/node.lic

# dos2unix /usr/NX/etc/server.lic
 

(c) License files are corrupted 

If neither (a) or (b) solves the issue, you may contact our Support Team and request a verification of the server.lic and node.lic files you received.