Cookies are blocked or not supported by your browser.
“Cookies are blocked” error on the WordPress login screen: causes and what to check
WordPress shows this on the login screen when it sets a test cookie and the cookie is not sent back. The browser is rarely the cause. More often, the site address settings name a different domain or protocol, the cookie domain in wp-config.php is wrong, or the login page is served from a cache.
Which of these do you see?
The site address settings use another domain, www versus no www, or http versus https, so the cookie is set for the wrong address.
The siteurl and home options still contain the old address.
A cache serves a stored copy of wp-login.php that does not set the test cookie.
Common causes
References
Rather not fix it yourself? Let WP119 handle it automatically.
Wrong URL settings are handled automatically: the system corrects the site URL settings and runs a site-wide search-and-replace, including serialized data. Fixes are made on a copy of your site in the recovery station and written back only after re-verification passes. In your site’s database, the protected tables (members, comments, orders and form submissions) are copied as structure only. In SSH and FTP mode, the system creates a pre-recovery backup on your host before writing back and restores from it if verification after write-back fails. If the recovery cannot be completed, the recovery fee is refunded in full.
- Initial assessment: Site URL entry
- Copy to the recovery station: Work on a copy
- Diagnosis: Item-by-item checks
- Recovery and verification: Home and inner pages
- Write-back or delivery: Only after verification passes
Use WP119 when every browser shows this message and you cannot log in after a migration or an address change.
Check my site →