Skip to article content

You cannot log into WordPress but your site still opens: what to check step by step

Your website opens, but you cannot log in to WordPress. Find out whether the password, session, a security lockout or the dashboard itself is involved, and what to ask support to check.

Your public site loading and your admin letting you in are two different things

When you see the home page as usual but the admin will not let you past the login form, it is easy to assume «WordPress is down». In reality two different things are happening, and telling them apart saves time.

The front (what visitors see) is usually served from pre-generated or cached pages: no login is required to read them. The admin area is a different layer: wp-login.php checks your user and password, leaves a session cookie in your browser and, with that cookie, lets you into /wp-admin. If authentication, cookies or the admin environment fail, the home keeps loading because that layer is untouched.

A working homepage does not prove that the whole server or database is healthy: you may be seeing a cached page. The dashboard’s message can still guide the next check. The sections below separate access problems, session problems and dashboard failures.

Before you touch anything: write down what you see

When the panel fails the temptation is to try things. Every attempt adds noise, and repeated login attempts can make a lockout worse if a security plugin is watching. Pause and write down what you are seeing.

  • Take a screenshot of the error with the full URL. «Incorrect password» is not the same as «too many attempts», a blank page, a 500 or an infinite redirect to /wp-login.php.
  • Note the time, browser and network (home wifi, mobile data, office). This separates a network issue from a site issue.
  • Try once in a private window, without extensions. If you can log in there, cookies or an extension are in the picture.
  • Check for recent changes: a WordPress, plugin or theme update, a password change, a hosting notice, a migration, a domain change or a new certificate.
  • Keep any email from your hosting about access or blocks; it may give the answer in one go.

With these notes at hand, what comes next looks like a diagnosis. If you call hosting or whoever maintains your website later, you save them minutes by describing the exact error instead of «I cannot log in».

The most frequent causes when the front works and the admin does not

Not an exhaustive catalogue, but the map that fits most often. Each cause has a tell:

  • Password lost or changed. The form answers «incorrect password» or «user does not exist».
  • Browser cookies or cache. You type the password correctly, no error, and you land back on wp-login.php in a loop.
  • Login-attempt lockout. A «too many attempts» or «your IP has been blocked» notice appears.
  • Site URL misconfigured. siteurl and home no longer match the URL you enter through. Typical after a domain change or certificate swap.
  • http and https mix. You enter through one version and the panel believes you are on the other. Can produce an infinite redirect.
  • Your role has changed. Login works, but you only see your profile, no admin menu.
  • Two factors broken. You log in fine but the second-step code never arrives.
  • Server rules blocking /wp-admin. An .htaccess file or nginx rule prevents the form from even loading. Often a 403.
  • Update that left the panel blank. You log in correctly but the dashboard loads blank or with a 500. The failure is in a plugin or the theme.

The exact message often matches a single line and that is enough to jump to the section that applies to you.

If the login page opens but rejects your user

The most frequent case. The form loads, you type user and password, and WordPress replies something does not add up. A simple order:

  1. Click «Lost your password?» inside the form and wait for the recovery email. WordPress documents the flow in its official page on resetting your password.
  2. Check the inbox and spam folder. If it does not arrive within minutes, the mailbox may be rejecting it or the hosting outgoing mail may be misconfigured.
  3. Check that the email tied to your user is still yours. If it changed, the reset link will arrive at a different address.
  4. If another authorised administrator is available, ask them to check your account and help start a password reset through a secure channel. Avoid sharing one password between several people.
  5. If you are the only administrator and the email never arrives, do not touch the database on your own. The right path is whoever maintains your website or hosting support, who can reset it from phpMyAdmin or WP-CLI with a backup in place.

A less obvious case: the form lets you in but once inside you only see your profile and no admin menu. It is not the password, it is your role: a plugin, a deliberate change or an access you do not recognise may have altered it. In that scenario, review who has access to your site and with which permissions before touching anything else.

Fictional example: a small business finds the password no longer works and the recovery email never arrives. Hosting reveals the outgoing mail has been misconfigured since a recent migration. The technical team resets the key and leaves the server mail working again.

If you type the right password and nothing happens

You enter your username and password and return to the form without a clear error. The session, cookies or address used may be involved, but this behaviour alone does not identify the cause.

Authentication cookies are small files WordPress leaves in your browser to remember you have identified yourself. If the browser rejects them, deletes them or keeps them for a different address, the panel does not recognise your session. The WordPress documentation covers it in its official guide on cookies.

What you can check without touching anything delicate:

  • Clear the site cookies in your browser and try again.
  • Try in a private window. If you can log in there, cookies, extensions or settings in your usual browser may be involved; this does not establish a single cause.
  • Try another browser once. If it works, that difference helps investigate the session, extensions or configuration; it does not rule out every server-side problem.
  • Check you always enter through the same URL. yourdomain.com is not the same as www.yourdomain.com, nor is http:// the same as https://: cookies may not match.

If the loop persists, the team can review WordPress’s siteurl and home settings. One identifies the WordPress installation and the other the public site; they can legitimately differ. After a migration, compare them with the intended configuration using the WordPress documentation, rather than making them match without checking.

If you were locked out by login attempts

The symptom is easy to recognise: by the third or tenth try, you see «too many login attempts» or «your IP has been temporarily blocked». A hosting notice about brute force sometimes arrives too.

Brute-force attacks are automated attempts to guess users and passwords, described in the WordPress official guide. Public sites receive this traffic every day, and many use a security plugin (Limit Login Attempts, Wordfence, iThemes/Solid Security or others) that blocks the IP after several failures. When the blocked IP is yours, it locks you out just like the attacker.

How to tell them apart:

  • Try to log in from another network, for example your mobile data. If you can log in from there, record the difference and ask support to check whether your usual network’s IP address is blocked.
  • Check the hosting emails: some providers notify and explain how to request an unblock.
  • Check whether another administrator can log in and remove your IP from the block list.

If you cannot reach the dashboard and no other administrator is available, ask whoever maintains the website or hosting provider to check the block and authorised recovery options. Stop repeating attempts while they investigate: depending on the policy, further attempts may extend the lockout.

If this episode has made you want to understand the security of your site better, it fits well to read a vulnerability report calmly and review who has access to the panel.

If the admin is blank or returning a 500 error

Scene change: the form lets you in, but the dashboard loads as a blank page, a 500 or «there has been a critical error on this site». The problem is not your user: it is the admin environment, which cannot run to the end.

Typical causes: a plugin recently updated no longer compatible with the server's PHP, the theme or another plugin; a theme failing on some panel screens; or a memory or execution-time limit too tight.

The official list of common WordPress errors helps recognise what you are seeing. For the 500 and the blank dashboard see our guide on the 500 error in WordPress. If you have just updated something and the site stopped responding, the natural read is what to do when WordPress stops working after an update.

A couple of rules to avoid making it worse:

  • Before touching the server (FTP, the hosting file manager, renaming a plugin folder), make sure a recent backup exists. If you are not sure, how to check your backup actually works is a useful frame.
  • If the site is important and you are not confident on the server, call whoever maintains your website or hosting before trying fixes on your own. Trying things «by intuition» can turn a locked panel into a fully offline site.

What to ask, and from whom, based on what you saw

Use these observations to decide who to contact and what they need to check. Not every piece is solved by the same person: hosting tunes the server and outgoing mail, whoever maintains the website touches WordPress with a backup in place, and as owner you keep control of users and passwords.

Based on what you are seeing
SituationWho to contactWhat to ask for
Password reset email never arrivesHosting (outgoing mail)Check whether the server's outgoing mail is delivering, or reset your password from phpMyAdmin with a previous backup.
«IP blocked» or «too many attempts»Hosting or your technical team with panel accessUnblock your IP in the security plugin and, if applicable, review the lockout policy.
500 error or blank screen in /wp-adminWebsite maintenance (with previous backup)Reproduce the error in a safe environment, identify culprit plugin or theme, propose a plan before touching production.
Infinite redirect to the login formYour technical team or hostingReview siteurl, home, http/https mix and redirect rules in .htaccess or nginx.
Two factors not reaching email or phoneYour technical team or the 2FA administratorUse the system’s recovery codes or recovery procedure first. If an administrative change is needed, verify identity and authorisation before changing protection and restore its configuration afterwards.
Your role looks reduced or you do not recognise a userSite owner with whoever maintains the websiteConfirm which permissions you need and why they changed. Adjust them only with authorisation and investigate unknown accounts; do not make every account an administrator to fix access.

The work your hosting provider can handle depends on the support agreement. Keep a record of checks and coordinate the next change with whoever has the right access and responsibility. Before file or data changes, agree how to roll back.

When asking for help, explain which work the lockout prevents and whether visitors or customers are affected too. That information helps agree the priority. Mention unauthorised changes or loss of access to accounts you controlled from the first contact.

If you want us to walk you through it

If you are not sure what the message means, or where to start without breaking more, tell us what you have seen: the exact URL, the form message and whether any recent change took place. We look together at which part of the panel is failing and point out the next step, without touching your site until we have agreed what to do and in which order.

If your intention is not to solve a specific lockout but to leave the panel in a more stable state, our security area covers access and admin hardening as part of the work. For the scenario where the real question is who has access or with which permissions, the natural follow-up is how to review the users and permissions of your site.