Reload licence information after a renewal

Self-hosted only: This guide applies to self-hosted deployments. On cloud, the hosted operations team manages licensing.

When a licence lapses — for example, it expired before a renewal went through — and you then renew it, the product can still report the licence as expired. The server and Web Console each cache the last licence information they loaded; until that cache is cleared, they keep showing the stale, expired state even though the Members Portal now holds a valid licence.

The fix is to delete the cached licence files and restart the services so they fetch fresh information. The API key does not change — this procedure only clears the cache.

Tip: For a routine re-query — after adding seats or upgrading a tier — use the Refresh License Information button on Settings → Licensing first (see A.1). Use the procedure below when the cached state is stuck and the button does not clear it.

Before you start

• Shell access to the host running the NetLock RMM containers.
• A renewed, valid licence on the Members Portal under the API key the deployment already uses.

Step 1 — Delete the cached licence files

Each service stores the licence it last loaded in internal/license_info.json. Delete both:

sudo rm /home/netlock/web_console/internal/license_info.json
sudo rm /home/netlock/server/internal/license_info.json

Step 2 — Restart the containers

Restart both services so they reload:

sudo docker restart netlock-rmm-web-console
sudo docker restart netlock-rmm-server

On startup, each service re-fetches licence information from the Members Portal with the existing API key and writes a fresh license_info.json.

Verify it worked

• Open Settings → Licensing in the Console. The status badge should now read Active, with the correct name and seat count — see A.1.

Related

• A.1 — System overview & licensing — the Licensing page and the Refresh License Information button.
• Replace the Members Portal API key — when the key itself, not just the licence, must change.