If the FleetSSL cPanel plugin suddenly stops working after the API Token was accidentally removed from WHM, you can restore functionality by forcing the plugin to generate a new token automatically.
Cause
FleetSSL stores its WHM API Token inside the following file:
/etc/.letsencrypt-cpanel-api-token
When the plugin starts, it checks this file first.
-
If the file exists → FleetSSL uses the saved token.
-
If the file does not exist → FleetSSL automatically creates a new WHM API Token and saves it again.
If the token is deleted manually from WHM → Manage API Tokens, the saved file still remains on the server. FleetSSL then tries to use the old invalid token and authentication fails.
Solution
Step 1 — Remove the Invalid Token File
Login to your server via SSH as root and run:
rm -f /etc/.letsencrypt-cpanel-api-token
This removes the outdated token stored by FleetSSL.
Step 2 — Restart FleetSSL Service
Restart the FleetSSL daemon/service:
systemctl restart letsencrypt-cpanel
What Happens Next
After restarting:
-
FleetSSL detects the token file is missing
-
It automatically generates a brand new WHM API Token
-
The new token is saved again into:
/etc/.letsencrypt-cpanel-api-token
-
SSL management starts working normally again
Verification
You can verify the newly generated token from:
WHM → Development → Manage API Tokens
A new token created by FleetSSL should now appear.
Additional Notes
-
No manual token creation is required.
-
No reinstallation is required.
-
If the service is not restarted manually, FleetSSL will usually regenerate the token automatically during its next scheduled run or when the plugin is opened in WHM.
