Public NLS (test and pilot)

Direct nls-client connection to nls.vinteo.com without a local NLS

bg-dots
bg-dots

This article describes connecting nls-client directly to the public nls.vinteo.com without a local or dedicated nls-server in the customer perimeter.

Attention!
This scheme is intended only for test installations and pilot projects. For production, use Local NLS or Dedicated NLS. See Choosing a licensing scheme.

The VCS server must reach nls.vinteo.com over TCP 4000. Licenses are assigned by technical support (support@vinteo.ru). Until registration is confirmed, the NLS client stays in a waiting state.

Preparation

Step 1. Stop the local NLS server (if it is running) and disable it from autostart:

systemctl stop nls-server.service
systemctl disable nls-server

Registering the NLS client

Step 2. Start client registration:

client -reg

An interactive wizard opens. Provide the following:

  • encryption — 1 (GOST);
  • server — nls.vinteo.com;
  • port — 4000;
  • host name — a clear VCS server name so support can identify the request among others.

After the request is sent, the NLS client remains at “Connected to the server”. This is expected until registration is confirmed.

Confirmation and licenses

Step 3. Tell technical support the host name used during registration. Support confirms the server registration and assigns the required licenses.

Step 4. After you are notified that licenses have been added, restart the NLS client on the VCS server:

systemctl restart nls-client

Verification

systemctl status nls-client

Connection status and issued licenses are also shown in the web interface under System → Licenses.

If the connection fails, check reachability of nls.vinteo.com:4000 from the VCS server and review the logs:

journalctl -u nls-client -e
Static and Dynamic P2P calls and licenses