Support
Bug reports &
integration requests.
Support is for reporting bugs and requesting new plugin integrations. For setup and usage help, the Get Started page on this site has you covered.
Scope
What this form is for.
Please read before submitting. Requests outside scope will be closed without response, not because we don't care, but because we can't help with them.
We can help with this
Bug reports — something in the plugin behaves incorrectly after correct setup
Integration requests — you need bypass rules or purge sync for a plugin not currently supported
Unexpected behaviour — edge rules deploying incorrectly, purge not firing when expected, cache warmer not running
Confirmed conflicts — a specific plugin combination that causes a reproducible problem
Outside scope
Setup and usage questions — the Getting Started guide covers the full setup process
Bunny.net account, billing, or DNS issues — this is an unofficial third-party plugin. Contact Bunny.net support directly.
General WordPress help — hosting, theme, or WordPress core issues unrelated to this plugin
Cache plugin configuration — questions about WP Rocket, LiteSpeed, W3TC, or any other cache plugin's own settings
Before you submit
Try these first.
Most issues are resolved by one of these steps. If you've already tried them all, include that in your report so we don't ask again.
1
Redeploy the edge rules
Go to WP Bunny Connector → Edge Rules and click Deploy Rules. Rules can get out of sync after plugin changes or Bunny API updates. A clean redeploy fixes most rule-related issues.
2
Enable debug logging and reproduce the issue
Turn on debug logging in Settings → Purge Triggers. Reproduce the problem, then check your PHP error log for API errors. Include any logged output in your report.
Settings → Purge Triggers → Enable debug logging
3
Check the X-Cache response header
Open browser DevTools → Network tab, load a public page, and look at the response headers. The X-Cache value tells you whether Bunny is serving from cache (HIT) or fetching from origin (MISS). Include this in bug reports about caching behaviour.
X-Cache: HIT X-Cache: MISS
4
Confirm your pull zone is in proxy mode
Edge HTML caching only works when Bunny is acting as a reverse proxy for your domain. If your domain points directly to your host and Bunny only handles asset CDN, the edge cache rules will not fire.
5
Check the Getting Started guide
The documentation covers setup, settings, deployment, and verification with step-by-step instructions. If the issue is configuration-related rather than a bug, the answer is likely there.
Getting Started guide
Submit a request
What do you need?
Select the type of request below. The form fields will update accordingly.
Bug report
Integration request