Cloudflare has retired the partner API that powers the Cloudflare plugin inside cPanel. GreenGeeks confirmed the change in a support post, noting that existing Cloudflare configurations keep working while new ones must be set up in the Cloudflare dashboard.
The practical impact is small but real. The convenience of one-click management is gone, and the workflow is now split between cPanel and Cloudflare. Here is what changed, what stays the same, and how to update your runbook.
What happened
- Cloudflare deprecated the partner API used by cPanel plugins, including GreenGeeks'.
- Existing Cloudflare setups on cPanel hosts are unaffected and continue to resolve.
- New domains can no longer be added or managed through the cPanel Cloudflare plugin.
- Day-to-day changes to existing setups must now happen inside the Cloudflare dashboard.
- The change is not host-specific—it affects every cPanel provider that relied on the same API.
What GreenGeeks told its customers
The GreenGeeks post is direct. The Cloudflare partner API is deprecated, and the cPanel plugin is no longer functional. Existing Cloudflare configurations will keep working—DNS records pointing at Cloudflare continue to resolve, so customers do not need to change anything on a working site.
The break is in the workflow. If a customer wants to add a new domain to Cloudflare or modify an existing setup, they now have to log in to the Cloudflare dashboard directly. The cPanel plugin is no longer the entry point. GreenGeeks apologized for the inconvenience and pointed customers at a support article for the full impact.
This is not a GreenGeeks-only event. Any cPanel host that bundled a Cloudflare plugin using the partner API is in the same position.
Our analysis
The headline is that nothing is broken. Existing Cloudflare setups on cPanel keep pointing at the right servers, the CDN keeps serving cached content, and SSL keeps terminating. The change is operational, not technical, and that distinction matters.
The bigger story is what gets lost. The cPanel plugin was the one-click on-ramp. A reseller could add Cloudflare from the same control panel where they manage email, databases, and SSL. That is no longer possible, which means the Cloudflare setup is now a separate task in the onboarding checklist. For anyone running dozens of new sites a month, that extra step compounds.
There is a security angle worth naming. With the plugin gone, the temptation to hand out Cloudflare dashboard credentials to every team member goes up, because there is no longer a per-cPanel-account permission boundary. The safer move is to keep Cloudflare access inside a small admin group and use API tokens scoped to specific zones. A compromised cPanel login should not also compromise the CDN.
What it means for you
Say you are onboarding a new client. Your previous workflow was: set up the domain in cPanel, click the Cloudflare icon, flip the toggle, and move on. That toggle is gone. Your new workflow has to be: set up the domain in cPanel, log in to Cloudflare separately, add the zone, copy the nameservers back into the domain registrar, and verify. You need a Cloudflare account ready before you start the onboarding call.
Who should care
| Situation | Impact | Action needed |
|---|---|---|
| Existing Cloudflare setup via cPanel | None—keeps working | Leave it alone |
| New domain, want Cloudflare | Must use Cloudflare dashboard directly | Add Cloudflare step to onboarding checklist |
| Managing multiple client sites | Extra login, no single-pane view | Assign one team member or group to own Cloudflare access |
| Security-conscious setup | Plugin removal reduces accidental exposure | Use scoped API tokens per zone; do not share dashboard passwords |
Bottom line
The Cloudflare cPanel plugin is gone, but existing setups keep working. The deprecation is a workflow change, not a service change, and the new front door is the Cloudflare dashboard. Update your onboarding runbook, scope your API tokens, and treat the convenience layer as something you have to rebuild inside your own process.
Key takeaways
- Existing Cloudflare setups on cPanel are unaffected by the deprecation.
- New domains must now be configured in the Cloudflare dashboard, not the cPanel plugin.
- Scope API tokens per zone and keep Cloudflare access inside a small admin group.
Frequently asked questions
Do I need to change anything on a site that already uses Cloudflare through cPanel?
No. Existing configurations keep working, and DNS records pointing at Cloudflare continue to resolve.
Can I still add a new domain to Cloudflare through my cPanel host?
No. The plugin is deprecated, and new domains must be added and managed in the Cloudflare dashboard.
Does this only affect GreenGeeks?
No. Any cPanel host that relied on the Cloudflare partner API is in the same position.
Will my site keep loading over Cloudflare?
Yes. The change is in the management interface, not in the underlying DNS or CDN behavior.
What is the safer way to share Cloudflare access with my team?
Use scoped API tokens per zone, and keep the main dashboard login with a small admin group rather than spreading it across the team.