WordPress Admin Login Not Working? Get Back In Safely

If your WordPress admin login is not working, do not keep trying random passwords or deleting plugins. First identify what happens: an incorrect-password message, a missing reset email, a login page that keeps reloading, a 403 error, a two-factor code problem or a blank screen. Each points towards a different fix.

For most business owners, the safest first steps are to check the correct sign-in address, try a private browser window, reset the password through the usual link and inspect any security message. If those fail, the next step is often your hosting dashboard—not editing WordPress files blindly.

This guide is for owners and managers of self-hosted WordPress websites in the UK. It explains what you can check yourself, what a host or developer should investigate and how to recover access without putting bookings, orders or customer enquiries at further risk.

WordPress admin login not working: match the symptom first

The error on screen matters more than the fact that you cannot sign in. Use this table before making changes.

What you seeLikely area to checkSafest first action
“Incorrect password” or “unknown username”Account details, password manager, changed accountConfirm the account, then use “Lost your password?”
Password reset email never arrivesMailbox, admin email address or website email deliveryCheck junk folder and address; contact host if still missing
Login reloads with no errorBrowser cookies, caching, site URL or redirectsTry a private window, then clear cookies for the domain
“Too many attempts”, CAPTCHA or 2FA rejectionSecurity plugin or account protectionStop repeated attempts; use the approved recovery route
403 Forbidden or Access DeniedFirewall, hosting rules or file permissionsRecord the error and ask the host to check security logs
404 or login page has disappearedCustom login address, rewrite rules or migrationCheck your hosting login button and saved login URL
Critical error, white screen or 500 errorPlugin, theme, PHP or server failureCheck the administrator’s recovery email and host status

Important distinction: if the website itself is accepting new orders or enquiries, a failed admin login does not automatically mean the public site is down. Avoid taking a working shop or contact form offline to solve a dashboard-only problem.

What should you do first when WordPress will not let you log in?

Start with the message on your screen. If WordPress says the password is wrong, use the official reset link. If it accepts the login but returns to the same page, test a private browser window and the website’s cookies. If you see 403 Forbidden, ask the host about a firewall block. If there is a critical error, look for the WordPress Recovery Mode email.

Do these five checks in order before changing any WordPress settings:

  1. Check the correct address: use your own domain followed by /wp-login.php, unless your site has a custom login address.
  2. Try a private window: enter your details once without relying on saved autofill.
  3. Use password recovery: select Lost your password? if WordPress reports invalid credentials.
  4. Look for a security message: stop repeated attempts if the website shows a lockout timer or requests two-factor authentication.
  5. Check the hosting account: find the official WordPress sign-in or support option if the standard route is unavailable.

Most of these checks take minutes and do not alter the website. If you spot unknown administrators, malicious redirects or an unexpected change to your login email, stop and treat it as a possible account-security incident.

Which WordPress login fixes are safe to try yourself?

ProblemOwner-safe first checkWhen to involve your host or technician
Password rejectedCheck saved username; request a resetNo reset email and no other authorised administrator
Login returns to login screenPrivate window; clear only that site’s cookiesStill loops across devices or after a migration
403 ForbiddenRecord the time, URL and messageReview firewall, WAF or IP-block logs
404 at wp-adminCheck the handover email for a changed login URLLogin route or domain configuration is broken
Two-factor code failsCheck device time; use saved recovery codesRecovery method is lost or the account is blocked
500 error or critical errorCheck the WordPress Recovery Mode emailPlugin, theme, PHP or server diagnosis is needed

A useful rule: do not change the site’s database, delete .htaccess, disable the whole plugins folder or restore an old backup as your first move. These steps may interrupt an otherwise working shop, bookings or lead forms.

1. Confirm which WordPress login you actually need

Most self-hosted WordPress installations use a login page at https://yourdomain.co.uk/wp-login.php. Enter your actual business domain, not the example address. /wp-admin/ often redirects to that page when you are not signed in.

But the usual address will not always work. Your agency may have changed the login URL with a security plugin. Your host may offer a one-click admin-login button. A staging website can also have separate credentials.

  • Check the saved link in your password manager or handover email.
  • Look for a WordPress administration button in the hosting account.
  • Make sure the address is the live website, not its temporary or staging copy.
  • Confirm you are using the correct WordPress user account, not the email and password for your domain registrar or web host.

WordPress.com is different. An account used to manage a WordPress.com-hosted website may be accessed through WordPress.com. A self-hosted WordPress.org website normally has its own user records and password recovery process. Mixing the two is a common source of confusion.

2. Try a private browser window before touching the website

If your password appears correct but the screen simply refreshes, open a private or incognito browser window. Type the correct login address manually, and sign in once. This avoids old website cookies that can interfere with a login.

  1. Open a private window in Chrome, Safari, Edge or Firefox.
  2. Go directly to the website’s known login page.
  3. Type the username and password once; do not rely on an old autofilled password if it seems wrong.
  4. If it works, clear the cookies and website data for that domain in your normal browser.
  5. If it fails in both browsers, write down the exact error rather than repeatedly trying.

WordPress’ own login troubleshooting documentation recommends checking passwords, cookies and firewalls. Clearing only the affected website’s cookies is less disruptive than wiping every saved login across your browser.

3. Reset your WordPress password the normal way

How do you reset your WordPress admin password? Open the site’s login screen, choose Lost your password?, enter the username or email address associated with the WordPress account and follow the link sent to that mailbox.

Use a new, unique password stored in a password manager. Never email passwords to contractors in plain text. If more than one employee needs access, give each person their own account with suitable permissions rather than sharing one administrator login.

WordPress documents several recovery routes in its official password-reset instructions. Start with the email route. Methods involving database edits or theme files are technical fallbacks, not first steps for an ordinary business owner.

4. What if the WordPress password-reset email never arrives?

A missing password-reset email does not always mean the password is wrong or the site has been hacked. The message may be caught in spam, sent to an old address or never delivered because the website’s outgoing email is misconfigured.

  1. Check spam, junk and filtered inboxes for the email address registered to that WordPress user.
  2. Check that you are not typing a colleague’s personal email while the site account uses a business address.
  3. Wait a few minutes before requesting another link. Repeated requests can make it harder to identify the latest valid message.
  4. If your email address has changed, ask a current administrator to update the account through WordPress.
  5. If nobody can get in, contact the hosting provider with proof of site ownership and ask which supported account-recovery options are available.

When website email delivery is broken, it can affect more than password resets. New customers might also be submitting a form without a notification reaching your inbox. The contact-form delivery checks help separate missing notifications from failed submissions.

Never install a new SMTP plugin solely to recover your password when you cannot safely access the dashboard. Restore authorised access first, then investigate the site’s email configuration and test a real message end to end.

5. Can’t log in after entering the correct password? Check for a redirect loop

A WordPress login redirect loop happens when the site sends you back to the login page after accepting the form. Sometimes the browser shows Too many redirects; sometimes the page simply refreshes.

Common causes include stale cookies, an incorrect website address, a conflict between HTTP and HTTPS, an over-aggressive page cache or a security/redirect rule. A recent website migration or SSL change can make a URL mismatch especially likely.

Ask your host or developer to check the site’s WordPress Address and Site Address, whether visitors are consistently sent to the intended HTTPS and www/non-www version, and whether the login page is excluded from full-page caching.

What should you avoid? Do not paste an unknown wp-config.php snippet from a forum into a live website. Some instructions change cookie behaviour or override site URLs permanently. A wrong change can stop legitimate visitors from reaching the site. If a site was recently moved, the website migration checks are also relevant to redirects and search visibility.

6. WordPress wp-admin shows 403 Forbidden: what does it mean?

403 Forbidden means the server understands the request but is refusing access. It does not prove your password is wrong. A hosting firewall, website security plugin, CDN rule or a permissions problem may be blocking the login route.

  • Note the exact URL and the time of the 403 error.
  • Take a screenshot of the message. Do not include passwords or confidential tokens.
  • Try the standard login page once, provided you know it has not been deliberately hidden.
  • Ask your host to inspect WAF, security and access logs for that time.
  • If the site uses a proxy or CDN, ask whether its protection rules are blocking /wp-login.php or /wp-admin/.

A 403 affecting only one network may indicate an IP-based block. Testing from mobile data can be a useful diagnostic step, but it is not permission to bypass an organisation’s security controls. Ask the authorised administrator to check the rule and restore access properly.

Hostinger’s WordPress admin troubleshooting notes include DNS and site-configuration checks for its own hosting dashboard. Other hosts have different controls; follow guidance for the host that actually runs your website.

7. Locked out by too many login attempts or two-factor authentication?

Security plugins may temporarily block sign-ins after repeated incorrect passwords. This is intended to protect the website. A two-factor authentication (2FA) plugin may instead request a code from an app, email, hardware key or recovery list.

If the screen shows a timer, stop attempting logins until the stated period ends. If you no longer have the authenticator device, use the recovery codes supplied when 2FA was set up. Ask another trusted administrator to review access if your organisation has one.

Do not disable the entire site’s security permanently because one user is locked out. If a technician needs to disable a security plugin briefly for recovery, they should document the action, verify the account owner and reinstate equivalent protection immediately afterwards.

Why this matters to a business: a seemingly quick fix can leave every administrator account exposed. If the problem began after unexpected password-change emails, unknown accounts or unusual site content, treat it as a possible security incident rather than an ordinary login error. The compromised WordPress response plan explains the different priorities.

8. WordPress login page gives 404 or has disappeared

A missing login page can have several causes. The site may use a custom login URL. Its domain may point to a different server after a migration. Rewrite rules may be broken, or a host security rule may deliberately conceal the standard address.

Check your original handover information and password manager before guessing URLs. If the front-end site is also missing, check your hosting and domain records rather than assuming the login page alone is broken.

Ask the site maintainer whether a security plugin changed the address. If so, use the correct configured URL. Temporarily removing a login-hiding plugin is a specialist recovery measure that should be carried out only by an authorised person with a tested restore plan.

9. Critical error, blank screen or 500 error when you sign in

When WordPress reports a critical error, a PHP failure or an all-white screen, the problem may involve a plugin, theme, PHP version or server resources rather than your credentials.

First check the administrator mailbox for a WordPress Recovery Mode message. When applicable, this contains a special link to a protected session in which a failing component can be investigated. WordPress describes the process in its official Recovery Mode documentation.

A white screen that began immediately after a plugin update may require a technical rollback. Use a known-good backup and a staging environment where possible; never delete all plugins on a live shop just to see if login returns. The WordPress plugin-conflict checks and white-screen recovery steps explain these faults in more detail.

10. What can the hosting company do when you cannot reach wp-admin?

The hosting account can provide a recovery route even when the WordPress dashboard is unavailable. Depending on the plan, a host may offer one-click WordPress sign-in, backups, file manager access, server logs, a staging copy or secure technical support.

Before giving instructions, establish whether you personally own or are authorised to manage the hosting account. Agency-managed hosting often requires the owner to request access or ask the agency to carry out the checks. Do not attempt to enter an account belonging to another organisation.

The host should investigate whether there is a server-side block, a failed migration, a broken email service or a recent technical change. Ask it not to overwrite a functioning website from an old backup before confirming what customer information would be lost.

A practical website ownership record should show who controls the domain registration, hosting, WordPress administrator accounts and backups. It makes recovery considerably easier when an employee or web designer leaves.

11. Password-reset email broken and no other administrator? Technical recovery choices

When standard account recovery fails, a developer with verified authority can use server-side tools. WordPress’ current administrator login handbook recommends WP-CLI where suitable. It can reset the password for an existing authorised user without editing database tables directly.

Recovery routeWho it suitsMain risk or requirement
Lost-password emailBusiness owner with a working account mailboxRequires the correct account email and functioning mail delivery
Existing administrator changes the user’s passwordTeams with a second trusted adminIdentity verification and appropriate user permissions
Hosting provider’s managed recoverySite owner with hosting account accessHost-specific support and ownership checks
WP-CLI password resetAuthorised technician with secure server accessCommand-line permissions; avoid exposing passwords in logs/history
Database-level password resetExperienced technician when other options failBackup, correct database/user identification and careful validation

Do not create an extra administrator account using random PHP code from an internet article. Do not place a public password-reset script on a live site and forget to remove it. Both can expose the website to takeover if handled poorly.

If someone is suggesting a database change, ask them to identify the target user, back up the affected database first, record the intended change and verify that legitimate editors still have access afterwards. You do not need to perform these steps yourself to understand what a responsible technician should do.

12. WordPress login stopped working immediately after a website change

The timing is useful evidence. List everything that changed in the 24 hours before the first failure: a plugin update, domain move, DNS update, SSL renewal, PHP upgrade, new security rule, password change or switch to another hosting provider.

For each change, compare the symptoms. A login loop after switching to HTTPS suggests a different starting point from a 403 that appeared after enabling new firewall rules.

WordPress recommends testing plugin problems systematically. A developer can isolate a recently changed plugin, review logs and restore a compatible version. If you use Elementor and the error happens only when editing a page, that is a different problem from failing to authenticate: see the Elementor editor diagnostic rather than changing login settings at random.

13. Don’t turn a login problem into lost sales

When customers can still browse and pay, prioritise business continuity. Tell the person fixing the login whether the website takes online orders, accepts bookings, sends quotation requests or holds customer data.

  • WooCommerce shop: test that checkout, order confirmation and payment processing still work before and after a fix.
  • Service company: verify the contact form and telephone button. Keep another enquiry route available while the dashboard is inaccessible.
  • Bookings: check whether the appointment service operates outside WordPress and whether changes could disconnect it.
  • Marketing: do not change domain or URL settings without assessing possible effects on Google indexing and paid landing pages.

A login fix is successful only when an authorised person can sign in and the customer-facing website still works. If you suspect enquiries have gone missing, the website enquiry-tracking setup can help test what is measured, but analytics does not replace checking the actual inbox and forms.

14. What should you ask before paying for WordPress login recovery?

A responsible quote should explain what will be diagnosed, what access the technician needs, how customer information will be protected and how the result will be tested. Avoid vague promises to “unlock WordPress” without any description of what happens afterwards.

QuestionWhy it matters
Will you check the reason for the lockout before resetting anything?Prevents a temporary fix that conceals a security incident or misconfiguration.
Will you record a backup or restore point?Makes risky changes easier to reverse.
What services may be interrupted during repair?Protects orders, contact forms, bookings and working hours.
Will you verify admin login from a fresh browser?Tests real access rather than a cached developer session.
Will you re-enable security measures afterwards?Avoids a permanently unprotected login page.
Will the owner retain their own access and credentials?Prevents repeat dependency on a particular developer.

Cost depends on the cause. A normal account password reset may take only a small amount of support time. Recovering a compromised site or a failed hosting migration is a wider technical project. Ask for a written, cause-specific scope rather than trusting a one-price-fits-all estimate.

15. A 15-minute checklist for the business owner

You can complete these initial checks without installing plugins or editing server files:

  1. Open the live website in a separate browser and check whether customers can still use it.
  2. Record the precise login URL and the wording of the failure.
  3. Check your saved WordPress account and any custom login address.
  4. Use a private browser window and attempt to sign in once.
  5. Try the official password-reset method, if the site is prompting for credentials.
  6. Check the registered account’s mailbox and spam folder.
  7. Check for a security lockout or two-factor recovery option.
  8. Look for a hosting provider’s WordPress management button.
  9. Check for a WordPress Recovery Mode email if the error is technical.
  10. Save a screenshot and contact the authorised host or technician with what you found.

Stop earlier if you see evidence of unauthorised changes, unknown users or malicious redirects. Those need a security response, not repeated sign-in attempts.

16. What information should you send to website support?

Sending complete diagnostic information usually helps support investigate without guessing. You can copy this simple request and fill in the factual details:

“Our business WordPress admin login is failing at [login address]. The problem began [date and time]. The exact message is [message]. The public website [does/does not] load, and our checkout or enquiry form [works/does not work/has not been tested]. We have already tried [safe checks]. The most recent website change was [change, if known]. Please investigate without replacing live data or removing security protection, and confirm what access you need from us.”

Attach a redacted screenshot if useful. Do not send the password, full database exports or private customer information in the first email. A technician can explain a secure route for exchanging authorised credentials if necessary.

17. How to protect access after the problem is fixed

Once you can sign in normally, avoid simply closing the support ticket. Find out why access failed and reduce the chance of a repeat.

  • Give each person a separate login and remove accounts no longer needed.
  • Use strong, unique passwords and a password manager.
  • Enable two-factor authentication and save recovery codes securely.
  • Confirm the administrator’s email address is monitored and password-reset messages arrive.
  • Record hosting, domain and website ownership details in a secure handover document.
  • Keep WordPress, extensions and themes maintained, using backups and tests before risky updates.
  • Exclude login and administrator URLs from inappropriate page caching.
  • Review unusual user-account changes, suspicious redirects and access logs after a lockout.
  • Arrange a regular website maintenance and backup routine suited to the importance of the site.

Security is a process, not a button. A strong login protects the business only when access recovery, updates, backups and ownership are also properly managed.

Why can WordPress accept your password but refuse the dashboard?

WordPress uses browser cookies to remember a successful sign-in. If those cookies are blocked, sent to a different domain or handled incorrectly by caching, the login page may keep reappearing even when the password is right.

This is especially worth checking after a change to HTTPS, Cloudflare, another CDN, the site’s domain or hosting. Your technician should confirm that the login and dashboard use the same intended domain, including the correct www choice. The login page and signed-in admin sessions must not be served as cached public pages.

Ask the host these questions:

  • Are /wp-login.php and authenticated /wp-admin/ requests excluded from full-page caching?
  • Do the site URL, SSL and proxy settings all agree about HTTPS?
  • Is a firewall blocking the login request or returning a 403?
  • Does the login response set an authentication cookie, and is the browser returning it on the next request?
  • Did the problem begin after a DNS, SSL, CDN, hosting or security-plugin change?

The official WordPress login handbook explains cookies, URL mismatches and cache exclusions. A business owner does not need to change server settings personally to request these checks.

WordPress login problems after moving a website

If the login stopped working after a migration, first confirm whether the domain points to the intended live installation. Make sure you are not using credentials for an old staging site. A mismatch between the public website address and the WordPress installation address can also trigger login redirects.

Do not immediately change DNS or overwrite the database. Ask the person who handled the move to compare the old and new addresses, the HTTPS setup, redirect rules and recent backups. If customers can still order or enquire, protect that live data while the login is repaired.

When does a WordPress login problem become urgent?

Urgent: customers cannot check out, a booking system has stopped, the website redirects to an unknown destination, or you see unauthorised account changes. Escalate promptly to the host or an authorised specialist.

Usually less urgent: the dashboard is inaccessible but the public website works, forms deliver messages and orders continue. Carry out the safe checks first. Still arrange a fix, particularly if you need to process orders or publish time-sensitive information.

After access is restored, test three things: signing in from a fresh browser, the actual enquiry or checkout journey, and the security controls that were active before the issue.

Frequently asked questions

Why can’t I log into WordPress with the correct password?

The account may have changed, or cookies, redirects, caching, two-factor authentication or security rules may be interfering. Try a private window, verify the username and reset the password before requesting a review of server logs.

How do I access wp-admin when the WordPress login page is missing?

Check the correct domain and any custom login URL first. Use the WordPress entry point in your hosting control panel if offered. If neither works, ask the host or site maintainer to review redirects and security settings.

Can a hosting provider reset my WordPress admin password?

Often, a host can support the owner with an approved recovery route or provide the tools needed by an authorised technician. The exact service depends on your hosting plan and the access controls in place.

Does a WordPress 403 error mean someone hacked the website?

No. A 403 indicates access has been refused, which can result from a firewall, plugin rule or permissions problem. Investigate unusual account activity or unexpected changes separately before ruling out a compromise.

Will clearing my browser cookies delete website content?

No. Clearing cookies for the site usually signs you out and removes browser session data. It does not delete WordPress pages, posts or customer orders from the server.

Can I fix a WordPress login redirect loop myself?

It is reasonable to try a private browser window and clear the site’s cookies. If the problem involves SSL, DNS, caching, WordPress URLs or server redirects, ask the host or a developer to inspect it rather than modifying live configuration files without a restore plan.

Should I disable all WordPress plugins to get back into the dashboard?

Not as a first step. Disabling plugins can interrupt forms, payments, bookings and security. A professional may isolate a plugin after making a backup and assessing the impact, but an ordinary owner should not start by disabling an entire live site.

Getting authorised WordPress access restored

Start with the exact symptom, not the most drastic fix. A password problem, firewall block and broken PHP update require different remedies. Confirm the public website still takes enquiries and orders, then use the lowest-risk recovery method available.

For UK businesses that need a specialist to diagnose a persistent lockout, Core Web UK’s emergency website support can assess the error, access arrangements and consequences for the live website. Describe the error and any recent changes in the website enquiry form before sharing sensitive access details.

Share