• Resolved meeplescorner

    (@meeplescorner)


    Hi.
    I installed Cloudflare and your plugin on my site yesterday. Installation and setup was easy and everything seemed to work.

    After I tested my page if everything is still working, I went back to the plugin and clicked on TEST CACHE. After a moment the following message pops up:

    `Page caching seems not working for both dynamic and static pages.

    Error on dynamic page: Seem that your website is not behind Cloudflare. If you have recently enabled the cache or it is your first test, wait about 30 seconds and try again because the changes take a few seconds for Cloudflare to propagate them on the web. If the error persists, request support for a detailed check.

    Error on static resource: Seem that your website is not behind Cloudflare. If you have recently enabled the cache or it is your first test, wait about 30 seconds and try again because the changes take a few seconds for Cloudflare to propagate them on the web. If the error persists, request support for a detailed check.

    Please check if the page caching is working by yourself by surfing the website in incognito mode ’cause sometimes Cloudflare bypass the cache for cURL requests. Reload a page two or three times. If you see the response header cf-cache-status: HIT, the page caching is working well.`

    I’m with Siteground and use their SG Optimizer plugin. I de-activated the dynamic caching in the SG Optimizier because with it on, I couldn’t find any cf-cache headers. That seems to work now, but the TEST CACHE still comes back with the error message.

    I changed now from page rules to workers, which seems to work because Cloudflare is registering requests for the workers. But the error message is still popping up.

    Is there something I can change or do differently?

    Many thanks!

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • I also have the same mistake. I would like to have a solution to the problem. Thanks

    Is there any solution to this, I also experienced the same issue, however it’s erratic, on some occasions the test is successfully completed.

    The error I get:

    Page caching seems not working for both dynamic and static pages.
    
    Error on dynamic page (https://bicyclemarketplace.co.za): Cache status: BYPASS - Cloudflare has been instructed to not cache this asset. It has been served directly from the origin.
    
    Error on static resource (https://bicyclemarketplace.co.za/wp-content/plugins/wp-cloudflare-page-cache/assets/testcache.html): Unable to find the Cache-Control response header.
    
    Please check if the page caching is working by yourself by surfing the website in incognito mode 'cause sometimes Cloudflare bypass the cache for cURL requests. Reload a page two or three times. If you see the response header cf-cache-status: HIT, the page caching is working well.
    Plugin Contributor iSaumya

    (@isaumya)

    Hi @meeplescorner,
    It seems you have figured out and resolved the issue on your website as I can see caching is working perfectly on your website: https://i.imgur.com/f1iEpc6.png

    Thread Starter meeplescorner

    (@meeplescorner)

    Thank you for checking again.

    I didn’t change anything with the plugin, but I had to reinstall our SSL certificate because there was some problem. I noticed that the hit rate on Cloudflare went up afterwards, so maybe it was connected to this.

    Very happy with the plugin, thank you very much!

    PS: I’m on Cloudways and I use their Breeze plugin for page caching in addition to Cloudflare to make the website faster for users that are logged in. Would you recommend using the fallback cache in your plugin instead?

    Plugin Contributor iSaumya

    (@isaumya)

    If you are using another plugin for disk-level caching then no I won’t recommend turning on the fallback cache as you are already using a plugin for disk-level caching.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Test Cache results in error message’ is closed to new replies.