
You type your WordPress username and password, click Log In, and end up back at the login screen—or the /wp-admin/ page refuses to open at all. The problem can be as small as a browser cookie or as serious as a server failure or compromised account. The quickest fix comes from identifying what actually happens after you try to log in instead of changing random settings.
Before you change files: If the website is a live business or WooCommerce store, take a verified backup of its files and database. Record any error message and the time it happened. Avoid sharing passwords or access tokens with anyone offering help.
First, identify your WordPress login symptom
- Incorrect username or password: WordPress shows a credential error before opening the dashboard.
- Login loop: the form reloads after submitting correct details.
- 403 or blocked access: a security plugin, hosting firewall, or web server may reject your request.
- White screen, 500 error, or critical error: WordPress or its server may be failing before authentication finishes.
- Page not found: the login path may have changed, or the site address and routing may be incorrect.

10 ways to fix WordPress login problems
1. Open the correct login URL
For most self-hosted WordPress installations, visit https://yourdomain.com/wp-login.php or https://yourdomain.com/wp-admin/. Replace yourdomain.com with your own domain. If WordPress is installed in a subdirectory, the login URL may include that directory. Some security plugins deliberately change the login path; use the custom URL your administrator configured rather than disabling protection blindly.
2. Reset your password using the official form
Click Lost your password? below the login form and enter the email address or username linked to your account. Check the spam folder if the reset email does not arrive. If email delivery has also failed, ask your hosting provider or an authorized administrator to restore account access. Never use a password-reset link from an unexpected sender.
3. Test private browsing and clear site cookies
Open the site in a private/incognito window and try again. If it works there, clear only the affected site’s cookies and cached files in your normal browser, then temporarily disable browser extensions that modify requests. WordPress relies on authentication cookies; blocked or stale cookies can cause a login loop.
4. Check the HTTPS address and redirects
Confirm the login page stays on your intended HTTPS domain throughout the process. An unexpected switch between http and https, or between www and the non-www hostname, may create authentication problems. If you manage the site, check the configured WordPress Address and Site Address; do not change them impulsively when WordPress has a custom directory or reverse-proxy setup.
5. Check whether a security plugin or firewall blocked your IP
Repeated failed attempts can trigger temporary lockouts. Check your security plugin’s lockout logs and the hosting firewall or CDN events if you have authorized access. Wait for the stated lockout period or ask the site owner to unblock your IP. Do not repeatedly hammer the login page or bypass rate limits.

6. Isolate a suspected plugin conflict
If the problem appeared directly after a plugin installation or update, restore a known-good backup or investigate on staging first. When the dashboard is inaccessible, a site owner with SFTP or hosting file-manager access can temporarily rename a suspected plugin’s folder inside wp-content/plugins/ to disable it. Test login and then reverse the rename. Renaming the entire plugins folder can disrupt payments, forms and security, so it is a last-resort diagnostic rather than a routine first step.
7. Revisit recent theme or custom-code changes
A faulty functions file or custom authentication snippet can interrupt login. Identify what changed just before the issue started, review the PHP error logs, and roll back that change from a backup if necessary. Test theme switching only on staging where possible; changing a live store theme can affect templates, navigation and layouts.
8. Investigate rewrite and redirect rules
If login redirects to an incorrect location, examine custom redirects, hosting rules, and security-plugin settings. Back up .htaccess before editing it on an Apache server. On Nginx, equivalent routing rules may live in server configuration, not .htaccess. Avoid pasting random replacement configurations without checking the site’s setup.
9. Check for PHP errors or exhausted server resources
A 500 error or blank screen may indicate a PHP fatal error, incompatible plugin version, memory exhaustion, or hosting issue. Review your hosting error logs around the login attempt. If you see a PHP memory error, assess the host’s supported memory settings; if there is a fatal error naming a plugin or file, diagnose that component first. You can also consult our WordPress critical error guide.
10. Treat suspicious changes as a security incident
If passwords suddenly stop working, new administrators appear, or the site redirects visitors elsewhere, do not assume this is a normal login bug. Secure your hosting account, preserve logs and backups, rotate passwords from a clean device, and investigate unauthorized changes. Our first 30 minutes after a WordPress hack guide explains the initial containment steps.
A safe recovery checklist
- Write down the precise symptom and URL.
- Try the correct URL and normal password-reset flow.
- Test a private window and check HTTPS consistency.
- Review security lockouts, plugin updates and server logs.
- Make reversible changes one at a time and test after each.
- Once access is restored, create a backup and enable two-factor authentication.
Frequently asked questions
Why does WordPress keep redirecting me to the login screen?
Common causes include blocked cookies, inconsistent site URLs, cached authentication pages, or login/security-plugin conflicts. Test a private browser session before touching WordPress files.
Can I recover access without my password-reset email?
Yes, but recovery depends on what authorized access you still have. Your host or another verified administrator can help recover the account. Database or command-line recovery should be performed only by someone who owns or administers the site.
Will deactivating plugins delete my website?
Normally deactivation does not delete content, but it can temporarily disable crucial functions. Take a backup first and avoid bulk changes on a live business site.
Need help getting back into WordPress?
If your business website is inaccessible and the issue is affecting customers, DevTechi’s WordPress Emergency Fix service can help investigate the issue. Describe the error, the last successful login, and any recent changes—but never put credentials in a public form.
Reference: WordPress official login troubleshooting documentation and WordPress developer login guide.