Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
WordPress keeps you signed in with authentication cookies. If the browser cannot save or return those cookies—or if WordPress, a cache, proxy, or plugin presents a different site address—the login form may loop, reject cookies, or log you out immediately. Start by clearing cookies and testing a private window, then verify cookies, both WordPress URLs, HTTPS and proxy settings, caches, and plugins in that order.
Start with the browser
- Clear this site’s cookies and cache. Remove cookies for the affected domain, clear cached files, close the browser, and sign in again.
- Retry in a private or incognito window. A successful private-window login points to stale cookies, cached redirects, an extension, or a browser privacy setting rather than a WordPress server failure.
- Allow cookies for the site. Disable a setting or extension that blocks first-party cookies, then retry. WordPress authentication cannot persist without a cookie that the browser accepts and sends back.
If the same failure occurs in a private window and another browser, continue with the site configuration checks below.
Understand the cookies WordPress needs
WordPress uses cookies to manage authentication. Its standard authentication cookies include wordpress_[hash], wordpress_logged_in_[hash], and, on HTTPS sites, wordpress_sec_[hash]. WordPress Developer Resources states that standard cookies last 48 hours; selecting Remember Me extends the login to 14 days. Those are expiration periods, not guarantees: a domain, path, HTTPS, or cache problem can invalidate the session sooner.
Recommended Free Tools
In your browser’s developer tools, inspect the response from the login request and the cookies stored for the site. Check that the cookie domain and path match the hostname and URL path you are using, that secure cookies are being used on HTTPS, and that the browser is returning them on the next request. A cookie warning identifies the browser-side symptom; it does not by itself identify whether the cause is the browser or server configuration.
#1 Best Overall
Make the WordPress URLs consistent
In the dashboard, open Settings > General and compare WordPress Address (URL) with Site Address (URL). They should describe the intended canonical origin—normally the same https:// hostname. Differences such as www.example.com versus example.com, or http versus https, can make the browser store a cookie for one origin while WordPress redirects to another.
If the fields are unavailable, inspect wp-config.php for WP_HOME and WP_SITEURL. These constants override the dashboard values. Change them only after confirming the exact canonical hostname and scheme with your host; an incorrect edit can make the dashboard unreachable.
Check cookie domain and path settings
Review any COOKIE_DOMAIN definition or custom cookie code. A hard-coded domain that does not match the current hostname, a subdomain migration, or a path mismatch prevents the browser from returning the authentication cookie. Remove an unnecessary hard-coded cookie domain rather than guessing a replacement. After changing URL or cookie settings, delete old cookies and sign in again.
Free tools Windows power users keep installed
One-click scans. No signup required.
Bypass every cache during login
Login responses and authenticated pages must not be served from a public cache. Exclude wp-login.php, /wp-admin/, and requests carrying WordPress authentication cookies from the page cache, CDN, reverse proxy, and server cache. Purge the WordPress cache plugin and host or CDN cache after changing URLs, certificates, or HTTPS rules.
A cached redirect or cached anonymous version of an admin page can look like a logout even when the cookie is valid. Test with caches temporarily bypassed, then restore caching for public pages while keeping login and cookie-based requests excluded.
Isolate plugin and theme conflicts
- Make a backup or ensure you have host recovery access.
- Temporarily disable plugins, prioritizing caching, security, SSO, membership, and redirect plugins.
- Test login in a fresh browser session.
- If it works, re-enable plugins one at a time, testing after each change until the conflict returns.
- Update or reconfigure the offending component, and re-enable security protection as soon as diagnosis is complete.
Do not leave a security plugin disabled longer than necessary. If you cannot reach /wp-admin/, use the host’s file manager or control panel to rename the plugins directory temporarily, or ask the host to disable plugins safely; restore the directory name after testing.
Verify HTTPS and reverse-proxy behavior
HTTPS is strongly recommended for WordPress logins and visitors. If FORCE_SSL_ADMIN is enabled, the login and dashboard must resolve consistently to HTTPS. A CDN or load balancer that terminates TLS must pass the original HTTPS state to WordPress. An incorrect X-Forwarded-Proto interpretation can produce an HTTP/HTTPS redirect loop or cause secure-cookie expectations to disagree with what the browser receives.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsAsk the host to verify the proxy’s forwarded-protocol configuration, the certificate and canonical redirect, and whether WordPress sees the request as HTTPS. Do not disable HTTPS merely to mask the symptom.
Best Value
Check firewalls, hosting and multi-server state
Web application firewalls and hosting security rules can block or challenge login requests. Review firewall and PHP error logs for the time of a failed attempt. For sites behind more than one server, ask the host to confirm that all nodes use the same WordPress salts and keys and consistent object-cache and session-related settings. Inconsistent nodes can accept a login on one request and reject it on the next.
Provide the host with the WordPress, PHP, web-server, CDN and plugin versions, the exact hostname, whether the failure affects every browser, and timestamps from the logs. This is more actionable than reporting only that WordPress “logs out.”
Use Site Health and update the stack
Open Tools > Site Health when the dashboard is available. Review critical issues, HTTPS status, loopback tests, and the environment details shown there. Keep WordPress core, plugins, and themes updated; WordPress hosting guidance identifies updates as the most important WordPress security measure. Apply updates through a backup or staging process when the site is business-critical, then retest login and admin navigation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose the next fix by symptom and access
| Symptom or situation | First action | Scope | Diagnostic value and reversibility |
|---|---|---|---|
| Works in private browsing only | Clear site cookies/cache; allow cookies and review extensions | Browser-only | Highly reversible; confirms stale or blocked browser state |
| “Cookies are blocked or not supported” | Enable cookies, then verify URL, cookie domain and HTTPS | Browser plus site configuration | Reversible; separates a browser policy from an origin mismatch |
| Login redirects between HTTP/HTTPS or hostnames | Align WordPress Address, Site Address, canonical redirects and proxy HTTPS detection | Server/configuration | Requires care; fixes origin and secure-cookie disagreement |
| Login succeeds but admin immediately logs out | Bypass caches; disable caching, security, SSO and redirect plugins methodically | Cache/plugin configuration | Reversible when changed one component at a time |
| Failure persists across browsers, or site uses a CDN/load balancer | Have the host inspect WAF, logs, forwarded headers, salts and object cache | Hosting/infrastructure | Low-risk for the site owner; host access is usually required |
When to escalate
Escalate to a managed host or WordPress administrator when you cannot edit wp-config.php, database options, cache rules, or proxy headers; when the site has multiple application servers; or when logs show firewall, PHP, or object-cache errors. Persistent failures after browser, URL, cache, and plugin tests need an environment-level review rather than repeated password resets.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
