Trouble Logging In? How to Fix Sign-In Problems

Trouble logging in almost always comes from one of five things: a wrong or outdated password, an email address that is not the one on the account, a second-factor code that will not verify, a browser holding a stale session, or an account locked after too many tries. Working through them in that order fixes most cases without contacting anyone.

Below are the checks in order, what each one rules out, and what to do when you genuinely cannot get in and need a person to help.

What should you check in the first two minutes?

1. Look hard at the email address or username you are typing. Many people have more than one address and registered with the one they use less.
2. Reveal the password with the eye icon and read it. Caps Lock, a phone keyboard capitalising the first letter, and a trailing space are the three usual culprits.
3. Check you are on the right sign-in page. Some companies run separate pages for personal and business accounts, and each one rejects the other's users.
4. Hard refresh the page, then try once in a private or incognito window. That rules out a stale cookie and most extensions.
5. Check your device's date and time are set automatically. A wrong clock breaks secure connections and one-time codes.

If none of that works, stop guessing at the password. Repeated wrong attempts are exactly what triggers a lockout, and a lockout turns a two-minute problem into an hour.

How do you reset a password properly?

Use the "forgot password" link on the sign-in page itself, not a link in an email you happen to have.

1. Enter the address you believe is on the account.
2. Wait a few minutes. Reset messages are often delayed, and requesting a second one usually invalidates the first, so if two arrive, use the newest.
3. Check spam, promotions and any filtered folders. Search the whole mailbox for the service name instead of browsing folders one by one.
4. Open the link on the same device and browser you will sign in with, where you can.
5. Set a password you have not used on that account before. Many systems refuse recent reuse and do not always say so clearly.

If no message ever arrives and it is not in spam, the address you entered is probably not the one on the account. Try your other addresses one at a time.

What is two-factor authentication, and why is it blocking you?

Two-factor authentication, usually shortened to 2FA, is the second proof asked for after your password: a code from an app, a text message, a security key, or a prompt on a phone you are already signed in on. It fails in a small number of predictable ways.

• Codes from an authenticator app are based on time. If the phone's clock has drifted, every code is rejected. Set the clock to automatic and try again.
• Text messages do not arrive when the number on the account is old, or when you are roaming on a network that blocks them.
• Backup codes are single use. One you have already used will not work a second time.
• A code typed slowly can expire mid-entry. Wait for a fresh one rather than rushing the current one.

If you no longer have the phone or the app, look for the account recovery path rather than the sign-in path. Recovery is deliberately slower and asks for evidence, and there is no legitimate way to speed it up.

Why does the page keep sending you back to sign in?

A sign-in loop, where the page accepts your details and then returns you to the same form, is usually a cookie problem rather than a password problem. Clear cookies for that one site, allow cookies if you have blocked them, and turn off strict tracking protection for the site. On a work device, a corporate network filter can also strip the cookie that keeps you signed in.

If the loop happens in only one browser, use another one to get in now and fix the first at your leisure.

What if the account is locked?

Lockouts are automatic after a number of failed attempts, and most clear themselves after a wait. Waiting really is the fix, because further attempts during the lock restart the timer on many systems.

If the message says "suspended" or "disabled" rather than "temporarily locked", that is a decision by the provider and not a timer. Those need support, and the message on screen normally names a reason or a reference code. Write it down exactly as it appears.

What should you have ready before contacting support?

1. The exact address or username on the account.
2. The exact error text, copied word for word, with any code.
3. When it started, and what changed just before: a new phone, a password change, a new network.
4. Which of the checks above you have already done.
5. A screenshot of the full window.

Contact through the provider's own help route, reached from the company’s official website, rather than through numbers or forms found in search results. Sign-in problems attract impostors, and no genuine agent will ask for your password or ask you to read out a one-time code.

How do you avoid this next time?

Store passwords in a password manager, including the one built into your browser or phone, so the address and the password always travel together. Download the backup codes when you turn on two-factor authentication and keep them somewhere that is not the phone itself.

Keep a recovery email and a current phone number on the account, and check once a year that both still reach you. Recovery details are only ever tested at the worst possible moment, which is precisely why they are so often out of date.