Perplexity ‘Sign In With Google’ Returns Error: Fix

When you try to sign in to Perplexity using Google, the browser may display an error message such as “Something went wrong” or “Access blocked.” This usually happens because your browser’s cached data conflicts with Google’s authentication process or because a browser extension interferes with the sign-in flow. This article explains why the error occurs and provides clear steps to resolve it on Windows 10 and Windows 11.

Why Google Sign-In on Perplexity Fails

The “Sign In With Google” feature uses OAuth 2.0, an industry-standard protocol for secure authorization. When you click the Google button, Perplexity sends a request to Google’s servers. Google then asks for your consent and returns an authorization code to Perplexity. If anything interrupts this exchange, the sign-in fails.

The most common cause is stale or corrupted browser cache and cookies. Your browser saves old versions of Google’s authentication pages. When Perplexity tries to redirect you to Google, the browser loads a cached page that no longer matches the current OAuth request. Google then rejects the request and shows an error.

Another frequent cause is browser extensions. Ad blockers, script blockers, and privacy-focused extensions can block the pop-up window that Google uses to verify your identity. Without the pop-up, the OAuth flow cannot complete. Other causes include a misconfigured Google account (unlikely for most users) or a temporary outage on Perplexity’s servers.

Steps to Fix Google Sign-In Errors on Perplexity

Follow these steps in order. Test the sign-in after each step to see if the error is resolved.

Step 1: Clear Browser Cache and Cookies

1. Open browser settings
   In Chrome or Edge, click the three-dot menu in the top-right corner and select Settings.
2. Go to Privacy and Security
   In the left sidebar, click Privacy and security then click Clear browsing data.
3. Select time range and data types
   Set the time range to All time. Check the boxes for Cookies and other site data and Cached images and files. Do not check browsing history unless you want to remove it.
4. Clear the data
   Click Clear data. Close and reopen the browser.

Step 2: Disable Browser Extensions

1. Open the extension manager
   In Chrome, click the puzzle-piece icon in the toolbar and select Manage extensions. In Edge, click the puzzle-piece icon and choose Manage extensions.
2. Turn off all extensions
   Toggle off every extension. Pay special attention to ad blockers like uBlock Origin, AdBlock Plus, or Ghostery. Also disable any script blockers such as NoScript or ScriptSafe.
3. Test the sign-in
   Go to perplexity.ai and try the Google sign-in again. If it works, re-enable extensions one by one to find the culprit.

Step 3: Use an Incognito or InPrivate Window

1. Open a private browsing window
   In Chrome, press Ctrl+Shift+N. In Edge, press Ctrl+Shift+P.
2. Navigate to Perplexity
   Type perplexity.ai in the address bar and press Enter.
3. Try signing in with Google
   Click the Google sign-in button. If the incognito window works, the issue is caused by cached data or an extension in your normal browser profile.

Step 4: Reset Chrome Flags (Chrome Only)

1. Open Chrome flags page
   Type chrome://flags in the address bar and press Enter.
2. Reset all flags to default
   Click the Reset all button at the top of the page.
3. Relaunch Chrome
   Click the Relaunch button that appears at the bottom of the page.

Step 5: Check Google Account Permissions

1. Go to your Google Account
   Open myaccount.google.com and sign in.
2. Open Third-party apps with account access
   In the left menu, click Security. Under “Third-party apps with account access,” click Manage third-party access.
3. Remove and re-add Perplexity
   Find Perplexity in the list. Click it, then click Remove Access. Go back to Perplexity and sign in with Google again to re-authorize the connection.

If the Error Persists After the Main Fix

“Access blocked: Perplexity’s request is invalid”

This error appears when Google detects that the OAuth request from Perplexity does not match the registered application. This is rare and usually caused by a Perplexity server-side issue. Wait 30 minutes and try again. If the error continues, contact Perplexity support at support@perplexity.ai.

“This browser or app may not be secure”

Google shows this warning when it detects automated login attempts or unusual activity. If you use a VPN or proxy, disable it temporarily. Also ensure your browser is up to date by going to Settings > About Chrome or Settings > About Microsoft Edge.

Sign-in works but Perplexity shows a blank page

This indicates that the OAuth token was received but Perplexity’s front-end failed to load. Clear the site-specific storage: open Developer Tools with F12, go to the Application tab, click Clear storage, and click Clear site data. Reload the page.

Perplexity Sign-In Methods: Google vs Email vs SSO

Item	Sign In With Google	Email and Password	Single Sign-On (SSO)
Account creation speed	One click	Requires email verification	Depends on organization setup
Security factor	Google account password + 2FA if enabled	Perplexity password only	Organization-managed authentication
Common error causes	Cache, cookies, extensions	Forgotten password, mistyped email	Misconfigured SAML or OIDC provider
Recovery method	Clear cache or use incognito	Password reset via email	Contact your IT admin

Signing in with Google is the fastest method, but it depends on your browser’s state. If you frequently encounter errors, consider switching to email and password sign-in. You can add a password to your Perplexity account after signing up with Google by going to Settings > Account > Password within Perplexity.

After following the steps above, you can sign in to Perplexity with Google without seeing an error. If the problem returns, clear your browser cache weekly or use a dedicated browser profile for Perplexity. For advanced users, create a Chrome profile with no extensions and use it exclusively for AI tools. This isolates sign-in issues to one environment.