Perplexity Something Went Wrong – How to Fix

Step-by-Step Fix

The "Something went wrong" error is Perplexity's generic catch-all for any failure in the query processing pipeline. It is vague by design — the same message appears whether the problem is a brief server hiccup, a dropped network connection, or an expired session. Work through these steps in order to identify and fix the actual cause.

Step 1: Refresh the Page

This is the first and most effective fix. In over 80% of cases, the error is caused by a temporary server-side blip that clears itself within seconds.

1. Press F5 (Windows/Linux) or Cmd+R (Mac) to refresh the page
2. Wait for the page to fully reload
3. Submit your query again

If the error was a temporary glitch, this resolves it immediately. If the error reappears on the same query after refreshing, move to the next step.

Do not use "reopen closed tab" or restore from history — start a fresh page load.

Step 2: Clear Browser Cache and Cookies

Stale cached data can cause Perplexity to attempt to resume a broken session, repeatedly triggering the error.

Chrome:

1. Press Ctrl+Shift+Delete (Windows) or Cmd+Shift+Delete (Mac)
2. Set time range to Last 7 days
3. Check Cookies and other site data and Cached images and files
4. Click Clear data

Firefox:

1. Press Ctrl+Shift+Delete
2. Select Cookies and Cache
3. Click Clear Now

Safari:

1. Go to Safari → Settings → Privacy
2. Click Manage Website Data, find perplexity.ai, and remove it

After clearing, close and reopen the browser, then navigate to perplexity.ai.

Step 3: Log Out and Log Back In

An expired or corrupted session token is one of the most common causes of persistent "Something went wrong" errors, especially if you have been logged in for a long time.

1. Click your profile avatar in the top-right corner of Perplexity
2. Select Sign out
3. Close the tab
4. Open a new tab and go to perplexity.ai/login
5. Log in with your usual method (Google, Apple, or email/password)
6. Try your query again with a fresh session

Sessions that have been open for more than 12 to 24 hours without activity are particularly prone to this error.

Step 4: Disable VPN and Browser Extensions

VPNs and browser extensions are the leading causes of streaming interruptions that show as "Something went wrong" mid-response.

For VPN:

1. Disconnect from your VPN entirely
2. Refresh the page and try the query again
3. If the error clears, your VPN was the cause — try a different server location or add perplexity.ai to your VPN's split-tunnel exclusion list

For browser extensions:

1. Open an incognito/private window (extensions are disabled by default in incognito)
2. Navigate to perplexity.ai and try your query
3. If it works in incognito, an extension in your normal browser is the culprit
4. Return to your normal browser and disable extensions one at a time to identify which one is causing the issue — ad blockers and privacy extensions (uBlock Origin, Privacy Badger, Ghostery) are the most frequent offenders

Step 5: Switch from Pro Search to Standard Search

Pro Search uses a multi-step processing pipeline that has more potential failure points than Standard search. If the error appears specifically with Pro Search queries, switching modes often resolves it.

1. On the Perplexity search bar, click the mode toggle
2. Switch from Pro to Standard (or vice versa if you are already in Standard)
3. Submit the same query and observe whether the error still appears

Pro Search queries that trigger "Something went wrong" are often queries that take too long to process — Pro Search has a longer processing chain and is more vulnerable to timeouts.

Step 6: Check Perplexity's Status Page

If none of the above steps resolve the error and it is happening consistently across multiple queries, the problem may be on Perplexity's servers.

1. Go to perplexity.ai/status
2. Look for any active incidents, particularly those affecting search or AI response generation
3. Check Perplexity's official X (Twitter) account for real-time outage updates
4. If an incident is confirmed, wait for it to resolve — most Perplexity outages last between 15 minutes and 2 hours
5. Try again after the incident is marked as resolved

Step 7: Try a Different Browser or Network

If the error is isolated to one browser or network, switching rules out local configuration as the cause.

1. Try perplexity.ai in a different browser (Chrome, Firefox, Edge, Safari)
2. Try connecting via a mobile hotspot instead of your home or office Wi-Fi
3. If the error disappears on a different browser or network, the issue is your local setup — a network filter, ISP restriction, or browser-specific problem

Corporate networks frequently apply content inspection or traffic shaping that can disrupt Perplexity's streaming responses. If you are on a work network, try a personal connection.

Why This Happens

"Something went wrong" is Perplexity's catch-all error for any unhandled exception in its backend pipeline. The three most common root causes are:

1. Temporary server-side errors — Perplexity's AI infrastructure briefly fails to process a request. These are self-resolving within seconds and a page refresh is the complete fix.

2. Network or VPN interference — Perplexity uses streaming HTTP connections to deliver responses progressively. Any interruption in this stream — from a VPN, a browser extension, or a network drop — cuts off the response and triggers the error. The streaming connection typically remains active for 10 to 60 seconds for complex queries, making it vulnerable to brief network fluctuations.

3. Expired or invalid session tokens — Perplexity authenticates each request using a session token stored in your browser. When this token expires or becomes invalid (due to cache corruption or long inactivity), every request fails with a generic error until you log out and create a new session.

Common Mistakes to Avoid

• Refreshing the same errored query repeatedly without changing anything. If the first refresh did not help, the second and third will produce the same result. Change something — clear cache, disable VPN, switch modes — before retrying.
• Keeping a Perplexity tab open for hours and expecting it to work. Browser sessions degrade over time. If you use Perplexity in a long-lived tab, log out and back in periodically, especially if you notice the error appearing more frequently.
• Not testing in incognito mode. Incognito is the fastest way to rule out browser extensions as the cause. If you skip this step, you may spend time troubleshooting extensions when the issue is actually your network.
• Assuming it is a permanent account problem. "Something went wrong" almost never indicates an account-level issue. It is a transient error in the vast majority of cases. Do not contact support or attempt account recovery until you have completed all the steps above.
• Continuing to use a VPN you know causes the error. Once you have confirmed a VPN causes the issue on a specific server, using that server again will reproduce the error. Switch servers or disable split tunneling for perplexity.ai.

FAQ

Does "Something went wrong" mean Perplexity is down? Not necessarily. The error appears both during outages and for individual users with session or network problems. Check perplexity.ai/status to determine whether it is a service-wide incident. If the status page shows all systems operational, the issue is specific to your browser or network.

Why does the error appear in the middle of a response? A mid-response error means the streaming connection was interrupted before the response could complete. This is most often caused by a network drop, a browser extension intercepting traffic, or a response that hit a length or content limit. Refresh, disable extensions, and retry — if the same query consistently fails mid-response, try a shorter or rephrased version.

Does a VPN cause the "Something went wrong" error? Yes, frequently. Perplexity's streaming responses are sensitive to VPN-induced latency and traffic rerouting. If you are on a VPN, disable it and retry. If the error disappears, try a different VPN server location or add perplexity.ai to your VPN's split-tunnel exclusion list.

How do I know if my session expired? If you left Perplexity open for several hours in a background tab and now every query produces the error, session expiration is the most likely cause. Log out, close the tab, open a fresh session at perplexity.ai/login, and retry.

Why does the error happen more on Pro Search queries? Pro Search has a multi-step processing pipeline that takes longer and has more potential failure points. Complex or long queries are more likely to time out in Pro Search mode. Switch to Standard search for a more reliable response, then retry with Pro Search if needed.

What if clearing cache and logging back in does not fix it? Test in a different browser and on a different network (mobile hotspot). If the error disappears, your regular browser or network is the cause. If it persists everywhere, contact Perplexity support at perplexity.ai/settings with details about what queries trigger the error.

View all Perplexity guides