Common Licensing Errors Print

Most Cockpit licensing problems come from a small number of causes: the wrong license type, a server environment mismatch, loopback or private IP detection, or an activation request being made before the hosting setup is truly finished.

When to Use This

• The base panel license is not being accepted.
• The panel keeps redirecting you back to licensing.
• You moved the panel and licensing started failing afterward.
• You want a quick triage guide before opening a support ticket.

Most Common Licensing Problems

• using a module license where the base panel license is required
• copying the correct key with extra spaces or damaged formatting
• activating on the wrong server or unfinished hosting setup
• the server reporting 127.0.0.1, localhost, ::1, or a private IP instead of the real public server IP
• restoring or migrating files without fully rechecking the hosting environment

Quick Triage Steps

1. Confirm you are entering the base panel license, not a module key.
2. Copy the key again carefully and make sure there are no extra spaces.
3. Confirm the domain and server you are using are the ones intended for this panel.
4. Confirm the server is exposing the correct public IP to licensing.
5. If the panel was recently moved, recheck the new server's web stack and environment before retrying activation.

Expected Result

After basic licensing checks, you should be able to narrow the issue to one of three buckets: wrong key, wrong environment, or wrong server IP exposure.

What Different Symptoms Usually Mean

• License page never clears: The activation is not being accepted or the environment is not matching what licensing expects.
• Worked before a migration: The new server stack is a likely cause, especially if the IP or proxy setup changed.
• Works on one host but not another: The failing host often exposes a loopback or internal IP to PHP.

Common Mistakes

• Activating before the server is final: Settle the hosting stack first, then activate.
• Ignoring reverse proxy behavior: Apache behind NGINX or some panel-generated stacks can expose the wrong IP.
• Assuming the application is wrong when the host is wrong: Many licensing issues are server environment issues, not Cockpit bugs.

Example Use Cases

• Shared hosting problem: The panel keeps failing activation because PHP is reporting loopback instead of the server's public IPv4.
• Migration issue: A restore to a new VPS looks fine, but licensing fails because the new reverse proxy chain exposes the wrong address.
• Wrong key confusion: An operator pastes a module key into the base panel license screen and assumes licensing is broken.

When to Escalate

• You confirmed the correct base key is being used.
• You confirmed the server is intended for this panel.
• You still see licensing failure after checking for loopback or private IP exposure.
• You need hosting support to change how PHP receives the server IP.

Related Articles

• Activating Your Base Panel License
• Fixing Licensing When Your Server Sends 127.0.0.1, localhost, or ::1 Instead of the Real Server IP
• First Login After Installing Cockpit