[resolved] "ERROR: Cookies are blocked or not supported by your browser" on internal setup (6 posts)

  1. David Borrink
    Posted 1 year ago #

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

    Appears on my log-in on a MAMP setup. I used it a few days ago and did an upgrade to 3.8.2 during that session. Today I can't log in. I tried to solve it by running some other solutions from other threads, such as running

    define('COOKIE_DOMAIN', 'http://localhost:8888');

    in my config.php file, but nothing is happening.

  2. Tara
    Volunteer Moderator
    Posted 1 year ago #

    it's more likely to be a server sessions or cookie issue WP upgrade. Have you spoken to your hosts about it. Or checked your error logs?

  3. David Borrink
    Posted 1 year ago #

    This is on an internal setup on a Mac using MAMP. So I'm the "hosts". How would I check my error logs? I'm using Firefox, by the way.

  4. David Borrink
    Posted 1 year ago #

    Okay, I got it fixed. Another thread reported that a change in the login setup to prevent hackers was causing this problem. I read the following...

    "I discovered my WP was upgraded automatically to 3.8.2. I was using a child of a theme that was out of date. Didnt notice the parent theme had a new version release.

    WP 3.8.2 addresses a hack problem with forged authentication cookies that stop you from logging in. You must be running a version of your theme that is not up to date and is not compatible with 3.8.2. (the timing of this is too coincidental) I think that's how the hack enters.

    My host logged in for me using another password then deactivated my theme and activated the WP default theme (twenty eleven).
    Was able to login after that. Have reverted to my parent theme and upgraded it then activated it. It's okay now. "

    1. Went into phpMyAdmin and changed my login password (see https://codex.wordpress.org/Resetting_Your_Password )

    2. Logged in, but found my dashboard broken up with no CSS, but was able to find the Appearance > Themes area and selected my parent theme, getting out of my child theme.

    3. Then I kinda got lucky because my email notifications told me all of a sudden that one of my sites had automatically update to 3.8.3. Ah, a upgrade. That would update the database and "reset" everything.

    That took care of everything. One other person said they downgraded to 3.8.1 and then ran the updater to get back up to 3.8.2. Same idea.

  5. totalwhite
    Posted 1 year ago #

    Big thanks David!! I renamed the child theme folder via FTP and at last the ERROR message desappeared! Now it's time to upgrade to new version release of the parent theme and then dive into CSS :)

  6. David Borrink
    Posted 1 year ago #

    You're welcome, totalwhite. That's why we post these fixes here.

    I had another site do this a couple days ago. I reset the password via phpMyAdmin and also upgraded their site to 3.9.1. Also, I had to report that the login page URL had changed to sitename.com/wp-admin instead of being sitename.com/wp-login.php

Topic Closed

This topic has been closed to new replies.

About this Topic