Throws “Cookies are blocked or not supported by your browser” on 1st try

  • Resolved isarisar

    (@isarisar)


    2 years, 3 months ago

    Hi,

    I’ve noticed that with the plugin & a custom URL enabled, WordPress will always fail the first login attempt through the latter with

    ERROR: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.

    If one retries (or changes the language, which I suppose presets a cookie), the login attempt does succeed normally.

    This occurs

    • only if the plugin is enabled
    • across PCs & browsers (Chrome & Firefox, new profiles)
    • including with non-existing/invalid usernames & passwords

    However, I don’t recall this having been an issue for more than a few weeks. Maybe there is some new WP incompatibility?

Viewing 5 replies - 1 through 5 (of 5 total)

  • You have to exclude your new admin page from caching. I had the same error at the first login attempt. I solved it by excluding the old and new login path from catching by the WP-optimize plugin I use:

    WP-Optimize > Cache > Advanced settings > URLs to exclude from caching :

    /mynewwp-admin/
    /wp-admin/

    • This reply was modified 2 years, 3 months ago by dotch.
    Thread Starter isarisar

    (@isarisar)

    Hi @dotch, thanks for the advice – I’ve tried that with our WP Rocket and provider cache, unfortunately it does not work for us.

    Some also suggest setting define('COOKIE_DOMAIN', $_SERVER['HTTP_HOST'] ); in wp-config.php, unfortunately that didn’t work for us either.

    Plugin Support MaximeWPS

    (@seinomedia)

    Hello @isarisar

    @dotch is right.

    Have you purged your browser cache after you excluded wp-login.php and wp-admin pages from cache ?

    Are you using a CDN ? In this case, you’ve to exclude these pages from cache too there.

    Thread Starter isarisar

    (@isarisar)

    Hi @seinomedia,

    I did, attempts were with fresh incognito instances.

    I’ve also tried disabling WP-Rocket entirely, no change.

    Both /wp-admin & the new URL are excluded from my provider’s server cache, no change.

    The provider does supply CDN (Cloudflare), but it’s supposed (I have no influence) to only be set to cache static files.

    *edit:* Correction: Actually I can influence the CDN exclusions, it’s the provider cache I can’t seem to influence. Will try & contact them now, oops.

    • This reply was modified 2 years, 3 months ago by isarisar.
    Thread Starter isarisar

    (@isarisar)

    Hi again @seinomedia,

    you are both right. I got confused over the exclusions selectable on our provider’s backend: They’re for CDN only, not the provider’s own cache. So I contacted them and they (had to) manually added the custom URL to the latter’s list.

    Solved, thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Throws “Cookies are blocked or not supported by your browser” on 1st try’ is closed to new replies.