Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter allstarsft

    (@allstarsft)

    Update: I have tried Temporary disabled all plugins, except for NextEnd Login and my OceanWP… but the same error occurs (this is with Cloudflare paused and Cache plugin disabled).

    Next I tried with Cloudflare enabled and Cache Disabled — Page caching disabled.. Error still shows..

    • This reply was modified 1 year, 2 months ago by allstarsft.

    Hi @allstarsft,
    Can you try disabling the proxy inside Cloudflare? That is turn off the orange cloud inside your Cloudflare DNS for the ones it is enabled. Take a screenshot before doing this so you remember which ones used the orange cloud.

    After disabling the orange cloud, try again and let me know.

    Plugin Support Laszlo

    (@laszloszalvak)

    Hi @allstarsft

    First you could give Saumya’s suggestion a try. ( By the way, thank you for your suggestion @isaumya )

    If that doesn’t make any difference either:
    I have checked your site, and it seems you renamed our “SESSnsl” cookie to “nextendlogin”, and I can see it being set as well, so I think the problem will be rather that we are not able to get the stored values from the site transients.
    This problem usually occurs when you have an Object Cache that was either:

    • misconfigured ( e.g. you chose an object cache method in the backend of the object cache plugin, that you don’t have the necessary PHP extension installed for )
    • or the necessary service doesn’t run ( e.g. the Redis server )

    So as a next step, I would suggest you to go to your plugins list and check if you can see a Must Use or Drop-Ins tab there. If you do, then you should inspect them maybe you will find an Object Cache plugin there. If you do, try disabling it ( some of them e.g. Redis Object Cache has a option for this in their backend ) and see if that makes any difference.

    If it fixes the problem, then you should leave the object cache disabled. Or if you would like to use object cache on your site, then you need to fix the problem first.

    Thread Starter allstarsft

    (@allstarsft)

    Hi @laszloszalvak

    Thanks for your reply.

    As far as Object Cache is concerned, I thought it was activated at server’s end by the webhost. (Apparently its not)

    I did not install the Redis Plugin as I was advised by Webhost that its best not to install multiple Cache plugin.

    I have installed Redis now and activated the Object Cache… and the FB Login was solved! LOL

    Per REDIS :

    Status: Connected

    Drop-in: Valid

    Filesystem: Writeable

    That has solved the issue.

    But then again — is it still better to run on Primary DNS with Cloudflare? Have to pain one time to shift to Primary DNS at Cloudflare (DNS Propagation of the Domain name – nameservers is a Pain In The Ass)

    Other than ObjectCache, perhaps I can explore using the MemCache instead? Opinions please? 🙂

    Plugin Support Laszlo

    (@laszloszalvak)

    Hi @allstarsft

    I have also checked the login with social login again and it worked fine for me, too.

    So in this case you can ignore the DNS settings of Cloudflare, as it wasn’t connected to the problem, but it was the misconfigured Object cache.

    As for using different kind of object cache methods:
    Feel free to give it a try, just make sure the necessary PHP extension is installed on your server, otherwise you will experience the same problem as you did.
    Actually on our end the only thing that matters is that your object cache needs to work correctly, otherwise we won’t be able to set or read the data out of the site transients and we need that data to prevent CSRF attacks.

    Thread Starter allstarsft

    (@allstarsft)

    Great! Thanks @laszloszalvak !

    Thanks to @isaumya too! Shall mark this as resolved!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Error: Unable to validate CSRF state’ is closed to new replies.