Reload licence information after a renewal
Make the server and the Web Console fetch the licence again when a renewed licence has not reached the deployment yet.
Reload licence information after a renewal
Self-hosted only: This guide applies to self-hosted deployments. On cloud, the hosted operations team manages licensing.
If a licence ran out before the renewal was paid, the deployment can still show the old, expired licence after the payment went through, or keep reminding you that the licence expires. The server and the Web Console each keep the licence they last loaded in a local file and keep using it while it is still within its grace period. The Refresh License Information button on Settings → Licensing only updates the Web Console; the server loads its licence when it starts.
To make both services load the renewed licence, delete their licence files and restart the containers. The API key stays the same.
Before you start
- The renewal is paid and the licence shows as active in the Members Portal, under the API key the deployment already uses.
- Shell access to the host running the NetLock RMM containers.
- The host can reach the Members Portal. Without that connection, the server cannot load a licence after the files are deleted and stops.
- A short maintenance window: both services restart, and the server downloads the agent packages again during its start.
Step 1 — Delete the licence files
sudo rm -f /home/netlock/server/internal/license_info.json
sudo rm -f /home/netlock/web_console/internal/license_info.jsonStep 2 — Restart both services
In the directory that contains your docker-compose.yml:
cd /home/netlock
sudo docker compose down
sudo docker compose up -dDuring the start, both services fetch the licence from the Members Portal with the existing API key and write a new license_info.json.
Verify it worked
-
Settings → Licensingshows the statusActive, with the correct licence name and seat count (see A.1). -
The server log of this start shows the new end date under
License valid until:sudo docker logs netlock-rmm-server 2>&1 | grep "License valid until"
If the status is still Expired, check in the Members Portal that the renewal is active for this API key, and that the host can reach the Members Portal.
Related
- A.1 — System overview & licensing — the Licensing page and the
Refresh License Informationbutton. - Replace the Members Portal API key — when the key itself, not just the licence, must change.
Replace the Members Portal API key
Replace the Members Portal API key of a self-hosted deployment on the Licensing page and restart the web console and the server.
Install the NetLock RMM server with Docker
Deploy the NetLock RMM server and Web Console on your own infrastructure with Docker, using the guided installer or a manual Docker Compose setup.