License

This document explains how the license is activated, how the panel behaves when it cannot reach the license server, which actions pause, how to refresh the license state and how to move the license to another server.

Before you start

• Your license key.
• Root access to the main server.
• The server can reach https://api.xtreamgo.io on port 443.

Activation

1. The installer asks for the key at the prompt License Key: (or takes it from --license-key=).
2. It validates the key with the license server before it installs anything. An invalid key stops the installation.
3. It writes the key as LICENSE_KEY into /home/xtreamgo/.env.production and calls the activation endpoint with the key, the server IP and the host name. On success it prints License: <type> (Expires: <date>).
4. After the start the panel verifies the license by itself. The first verification binds the license to the public IP address of the server.

There is no separate activation step in the panel.

How verification works

• The panel contacts the license server every minute. It sends the license key, the server IP, a hardware fingerprint and usage figures.
• The answer is signed. The panel ignores answers without a valid signature.
• The panel stores the last state in /app/data/.license_state inside the API data volume, so the state survives a restart.
• The License page shows the type, the expiry date, the connection and stream limits, the last verification time and the active modules.

When the server cannot reach the license server

When a Telegram bot is configured, the panel sends LICENSE WARNING after 5 failed checks and LICENSE CRITICAL when it locks.

As soon as a check succeeds again, the lock is removed. No action is needed on the server.

Which actions pause

While the license is invalid

The API answers every request with HTTP 403 and "error":"license_invalid", except for the paths below.

Still available for administrators:

• Login (/api/v1/auth/login).
• License status (/api/v1/license/status).
• Migration paths (/api/v1/migration...).

Still available for subscribers:

• /player_api.php, /get.php, /xmltv.php, /portal.php.
• /live/..., /movie/..., /series/..., /hls/..., /timeshift/..., /catchup/....
• Everything under /stalker_portal/.
• The same Xtream paths behind a reseller code prefix.

All other subscriber paths are blocked while the license is invalid. Blocked paths include /c/, /server/load.php, /load.php, /enigma2.php, /panel_api.php, /livehls/..., /vodhls/..., /hlsr/..., /stk/..., /catchup-segments/..., /play/... and the short stream form /<username>/<password>/<stream-id>.

Individual actions with their own check

Existing subscribers, running streams and existing lines are not changed by a lock.

How to refresh the license state

1. Open License in the panel and use the refresh function. The panel runs a verification at once.
2. On a lock screen use Retry.
3. Without the panel, wait one minute. The background check runs every minute.

Check the state from the server:

curl -s http://127.0.0.1/api/v1/license/status
API=$(docker ps --filter name=xtreamgo-api --format '{{.Names}}' | head -1)
docker logs "$API" 2>&1 | grep LicenseChecker | tail -20

Ask the license server directly, the same way the installer does:

curl -s -X POST https://api.xtreamgo.io/api/v1/cms/verify \
  -H 'Content-Type: application/json' \
  -d '{"license_key":"<your-key>","server_ip":"checking"}'

The answer contains "valid":true or a message with the reason.

Expiry and renewal

• The panel shows a banner with the remaining days before the expiry date.
• The License page has a renewal request. The request goes to XtreamGo support and is approved by a person.
• The website states that licenses do not renew automatically. Order the same package again before the end of the period.
• After the expiry date the license server answers License has expired and the admin panel locks as described above.

Changing the license key

The License page has a function to enter a new key. The panel verifies the new key with the license server and switches to it.

The new key applies to the running API at once. It is not written into /home/xtreamgo/.env.production. Edit the line LICENSE_KEY= in that file by hand right after you change the key in the panel. Otherwise the API starts with the old key after a restart or an update.

Moving the license to a new server

The license is bound to one server IP. A second server with the same key is rejected with License is bound to a different server IP.

The customer dashboard on the XtreamGo website has a function to change the server. It has two modes:

Points to know:

• Both modes ask for the root SSH password of the new server. It is stored encrypted for the license and used for later updates. See Updates and rollback.
• The automatic mode moves the database. Media files, certificates and load balancers are not moved. See Backup and restore for the remaining steps.
• Install the panel on the new server first, then start the move.
• If the license is locked to hardware, the new server is rejected with Hardware fingerprint mismatch. License is locked to a different hardware. Ask XtreamGo support to reset the fingerprint.
• If you cannot use the dashboard function, ask XtreamGo support to move the license.

A server that keeps its IP address and hardware does not need a move. Reinstalling the operating system on the same server changes the hardware fingerprint input (/etc/machine-id). On a license with hardware lock, ask XtreamGo support for a fingerprint reset before the reinstall.

How to check it worked

curl -s http://127.0.0.1/api/v1/license/status

Expected fields: "licensed":true, your license_type, the expires_at date, days_remaining, and a last_check time within the last two minutes.

If something goes wrong