Common Issues with cPFence License Failing

Note: If you are using a Per-Website License, the most common fix for license issues is to sync your license after adding a new server. Run this command on your main CP server:

cpfence --sync-ips

For Per-Server or Bulk Per-Server licenses, please follow the instructions below for your license type.

If your cPFence license is not working, it’s usually due to one of the following common issues. Below are the causes and how to fix each one.

1. Invalid License Key

If the license key on your server is invalid, cPFence will fail to validate.

Solution: Log in to your cPFence Client Area, copy your correct license key, and update it on your server using:

/opt/cpfence/app/install Add-License-key-Here

See also: How to Manage cPFence License

2. New Server Added Without Updating License

When you add a new server to your cluster, the license must be updated to include the new server’s IP address.

  • Per-Website License: Run the sync command on your main CP server:
    cpfence --sync-ips
  • Per-Server License: Use the Reissue feature in your client area. 

    Please log in to the Client Area and go to the "My Services" page. Then, click on the corresponding license and then click the "Reissue" button. The server's IP will be detected automatically on first use and added to your account.

  • Bulk Per-Server License: Do not use reissue. Contact support to add your new IP.

See also: How to Add a New IP to My Per-Website License

And also: How to Add a new Server to WebUI

3. Blocked by Cloudflare Firewall

If your server sends several invalid license requests, it may be blocked by our Cloudflare firewall.

Solution: Open a support ticket so we can unblock your IP. To confirm if you are blocked by Cloudflare, run this command:

curl -s -D - -o /dev/null https://my.cpfence.app

If the output shows HTTP/2 403 or 503, it means your server IP is blocked; a normal response will show HTTP/2 200.

4. Server IP Blacklisted in IPDB

If your server IP is blacklisted in our protection IPDB, license validation may fail.

Solution: Check your IP reputation here:

https://www.abuseipdb.com/

If your IP is blacklisted, we recommend switching to a new VPS with a clean IP. If that’s not possible, contact us for more information.

5. Server IP is not Public or not Added in Enhance Server Settings

The IP address must match the Server IP listed in Enhance Control Panel > Servers > Server IP Address, and it must be Public. Floating or private IPs are not supported with a per-website license.

To fix this, either update the Server IP in Enhance to the licensed IP and run cpfence --sync-ips again on your main control panel server, or switch to a per-server license for this setup.

 


Need Further Assistance?

If you continue to have license issues after trying these steps, please open a ticket with our support team via your client portal.

 

  • license, invalid
  • 2 Utilisateurs l'ont trouvée utile
Cette réponse était-elle pertinente?

Articles connexes

How to Whitelist Your Enhance Cluster's IPs in cPFence (Important)

Important: It is essential to whitelist your IP addresses to ensure optimal operation and...

What is the Recommended cPFence Settings for Email, Backup, and DNS Servers?

If you're running DNS, backup, or email servers, optimizing cPFence settings can help ensure...

How to Manage cPFence License?

When cPFence is initially installed, the license should be added automatically. If you encounter...

Configuring cPFence

The default configuration of cPFence is highly recommended for the majority of use cases. Upon...

Installation Guide & Quick Start

cPFence installation is a straightforward process : Requirements - Ensure your server is...