Common Issues for WP Cloudflare Super Page Cache

1. Error: Invalid request headers (err code: 6003 )

   This is a Cloudflare authentication error. If you chose the API Key as the authentication mode, make sure you have entered the correct email address associated with your Cloudflare account and the correct Global API key (not your Cloudflare password!).

   If you choose the API Token as the authentication mode, make sure you have entered the correct token, with all the required permissions, and the domain name exactly as it appears in your Cloudflare account.

   Also, make sure you haven't entered the API Token instead of the API key or vice versa

2. Error: Page Rule validation failed: See messages for details. (err code: 1004 )

   Login to Cloudflare, click on your domain and go to the Page Rules section. Check if a "Cache Everything" page rule already exists for your domain. If yes, delete it. Now from the settings page of WP Cloudflare Super Page Cache, disable and re-enable the cache.

3. Error: Actor 'com.cloudflare.api.token.' requires permission 'com.cloudflare.api.account.zone.list' to list zones (err code: 0 )

   If you are using an API Token, check that you entered the domain name exactly as in your Cloudflare account.

4. PHP Warning: Cannot modify header information - headers already sent in /wp-content/advanced-cache.php

   Maybe you have some extra line or space in other PHP files executed before advanced-cache.php such as must-use plugins or wp-config.php.

   Check those files and try the following:

   1. If you have any code inside the must-use plugin take them out of that folder. Check your server error log and test to see if you are getting the header errors still.
   2. If not then check the codes inside the PHP files and see if any of them has an extra line or space at the end of the script. If they have, delete those new lines and spaces then test again.

   3. If it still doesn't work, check if any of the scripts inside the must-use plugins have print, echo, printf, vprintf etc. in the code. For more details check: https://stackoverflow.com/a/8028987/2308992

      In short, the problem is not coming from this plugin but some mu-plugin is sending the header before advanced-cache.php can. That's causing the issue. We have thoroughly tested this.

5. Custom login page does not redirect when you login

   Login to Cloudflare, click on your domain and go to the Page Rules section. Check if a Cache Everything page rule already exists for your domain. If yes, delete it. Now from the settings page of WP Cloudflare Super Page Cache, disable and re-enable the cache.

6. WP Admin or WP Admin Bar is being cached

   This should never happen. If it happens, it is because the value of the Cache-Control response header is different from that of the X-WP-CF-Super-Cache-Cache-Control response header (make sure they are the same).

   If you are using the LiteSpeed Server version lower than 6.0RC1, make sure the "Overwrite the cache-control header for Wordpress's pages using web server rules" option is disabled. If not, disable it, clear your cache and try again. You can keep this option enabled for Litespeed Server versions equal to or higher than 6.0RC1

   If you are not using LiteSpeed Server and you are using this plugin together with other performance plugins, enable the "Overwrite the cache-control header for Wordpress's pages using web server rules" option, clear the cache and try again.

   If this doesn't work, you can always choose to activate the Force cache bypassing for the backend with an additional Cloudflare page rule option or to change the caching mode by activating the Worker mode option.

7. Why changes are never shown when visiting the website?

   First of all, enable the log mode and check it in the log file, after clicking on the update button on the edit page, you see the information about the cache purging.

   If so, good news: the plugin is working correctly. If not, open a ticket on the support forum.

   If you have enabled the Fallback cache, make sure you have also enabled the option "Automatically purge the fallback cache when Cloudflare cache is purged".

   If you are using Varnish cache, make sure you have also enabled the option Automatically purge Varnish cache when the Cloudflare cache is purged.

   Disable any other page caching plugins or services. Only use this plugin to cache HTML pages.

   If you still don't see the changes despite everything, the problem is to be found elsewhere. For example wrong configuration of wp-config.php.

8. URLs with swcfpc=1 parameter getting indexed

   In very rare cases, it may happen that some third-party plugin stores the cache buster parameter in the database, and therefore this is then also displayed to users who are not logged in and therefore to search engine bots.

   If this happened on your site, enable the SEO redirect inside the plugin settings page under the Advanced tab. This will auto redirect any URLs which has swcfpc=1 in it to it's normal URL when any non-logged in user clicks on that link, avoiding duplicate content problems.

9. I am seeing ?swcfpc=1 at the front end URLs even when I'm not logged in

   Some page builders might copy the admin side links and show that on the front end for all users. This happens because these page builders do not follow the standard WordPress coding guidelines to fetch URLs and instead copy hard code URLs. If you are facing this issue, you can easily fix this by enabling the SEO redirect option inside the plugin settings page under the Advanced tab. This will auto redirect any URLs which has swcfpc=1 in them to its normal URL when any non-logged-in user clicks on that link.

10. Even after enabling the plugin, I'm seeing CF Cache Status DYNAMIC for all the pages

    There are a couple of things that can cause this issue and tell Cloudflare not to cache everything. If you are facing this issue, please check the following:

    • Make sure that Development Mode is NOT enabled for your domain inside Cloudflare.
    • Make sure you have the orange cloud icon enabled inside the Cloudflare DNS settings for your main domain A record and WWW record.
    • Make sure you do not have any other page rules that might conflict with the Cache Everything rule
    • Make sure you do not have any Cloudflare Worker code deployed that might overwrite the normal cache policies
    • Make sure you don't have any plugins which might be adding a lot of unnecessary Cookies in your request header for no reason. If you have any cookie consent plugins or any similar things, try disabling those plugins and check again. You can also enable the Strip response cookies on pages that should be a cached option under the Cache tab to see if this resolves your issue. If it does, that means there are plugins that are injecting cookies into your site header and when Cloudflare sees these Cookies, it thinks that the page has dynamic content, so it doesn't cache everything.

11. Should I enable the cURL mode for Fallback Cache?

    In most cases, you don't need to enable the cURL mode for the fallback cache. If you don't enable the cURL mode, the plugin will use the standard WordPress advanced-cache.php  method to generate the fallback cache. This system works well in almost all cases, also this cache generation mechanism is very fast and doesn't eat much server resource. On the other hand, the cURL mode is useful in some edge cases where the advanced-cache.php  mode of the fallback cache is unable to generate proper HTML for the page. This is rare, but the cURL option is given just for these edge cases.

    One of the benefits of the cURL mode is that as it uses server level cRUL instead of advanced-cache.php  to generate the page cache, the cache files come out very stable and without any issues. But then again if you enable the cURL mode, that means cURL will fetch every page of your website (which are not excluded from the fallback cache) to generate the fallback cache and each cURL request is going to increase some server load. So, if you have a small to medium site with not many pages, you can definitely use the cURL mode of the fallback cache. But for large high traffic websites, unless you have more than enough server resources to handle the cURL requests, we will recommend sticking to using the default advanced-cache.php  option which works flawlessly anyway.

12. What's the benefit of using Cloudflare workers over page rules?

    Cloudflare Workers is an amazing technology that allows us to run complicated logical operations inside the Cloudflare edges. So, basically, before Cloudflare picks up the request, it passes through the Cloudflare worker and then we can programmatically tell Cloudflare what to do and what not to do. This gives us great control over each and every request and how Cloudflare should handle them.

    The Page Rule option of Cache Everything works perfectly in almost every case but in some situations due to some server config or other reasons, the headers that this plugin sets for each request, do not get respected by the server and get stripped out. In those edge case scenarios, Cloudflare Worker mode can be really helpful over the page rules mode.

    So, in terms of speed, you might not see a difference but the Worker mode is there just for the cases when the page rule mode is not working correctly across the whole website (frontend & backend).

13. Do you need to pay for Cloudflare Workers?

    Yes & No. It depends on how many visitors your site has. Cloudflare Workers have a free plan which allows 100,000 requests/day for FREE. But if your site has more requests than that per day, then you need to opt for the paid plan of $5/month which will give you 10 Million Requests/month and after that $0.50 per additional 1 Million requests.

    Please note that all requests first get intercepted by Cloudflare Worker before Cloudflare decides what to do with that request, so whether your requests get served from Cloudflare CDN Cache or from the origin, it will be counted towards your Worker usage limit.

    If you have a small to medium site, you can easily use Cloudflare Worker without hesitating about payment as you will not get past the free quota, but as you grow, and if you still want to use the Cloudflare Workers, you might have to pay for it. Cloudflare Workers are so much more and have so much power that if you are truly taking advantage of the Cloudflare Workers, you can do a lot of cool things. So, in short, if you have a big high-traffic site and you don't want to pay extra for the Cloudflare Workers, you should just stick with the Page Rules option.

14. How is the Worker Code deployed to my Cloudflare Account?

    After you enter the Cloudflare API details, we push our worker code using Cloudflare API to your Cloudflare account. You can find our Cloudflare Worker code inside the plugin's /assets/js/worker_template.js  path.

15. Can I use this plugin with WP CLI?

    Yes. Commands list: wp cfcache