Fixing the "CDN Acceleration Is Not Enabled" error

If you're seeing an error message indicating that CDN acceleration isn't detected on your website even after installing and setting up the Bunny.net WordPress plugin, this guide will help you troubleshoot and resolve the issue.

Common Causes

This issue typically arises in the following scenarios:

1 - Direct Origin Access

You may be accessing your WordPress admin panel without routing traffic through bunny.net. This often occurs if:

• DNS settings have not yet propagated.
• Your computer has a stale DNS entry.
• A static IP address for your domain is defined in your computer’s hosts file.

2 - CDN Acceleration Not Properly Configured

The plugin cannot detect Bunny CDN because your DNS settings are incomplete or misconfigured. This includes records that aren’t properly configured for CDN acceleration. 

3 - Web Server Altering Headers

If your site is behind a reverse proxy (e.g., Cloudflare, NGINX, or a load balancer), it might strip or modify headers used by bunny.net to confirm CDN usage.

Solutions

Try the following troubleshooting steps to resolve the issue:

1 - Clear Your DNS Cache

• On Windows: ipconfig /flushdns
• On macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
• On Linux: Restart the nscd or systemd-resolved service.

Then, restart your browser or clear its cache.

2 - Verify Bunny DNS and CDN Settings

• Go to the DNS section in your bunny.net dashboard.
• Make sure the DNS record pointing to your site has the green CDN Proxy icon enabled.
• If not, edit the DNS record and enable CDN Acceleration.

3 - Move Images Back to the WordPress Server (Optional)

If you're testing or troubleshooting, you can temporarily revert media delivery from BunnyCDN back to your origin WordPress server.

How Bunny Detects CDN Acceleration

Bunny.net checks for specific headers and DNS settings to confirm that your site is properly accelerated:

• In the bunny.net DNS section, a green CDN Proxy icon beside your DNS record indicates successful setup.

  

• Response headers like the following confirm BunnyCDN delivery:

  CDN-ProxyVer: 1.04
  CDN-RequestPullSuccess: True
  CDN-RequestPullCode: 200

• In your WordPress Admin Panel, go to bunny.net → About. Under the Technical Information block, check the Request Headers section. If both Cdn-RequestId and Via: BunnyCDN appear, your configuration is successful.

Need Help?

If you run into issues or need assistance, our support team is here to help. Reach out through our support request form for quick assistance.