Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #55359
    ACE
    Guest

    Hi team,

    Now, I have to start by saying that last week I started using the cloudflare extension you guys offer for the CDN. That being said, I now have to clear caches (both site and cloudflare at once) in order to solve this issue I’ve been having which is:
    members cannot login anymore. The page just gets stuck on logging in. It says it’s logging in but in reality the screen just ‘freezes’ and nothing happens at all.

    When I clear cache of course, everything works again. But for about 24h and then the problems start again.

    in the “Never cache the following pages” box I have included the login url’s and these used to work before. So I’m not sure what is setting this off right now. Any idea? As Cloudflare is telling me to go to you for these issues.

    Thanks!

    #55364

    Hello,

    Thank you for reaching out and I am happy to assist you with this.

    I have to start by saying that last week I started using the Cloudflare extension you guys offer for the CDN. That being said, I now have to clear caches (both site and Cloudflare at once) in order to solve this issue

    Just to confirm, did you start to experience the problem once you connected to Cloudflare? The question is have you been using W3 Total Cache before you connected with Cloudflare or vice versa?

    I can see that the cache-control header is set to 14400s and the default in W3TC is 3600s, So you may want to check the Cloudflare settings and set the browser Cache rules to respect the origin

    Let me know the answer and again make sure that the BC TTL in Cloudflare settings respects the origin headers.

    Thanks!

    #55366
    ACE
    Guest

    Hi, thank you for the quick reply. I got W3 first and added Cloudflare extension later on.

    I’ve had this problem before with the W3 plugin though, but after removing the page exceptions , doing a purge, adding the page exceptions once again (everything behind login basically), and clearing cache/purge again.. that solved the problem. Now it does not.

    So I’m assuming this does have something to do with Cloudflare but I’m not sure what. I’ve adjusted the settings of the browser cache rules. While I wait to see if this happens again, I’d love to hear if there’s anything else I can do.

    Thank you.

    #55371

    Hello,

    Thank you for your feedback.
    Let me know if the problem persists with the default W3TC Browser Cache settings.
    Also, make sure to check and configure Cloudflare Page rules and exclude the page from the cf cache.
    Thanks!

    #55385
    ACE
    Guest

    Hi,

    So I’ve set the cloudflare browser cache rule settings to respect the origin (w3) settings for this yet the problem is happening again unfortunately.

    Right now the page cache rule exceptions (what pages not to cache) are in the W3 settings for “never cache the following pages”. Are you saying I should remove them from there and instead put them into the Cloudflare page rules instead? Would this solve the issue?

    Thanks.

    #55492
    ACEnet
    Guest

    So to add onto this, I’ve now tried putting those page rules in CF and take them out of W3, but unfortunately the problem stays the same. I still have to cache every so often because logging in becomes impossible. I’ll add that on the site when people want to login, they get a login pop up. So I’m assuming that because it doesn’t have the admin /login url yet (because it’s a pop-up on a non-admin url, it’s still being cached? Could this have anything to do with it? And if so, how could I resolve it? Site is asexuals.net

    #55589
    ACE
    Guest

    A user has sent me this information:

    “The request is to wp-login.php. The response status is 200 with a response body of ‘-1’.

    The payload is:
    log: REDACTED@gmail.com
    pwd: REDACTED
    redirect_to:
    testcookie: 1
    security-login: REDACTED
    _wp_http_referer: /
    action: svq-ajax-login”

    If that’s helpful.

    #55604

    Hello,

    Well, this is very strange.
    The Cloudflare support refers you to us, even tho the problem started once you started using Cloudflare. And as we confirmed, you have not been experiencing the problem only with W3TC, and this was solved by excluding the pages from the cache.
    I am not quite sure why this is happening when you are using Cloudflare. The best thing in my opinion would be to move the login to a /login/ page or /account/ page and not use the popup since it the problems you mentioned may appear.
    I hope this helps!

Viewing 8 posts - 1 through 8 (of 8 total)
  • The topic ‘needs cache cleared every 24h because of member login issues’ is closed to new replies.