How to Fix Perplexity “Something Went Wrong”

Overview

Perplexity’s “Something went wrong” message is a generic failure state, not a diagnosis. It can appear when the web app cannot complete a request, the browser blocks a dependency, the session token is stale, the mobile app has bad local state, or an API request is malformed. Treat it as a troubleshooting path: confirm access, isolate the client, then inspect account, network, and developer-specific inputs. For official availability signals, use Perplexity-owned pages such as Perplexity’s official status page and product information from Perplexity’s official website.

Symptoms

The visible symptom is usually a generic “Something went wrong” response in the Perplexity web app, mobile app, browser extension, or developer workflow. The prompt may fail after submission, a thread may stop loading, a file or link action may not complete, or the UI may return to an empty state. In API use, the equivalent symptom may be a failed request rather than that exact UI text. Avoid over-reading the message. It does not prove a global outage, account ban, plan restriction, bad prompt, or browser defect by itself.

Why This Happens

This error usually sits at the boundary between Perplexity’s service, your authenticated session, and your local client. Browser extensions can block scripts or network calls. Privacy settings can reject cookies needed for sign-in. Corporate networks, VPNs, DNS filters, and captive portals can interrupt requests. Mobile apps can hold stale cache after an update or network switch. Developer environments add more failure modes: invalid authorization headers, unsupported request fields, request timeouts, or aggressive retries. The practical goal is to separate what you can prove locally from what only Perplexity can confirm, then avoid making destructive changes until one layer is clearly responsible.

Check Status, Account, and Basic Access

Start with the least destructive checks. Refresh once, then open a new Perplexity tab and submit a short plain-text prompt. If the same account fails everywhere, sign out and sign back in. If another account works on the same device, the issue may be account-scoped or feature-scoped. If no account works on multiple networks and devices, check Perplexity’s official channels before changing local settings. Perplexity’s status page is useful because it shows service state and incident updates separately from your browser session. For developer usage, compare the failing request with the authentication and request examples in Perplexity’s official API documentation, including the documented chat completions route, bearer-token authorization, JSON content type, model field, and messages array.

Try a Clean Browser or App Session

A clean client test is faster than guessing. In Chrome, Edge, Firefox, or Safari, open a private window and sign in again. If Perplexity works there, the likely cause is extension interference, cached site data, blocked cookies, or a browser profile setting. Disable ad blockers, script blockers, privacy extensions, and custom DNS tools one at a time. A strong reproduction path is to keep the same prompt, same account, and same network, then compare three runs: normal profile, private window, and clean profile. If only the normal profile fails, you have narrowed the problem to local browser state instead of Perplexity, your account, or the prompt itself. If the mobile app fails but the web app works, force-close the app, switch networks, and check for an app update through the official store. Avoid reinstalling until a clean browser or web test shows the issue is device-specific.

Check Files, Links, Prompts, and Feature Availability

If the error appears only on a specific task, simplify the input. Send a short prompt without links, uploads, pasted tables, unusual characters, or long context. If that succeeds, reintroduce the original elements in order. A single malformed URL, blocked document, expired share link, or unsupported file behavior can make the whole request fail. Do not assume an exact upload limit or plan rule unless Perplexity displays it or official documentation states it. Opinionated recommendation: for important work, draft the prompt locally first, then paste a smaller reproducible version into Perplexity before adding attachments.

Run Platform-Specific Checks

On desktop browsers, test with extensions disabled and allow cookies for Perplexity. On iPhone or Android, switch between Wi-Fi and mobile data, then restart the app. On managed work devices, check whether a proxy, secure web gateway, or VPN blocks AI services or streaming responses. For API clients, log the HTTP status code, response body, request ID if provided, endpoint, model name, and retry behavior. Do not keep retrying blindly; repeated failed requests can hide the original error behind throttling, timeout, or queue behavior.

$ curl -i https://api.perplexity.ai/chat/completions \
  -H "Authorization: Bearer $PERPLEXITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"sonar","messages":[{"role":"user","content":"Say hello in one sentence."}]}'
This follows Perplexity's documented chat completions pattern: POST request, bearer token, JSON body, model, and messages array.
⚠ Do not paste API keys into screenshots or support tickets.

Developer Workflow Checks

For API or automation failures, treat “Something went wrong” as a transport or request-validation problem until logs prove otherwise. Confirm the base URL, route, method, authentication header, content type, JSON shape, model identifier, and timeout settings. Then test the smallest possible request from a terminal or API client. If your app streams responses, check whether the frontend handles partial chunks, aborted connections, and server-sent events correctly. The lesser-known gotcha: many teams debug the model layer first, but the failure often sits in middleware that strips the Authorization header, rewrites JSON, buffers streaming responses, or times out long requests before Perplexity can return the useful error.

When to Use Perplexity and When Not To During an Error

Use Perplexity for research tasks when the web app or API can complete a clean, reproducible prompt and you can inspect the answer sources. Avoid relying on it as the only tool in a production workflow while the same account or integration is returning generic failures. For operational work, keep a fallback search path, cached notes, or another research tool available. This is not about distrust; it is about blast radius. A generic UI error gives too little diagnostic detail to be your only dependency during a deadline.

If It Still Fails

If the error survives a clean browser, another device, another network, and a minimal prompt, escalate with evidence. Capture the timestamp, browser and OS, whether private mode worked, whether mobile and desktop differ, and the smallest prompt that reproduces the issue. For API cases, include HTTP status, endpoint, sanitized request body, and sanitized response body. Use official Perplexity support or help routes rather than community guesses for account-specific issues. Do not include passwords, session cookies, API keys, private documents, or customer data in screenshots or tickets.

FAQ

Why does Perplexity say “Something went wrong”?

It means the request failed somewhere in the app, session, network, account, or API path. The message is generic, so it does not identify the exact cause by itself.

Is Perplexity down when I see this error?

Not necessarily. Check Perplexity’s official status page and test another browser, device, or network before treating it as a service-wide issue.

Should I clear my browser cache?

Try a private window or clean browser profile first. If that works, clear Perplexity site data or disable extensions before deleting all browser data.

Can browser extensions cause this error?

Yes. Ad blockers, script blockers, privacy extensions, VPN extensions, and corporate security tools can block scripts, cookies, or network requests that the app needs.

What should I do if the mobile app fails but the website works?

Force-close the app, switch networks, check for an app update, and test the same prompt on the web. If only the app fails, the issue is likely local to the device or app state.

How do I troubleshoot Perplexity API failures?

Log the HTTP status, sanitized response body, endpoint, authentication header format, JSON body, model value, timeout settings, and retry behavior. Compare the request with Perplexity’s official API documentation.

When should I contact support?

Contact support when the issue reproduces after clean browser, device, network, and minimal-prompt checks, or when it appears tied to your account, billing, workspace, or API access.