Step-by-Step Fix
Perplexity desktop and browser login issues generally fall into four categories: browser extension interference, corrupted cached data, network-level blocking, and certificate or OAuth redirect failures. Work through these steps in order — most users resolve the issue at step 1 or 2.
Step 1: Test in an Incognito Window First
The incognito test takes 30 seconds and immediately tells you whether the problem is extension-related or something deeper.
- Open an incognito or private browsing window:
- Chrome:
Ctrl+Shift+N(Windows) /Cmd+Shift+N(Mac) - Firefox:
Ctrl+Shift+P - Edge:
Ctrl+Shift+N
- Chrome:
- Navigate to perplexity.ai/login
- Attempt to log in using your usual method (Google, Apple, or email/password)
- Check whether login succeeds
If login works in incognito: a browser extension is blocking authentication in your regular browser. Proceed to Step 2.
If login also fails in incognito: the issue is network-level or account-level, not extension-related. Skip to Step 3.
Step 2: Disable Browser Extensions and Find the Culprit
Extensions that commonly block Perplexity login: uBlock Origin, AdGuard, Privacy Badger, Ghostery, NoScript, and any corporate security extension.
- In Chrome, go to Settings → Extensions (or type
chrome://extensionsin the address bar) - Toggle off all extensions at once
- Try logging in to Perplexity — if it works, extensions were the cause
- Re-enable extensions one at a time, testing login after each, until the issue returns
- Once you find the culprit extension, add perplexity.ai to that extension's allowlist or exception list
- uBlock Origin: click the extension icon → click the power button for perplexity.ai → refresh
- AdGuard: click the extension icon → toggle off "Protection on this site"
- Privacy Badger: click the extension icon → "Disable Privacy Badger for this site"
Step 3: Clear Cached Session Data for perplexity.ai
Corrupted cookies or cached authentication tokens can prevent login from completing even when credentials are correct.
Chrome:
- Press
Ctrl+Shift+Delete(Windows) orCmd+Shift+Delete(Mac) - Set the time range to All time
- Check Cookies and other site data and Cached images and files
- Click Clear data
- Close Chrome completely (quit the browser, not just the tab)
- Reopen Chrome and go to perplexity.ai/login
Firefox:
- Press
Ctrl+Shift+Delete - Set the range to Everything
- Check Cookies and Cache
- Click Clear Now
Edge:
- Press
Ctrl+Shift+Delete - Check Cookies and other site data and Cached images and files
- Click Clear now
Step 4: Test on a Different Network
Network-level interference — from corporate firewalls, VPNs, or DNS filters — can block the OAuth redirect that Google and Apple sign-in requires.
- Disconnect from your current Wi-Fi or disconnect from your VPN
- Switch to a mobile hotspot (use your phone's hotspot feature)
- Attempt to log in to Perplexity on the hotspot connection
- If login succeeds on the hotspot, your regular network is blocking Perplexity authentication
For corporate network users: the OAuth flow for Google and Apple sign-in requires access to accounts.google.com and appleid.apple.com in addition to perplexity.ai. If any of these domains are filtered, the redirect will silently fail. Ask your IT team to whitelist these domains.
Step 5: Try a Different Browser
If the issue persists after clearing cache and testing extensions, the problem may be browser-specific.
- Download a browser you do not normally use (Firefox if you use Chrome, or Chrome if you use Firefox)
- Install it without adding any extensions
- Open perplexity.ai/login and attempt to log in
- A clean browser with no extensions eliminates virtually all client-side causes
If login works in the new browser but not your regular browser even with extensions disabled, your browser's profile settings or stored credentials are corrupted. Create a new browser profile:
- Chrome: click your profile picture → Add → Guest (for testing) or create a new profile
Step 6: Check SSL Certificate Issues (Corporate Networks)
If you are on a corporate network and see SSL or certificate errors alongside login failures:
- Look for a certificate warning on the perplexity.ai page
- Click the padlock icon in the address bar and inspect the certificate issuer
- If the certificate is issued by your company's name rather than DigiCert or another public CA, SSL inspection is active
- Test on a personal network or mobile hotspot to confirm
- Contact your IT department — they will need to add Perplexity's authentication endpoints to the SSL inspection bypass list
Step 7: Contact Perplexity Support
If none of the above steps resolve the issue, email support@perplexity.ai with:
- Your operating system and version
- Your browser name and exact version number
- The exact error message or description of the failure
- Whether the issue occurs in incognito mode
- Whether you are on a corporate or home network
- Which login method you are using (Google, Apple, or email/password)
- Whether you have successfully logged in on this device before
Why This Happens
Desktop login failures on Perplexity almost always trace back to one of three root causes. First, browser extensions that block third-party scripts or network requests interfere with the OAuth redirect flow that Google and Apple sign-in depends on. Second, SSL inspection proxies common on corporate networks replace Perplexity's certificate during the HTTPS handshake, causing the OAuth callback to fail silently. Third, corrupted cookies containing stale session tokens can lock out an otherwise valid login by sending invalid authentication state to Perplexity's servers. Because all three causes can produce the same symptom — a login attempt that appears to do nothing — the incognito test is the fastest way to separate extension-caused failures from network-caused ones.
Common Mistakes to Avoid
- Trying to reset your password when the real issue is an extension. If your login button does nothing in your regular browser but works in incognito, resetting the password will not help. The issue is extension-related.
- Only clearing cookies without quitting the browser. Browsers may re-establish cached data from memory if you clear cookies without fully quitting and restarting. Always quit the browser after clearing, then reopen it.
- Assuming VPN is safe. Many VPNs route OAuth redirect traffic through servers that appear suspicious to authentication providers, causing silent login failures. Disable the VPN before testing.
- Testing on the same network after switching browsers. If the issue is network-level, switching browsers without switching networks will not help. Always test on a mobile hotspot to eliminate network variables.
- Ignoring the browser version. Outdated browsers may lack support for the authentication APIs Perplexity uses. If your browser is more than two major versions behind, update it before troubleshooting further.
- Creating a new account instead of fixing the existing one. If you cannot log in, creating a new account abandons your history and Pro subscription. Work through the steps above and contact support before creating a new account.