RunCache can connect to BunnyCDN so your site can serve static assets such as images, CSS, JavaScript, and fonts through a Bunny pull zone.
Before you start
Make sure you have:
- A Bunny.net account.
- A pull zone already created for your site.
- Permission to create an API key that can manage pull zones.
- Administrator access to WordPress.
Open the Bunny.net dashboard and RunCache > Dashboard > Assets CDN.
Enable BunnyCDN in RunCache
In WordPress, go to RunCache > Dashboard > Assets CDN, then enable BunnyCDN.
The BunnyCDN configuration fields will appear below the provider card.
Enable BunnyCDN to display its configuration fields.
Connect BunnyCDN
- In the Bunny.net dashboard, go to Account → Access Keys.
- Create or copy an API key with permission to manage pull zones.
- Paste the API key into the RunCache API Key field. RunCache will automatically retrieve the available pull zones.
- Select the pull zone you want to use for this site.
If RunCache cannot retrieve your pull zones, check that the API key has permission to manage pull zones.
For instructions on creating Bunny.net API keys, see Bunny.net’s documentation.
BunnyCDN Settings
| Field | Description |
|---|---|
| API Key | Enter a Bunny.net API key with permission to manage pull zones. RunCache retrieves the available pull zones after you enter the key. |
| Pull Zone | Select the Bunny.net pull zone that will serve your site’s assets. If only one pull zone is available, RunCache selects it automatically. |
| Allowed File Extensions | Enter the file extensions RunCache should rewrite through BunnyCDN. Separate multiple extensions with commas or spaces. |
You can use * to allow all file types, or leave the default values unchanged.
Save Settings becomes available after you enter an API key and select a pull zone.
How the CDN Hostname Is Set
RunCache gets the CDN hostname from the pull zone you select. You do not need to enter the hostname separately.
RunCache uses this hostname when rewriting static asset URLs on your site.
Verify That BunnyCDN Is Rewriting Asset URLs
The RunCache status confirms that it can connect to the selected BunnyCDN pull zone. You should also verify that your site’s asset URLs are being rewritten correctly.
Open the page source for a front-end page and check an image, stylesheet, or script URL.
If BunnyCDN is working correctly, the asset URL should use your BunnyCDN hostname rather than your site domain.
How RunCache Purges BunnyCDN Content
When BunnyCDN is enabled as the Assets CDN provider, RunCache can send purge requests to BunnyCDN.
- A full purge clears the selected BunnyCDN pull zone.
- A post purge sends the affected URLs to BunnyCDN for purging.
BunnyCDN processes these purge requests according to its own cache-purge behavior.
If a BunnyCDN purge fails, check the RunCache logs for details.
Protect Your BunnyCDN API Key
BunnyCDN API keys are included in exported RunCache settings.
Treat exported settings files as sensitive credentials and store them securely.
Using WP-CLI
The following command enables BunnyCDN as the Assets CDN provider:
wp runcache enable-cdnIf you are currently using Custom CDN, running this command switches the active provider to BunnyCDN.
Edit BunnyCDN Settings After Verification
After BunnyCDN has been verified, the configuration form is hidden.
To change the API key, pull zone, or allowed file extensions, disable BunnyCDN and then enable it again to reopen the configuration fields.
If you have any other questions or need help, please feel free to get in touch with our 24/7 support team. We’re here to help!