login works on phone but not desktop: what to check

TL;DR

When login works on one device and not another, the account is fine and the failing device is the problem. Check in order: browser extensions (especially password managers and ad blockers), stale saved passwords autofilling, the system clock being wrong (breaks auth tokens), and cached sessions. Do not reset the password first: if the phone works, the password works.

The query

login works on phone but not desktop: what to check

Use this when

• Users report login works on phone but not desktop (or reverse)
• Device-specific login failures
• Writing login troubleshooting guides
• "Wrong password" reports where the password is right

Not for

• Server-side auth debugging
• Password policy design
• Account recovery or takeover
• SSO configuration

Steps

1. Confirm the exact failure on the failing device

What does the user see: wrong-password error, infinite spinner, blank page, or redirect loop. Each points somewhere different. Get a screenshot or the exact message.

Expected output: the precise failure mode.

2. Disable extensions and try a private window

Password managers autofilling old passwords and ad blockers breaking login scripts are the top two causes. A private window with no extensions is the fastest isolation test.

Expected output: works in private window (extension issue) or still fails.

3. Check the system clock

If the desktop clock is off by more than a few minutes, auth tokens fail validation and logins break mysteriously. This is common on desktops with dead CMOS batteries or manual time settings. Enable automatic time.

Expected output: clock correct and set to automatic.

4. Clear saved passwords and site data for the login page

Stale saved credentials autofill silently and the user never sees what was submitted. Remove the saved entry for the site, clear cookies for the login domain, and type the password by hand once.

Expected output: a clean manual login attempt.

5. Compare environments deliberately

Same browser on both devices? Same network? Corporate VPN or proxy on the desktop? Note the differences. If it works on the phone's browser but not the desktop's, the difference is the environment, and you now know which one.

Expected output: the environmental difference identified.

Template: the troubleshooting reply

Good news, [Name]: since your phone logs in fine, your account and password are working. Something on the desktop is interfering. Let us check, in order:

1. Open a private/incognito window and try logging in there. If it works, a browser extension (often the password manager or an ad blocker) is the culprit.
2. Check your computer's clock: if it is off by more than a few minutes, logins fail. Set it to automatic.
3. Remove the saved password for [site] in your browser, clear cookies for the site, and type the password manually once.

Tell me which step changes things and we will go from there.

Variant phrasings

can log in on mobile but not computer

Steps 2 through 4. Extensions, clock, saved passwords.

password works on one device only

Step 1 first: confirm it is really the password failing and not the session.

login redirect loop on desktop

Steps 2 and 4. Extensions and stale cookies cause most redirect loops.

Why it happens

Login is a negotiation between the device and the server: tokens, cookies, clocks, and scripts must all agree. Phones are relatively clean environments; desktops accumulate extensions, saved passwords, proxies, and clock drift. The account is rarely the problem when one device works.

Edge cases

• Corporate proxy or VPN on the desktop: it can strip or block auth cookies. Try off-VPN as a test.
• Very old browsers: the login page's scripts may not run. Check the supported browser list.
• The phone uses the app, the desktop uses the web: different code paths. Compare web-to-web before concluding.
• Timezone vs time: the clock being wrong matters; the timezone being wrong usually does not.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_QcyEZmAktz5sR0vOqDud2A