Self Hosted Comet Server is shown as offline: FATAL: Couldn't validate license key (Licensing authority denied our request.). Server will shut down.

Symptoms

Unable to access Self Hosted Server with the error message below in the logs:

Please ensure
- your account has credit
- the system time is synchronised to an NTP clock
- the serial number is valid, and used on one machine only
- the hardware and/or external IP address has not changed
- only one instance of Comet Server is running on this machine


You can relax a serial number on the https://account.cometbackup.com/ website.
[2026-06-15T10:53:09-03:00] Listening on interface '0.0.0.0:8060' (insecure)...
[2026-06-15T11:03:09-03:00] Starting server (version: 26.4.4)
[2026-06-15T11:03:09-03:00] Using TMPDIR: C:\WINDOWS\TEMP
[2026-06-15T11:03:09-03:00] [SoftwareBuildRole] Setting Max Builders: 2
[2026-06-15T11:03:09-03:00] [EventStreamer] Initializing streaming API service...
[2026-06-15T11:03:09-03:00] [EventStreamer] Finished initializing streaming API service.
[2026-06-15T11:03:10-03:00] Requesting new serial number lease...
[2026-06-15T11:03:15-03:00] Finished requesting new serial number lease.
[2026-06-15T11:03:15-03:00] Requesting new serial number lease...
[2026-06-15T11:03:20-03:00] Finished requesting new serial number lease.
[2026-06-15T11:03:20-03:00] FATAL: Couldn't validate license key (Licensing authority denied our request.). Server will shut down.

Cause

This error occurs when the Comet Server cannot successfully validate or renew its license lease with the central Comet Auth servers. Common triggers include:

  • Hardware or IP changes: The host machine's hardware ID, internal environment, or external public IP address has been changed.

  • Duplicate Instances: The same license serial number is actively running on more than one machine at the same time.

  • Time Desynchronization: The local server's system clock has drifted too far out of sync with real-world time.

  • Account Issues: The partner account has an invalid balance or zero credit.

Resolution

Before resetting the license, double-check the local environment to prevent the issue from immediately recurring:

  • Check Account Balance: Log into the Comet Account Dashboard and ensure your account has sufficient credit.

  • Sync System Time: Force a time synchronisation against a reliable NTP clock (e.g., time.windows.com or pool.ntp.org) to ensure the clock is accurate.

  • Ensure no old or duplicate instances of Comet Server are running on the same network or on a decommissioned staging server using the same key.

If the server environment has changed (e.g., a VM migration, hardware upgrade, or external IP swap), the license must be unlinked from the old hardware profile.

  1. Navigate to Comet Account Dashboard.

  2. Locate the specific serial number assigned to this self-hosted server.

  3. Click Relax (or reset) on the serial number to clear its hardware/IP lock.

  4. Restart the Comet Server service on your local machine to force it to request a clean, new license lease.

    relax license.jpg

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.