When You Can’t Log Into WordPress Because Your “Cookies Are Blocked”

0
308

Your cupcakes usually are started, you’ve loosened these individuals and also the relax of this cache, along with the dilemma prevails in each and every cell phone browser!

A regular circumstances is usually as soon as you’ve duplicated your blog by it’s test out WEB SITE to help output, or it could be you’re possibly simply just syncing decrease ones prod facts on your dev setting, as i complete just about every from time to time to be certain I’m publishing value next to authentic facts packages. Soon after reestablishing this duplicated web page records in addition to adding ones MySQL data bank dispose of in ones dev db, people innocently seek to find the way on your /wp-admin webpage in addition to visit.

Therefore you can’t visit on account of many creepy blunders including “Cookies usually are blocked” with your process … disheartening.

 

Cookies_blocked_in_wordpress_error-238x300

 

 

 

Checklist

While you are cannot check within WordPress, don’t freak out. Just simply have the initially very few sensible making convinced:

  1. Make sure you’re really at the right URL. No kidding, we all work on a million websites, just make sure your browser didn’t auto-fill your address bar with the wrong URL – it happens, admit it and let your coworkers make fun of you, then go on about your day.You might even be at the correct URL, but your hosts file is redirecting you to a server you’re not expecting.  (Touched your hosts file lately?)
  2. Reset your password.  The forgot password route is super easy, and with as many passwords as we all tend to juggle, it’s probably faster to just reset to something you’ll remember instead of spending an hour trying every combination of letters/numbers/symbols you’ve ever tried to memorize throughout your computing life.
  3. Check for error messages. But beware, error messages can be deceitful.  For example, if you’ve moved or copied your blog to another location with a different URL, you may need to do some blog triage (described further below!).  Also, you might want to try turning WP_DEBUG on in your wp-config.php file, as it may reveal more info that is helpful in troubleshooting.  Remember not to leave this on in production, though!  Read more about debugging WordPress.
  4. Disable your plugins by renaming the plugins folder.  Doing so has minimal impact, and is an attempt to remove any other non-WordPress-Core code from loading and further get to the bottom of your login issues.  Also, try renaming your active theme folder (the folder under the /wp-content/themes directory) to get WP to fall back to the default Twentyeleven theme.You’ll need to go back in and reactivate each plugin later, but is a good troubleshooting step!

This won’t solve every problem out there, but it’s a good start.  In fact, it was when my normal checklist failed and I found a more unique fix for W3 Total Cache issues that I decided to write this post.

W3 Total Cache

If you have W3 Total Cache installed,this is triggering ones membership dilemma – especially when you’ve not long ago migrated your site you aren’t kept up to date it’s WEB SITE. Unquestionably, that simply just was terrible 35 min connected with lifetime absent, which means this seemed to be just one I need to to share specially.

W3TC gives in addition to modifies many records and this can be bothersome, so that you likely simply want to triage ones html_docs folder as soon as going your site in addition to applying of which plugin. In the event you’re struggle to wood in your blog, typically finding some sort of “Cookies usually are blocked” malfunction meaning to be a warning sign, you might want to disable in addition to remove the plugin which causes the area wind up in the internet site. (People don’t need to have or maybe wish some sort of caching plugin with your dev setting, regardless! )).

 

To disable and remove the W3 Total Cache plugin manually:

  1. Navigate to your /wp-content/plugins folder and delete the w3-total-cache folder.
  2. Also, delete the w3-total-cache-config.php file from /wp-content.
  3. Open your wp-config.php file and look for a line of code to comment out or remove:
    1
    define('COOKIE_DOMAIN', 'www.your-website.com'); // Added by W3 Total Cache

    This is the line that causes those confusing cookie errors!

  4. You will still have your settings in your database, and should you choose to re-install the plugin, your settings should still be there.  You could also choose to manually go in and prune the W3TC options from the wp_options table in the database, but it’s not a requirement.
  5. Additionally, I like to go to the Settings > Permalinks options page and just click save again to force WordPress to rewrite the .htaccess file.

If you have further problems, feel free to leave a comment below!  Find another special case of a plugin causing login issues?  Leave a comment and help prevent somebody else’s hair loss  🙂

Facebook Comments