• Cloudflare cache has been actived but test cache did not pass:

    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.

    Any suggestion?

    Thank you

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • I am having the same issue on my website (https://gaiusjaugustus.com).

    Cloudflare cache has been active for a long time, but I tried testing it today and got the same error. I assume our errors are related, which is why I’m posting in this same topic.

    Here is my output on the test cache page:

    alt-svc: h3=":443"; ma=86400
    cache-control: max-age=600
    cf-cache-status: DYNAMIC
    cf-ray: 8db09939ae10d7a8-LAX
    content-encoding: br
    content-type: text/html
    date: Thu, 31 Oct 2024 03:36:02 GMT
    expires: Thu, 31 Oct 2024 03:46:02 GMT
    last-modified: Tue, 29 Oct 2024 20:28:14 GMT
    nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
    priority: u=1,i
    report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=wY2rtAihHfWQvqU5MJ6gWRdexTwu2D2DtjkY5HSFlR7rtfISsQP7yLelncyzuiisWUpO8Tx0j06srKF5oZtGQu8TflcQVLwtWNj0t6c1ehdWgKT2I1RzJQUa%2FWXFWkSH3CHfd0gtt5wdjgWwiZRhPC8%3D"}],"group":"cf-nel","max_age":604800}
    server: cloudflare
    server-timing: cfL4;desc="?proto=QUIC&rtt=55359&sent=1720&recv=632&lost=23&retrans=27&sent_bytes=1619192&recv_bytes=209007&delivery_rate=11703&cwnd=56607&unsent_bytes=0&cid=1480395788c82d5f&ts=130568&x=1", cfExtPri, cfHdrFlush;dur=0
    vary: Accept-Encoding,User-Agent
    Plugin Support Andrei Baicus

    (@baicusandrei)

    Hey @peopleinside,

    It seems that one of the cookies your website sets is on the front end is wp-dark-mode-device. As such, removing wp- from the Bypass Page cache when these cookies are present in the request packet setting in the Cache tab of the plugin should probably fix this.

    Hey, @gaiusjaugustus

    Could you please try purging all cache first? If that doesn’t work, you can try disabling and enabling the Enable Cloudflare CDN & Caching setting to see if that works?

    Thank you!

    Have an awesome day ahead!

    Thread Starter peopleinside

    (@peopleinside)

    @baicusandrei thanks for the reply.
    When I try to remove wp- in cache then save the WordPress say a critical error as occur so the plugin doesn’t let me remove this.

    gaiusjaugustus

    (@gaiusjaugustus)

    @baicusandrei

    I purged all cache, then tested the cache. I still get the same error.

    I set “Enable Cloudflare CDN & Caching” to Disabled, and then click Update Settings. The page refreshes, but “Enable Cloudflare CDN & Caching” is still set to Enabled. I tried several times with the same result. (And, tried retesting the cache again just in case, with the same failed result).

    mslauria

    (@mslauria)

    Hello,

    I encounter the same problem with one website I’ve been using the component for some years already let’s same almost since the first version and so far I had no troubles but after last update page cache stopped to be cleared after posts updates.

    I changed the Cloudflare settings from API Token to API Key putting my global key with no success then I deleted the folder and I installed the plugin back and after disabling and enabling twice cloudflare the test started to work and it worked for some hours but after 3 hours stopped again to work and the log if full of

    [2024-11-01 00:44:42] [cloudflare::purge_cache_urls_async_cache] Response for request 0: {“success”:false,”errors”:[{“code”:9106,”message”:”Missing X-Auth-Key, X-Auth-Email or Authorization headers”}]}

    [2024-11-01 00:44:42] [cloudflare::purge_cache_urls_async_cache] Response for request 1: {“success”:false,”errors”:[{“code”:9106,”message”:”Missing X-Auth-Key, X-Auth-Email or Authorization headers”}]}

    I had to revert to previous version 5.0.4 to solve the problem but this is not a solution.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.