BugWP logo BugWP
Back to Community
Home / Community / Plugin → Breeze – wordpress cache plugin

Troubleshooting CDN Issues in Breeze WordPress Cache Plugin

27 threads Sep 10, 2025 Plugin → Breeze – wordpress cache plugin

Content

Using a Content Delivery Network (CDN) with the Breeze cache plugin can significantly boost your site's performance. However, configuration issues can sometimes prevent it from working as expected. This guide covers the most common CDN-related problems and their solutions, based on community reports and resolutions.

Common CDN Issues and How to Fix Them

1. CDN URL Protocol is Changed to // on Save

The Problem: You enter a full CDN URL like https://cdn.example.com, but the plugin saves it as //cdn.example.com. This can break absolute URLs for social media meta tags.

The Solution: This was a known bug that was resolved in Breeze version 1.1.7. The first step is to ensure your plugin is updated to the latest version. If you are unable to update immediately, the fix involved a code change within the plugin files, which is not recommended for most users. Updating is the safest and most effective solution.

2. Specific File Types Not Being Served by CDN

The Problem: You've added a file extension like .ttf to the CDN exclusion list, but font files are still being served from the CDN link, potentially causing CORS errors when logged into WordPress.

The Solution:

  • Check Exclusions Format: The 'CDN Exclude Content' field is sensitive to spaces. A list like .php, .svg (with a space) may not work. Instead, use .php,.svg (without spaces). The Breeze team has acknowledged this suggestion for a future update.
  • Configure CORS Headers: For font files (.ttf, .woff, etc.) served from a CDN, you must configure your CDN to send the appropriate CORS header. You need to add Access-Control-Allow-Origin: * or a more specific origin to the headers for these font files. This configuration is done on your CDN provider's platform (e.g., Amazon CloudFront), not within WordPress.

3. CDN Not Rewriting URLs for WordPress in a Subdirectory

The Problem: If your WordPress installation is in a subdirectory (e.g., example.com/folder1-wp/), the CDN URL rewriting might not work correctly, and assets continue to load from your origin server.

The Solution: This is often caused by a conflict with the .htaccess file at the root of your domain. The Breeze team has indicated that a rule in the root .htaccess file may be interfering with the rules Breeze writes in the WordPress directory's .htaccess file. You may need to manually review and merge the rewrite rules.

4. Logout and Admin URLs Changed to CDN Link

The Problem: After enabling the CDN, crucial WordPress URLs like the logout or wp-admin links are rewritten to use the CDN domain, which will break their functionality.

The Solution: This is almost always intentional behavior. The wp-admin area and critical functions like logging out should never be cached or served through a CDN. The plugin should automatically handle this, but if it doesn't, you must ensure these paths are excluded. A common practice is to add wp-admin and any other sensitive pages to your CDN's exclusion list or within Breeze's exclusion settings if available.

5. General Configuration for Amazon CloudFront and Other CDNs

The Problem: CDN integration doesn't seem to work, or some WooCommerce files are not loading from the CDN.

The Solution: For a CDN like Amazon CloudFront, follow these configuration steps within Breeze:

  • CDN Root URL: If your site uses both HTTP and HTTPS, use the protocol-relative format: //xxxxxxxxxx.cloudfront.net. For sites forced to use HTTPS, https://xxxxxxxxxx.cloudfront.net is also acceptable.
  • CDN Content: In the text field, specify the directories you want to be served by the CDN. The standard directories are wp-includes,wp-content (again, mind the lack of spaces).
  • Exclusions: For WooCommerce, you may need to exclude dynamic pages like the cart and checkout. Excluding the wp-admin directory is also critical.

While Breeze is generally compatible with most CDNs, including Digital Ocean Spaces, specific configuration might be needed on the CDN provider's side, such as properly setting origin paths and headers.

Verifying Your CDN is Working

After configuring Breeze with your CDN, always verify it's working correctly:

  1. Visit your website in a browser.
  2. Right-click and select View Page Source.
  3. Look for URLs in the code (e.g., for images, CSS, or JS files). They should now point to your CDN domain (e.g., https://cdn.yoursite.com/wp-content/.../image.jpg) instead of your main site domain.
  4. You can also use tools like GTmetrix or Pingdom to see where your assets are being loaded from.

By following these troubleshooting steps, you can resolve the most frequent issues that prevent the Breeze CDN integration from working smoothly and ensure your site benefits from faster global asset delivery.

Related Support Threads Support