Perplexity Error 403 – How to Fix Forbidden Error

PerplexityErrors & BugsUpdated May 17, 2026
Quick Answer

Perplexity error 403 means Forbidden — your request was understood but blocked. The three most common causes are: regional restrictions (Perplexity is unavailable in some countries), account-level restrictions (your account was flagged or your subscription lapsed), and content policy blocks (the specific query was rejected). Start by disconnecting any VPN, then checking your account status at perplexity.ai/settings/account, then clearing cookies and logging back in.

Step-by-Step Fix

Step 1. Identify What Type of 403 You Are Seeing

A Perplexity 403 error can appear in several forms:

  • "403 Forbidden" — direct HTTP error shown in browser or API response
  • "Access denied" — account-level restriction
  • "This content is not available in your region" — geographic restriction
  • "Your request was blocked" — content policy filter

The message gives you an important clue. A regional message points to VPN or location issues. An access denied message points to your account. If there is no additional context, work through the steps below in order.

Step 2. Disconnect Your VPN Completely

VPNs are the most common cause of 403 errors on Perplexity. Even if you use a VPN for other services without issue, Perplexity may block the specific exit IP address or exit country your VPN is using.

  1. Fully disconnect your VPN — do not just pause it or switch servers initially; quit the application
  2. Reload Perplexity in a fresh tab
  3. Attempt your search or API call again
  4. If the 403 is gone, your VPN exit IP or exit country was the cause

If you need a VPN and Perplexity works without it, try switching to a different VPN server in a supported country (United States, United Kingdom, Germany, and Canada are generally reliable). Avoid shared VPN servers as their IP addresses are more likely to be blocklisted.

Step 3. Check Your Account Status

If disconnecting the VPN does not resolve the 403:

  1. Go to perplexity.ai/settings/account and check that your account is in good standing
  2. If you have a Perplexity Pro subscription, verify your payment method is current — a lapsed payment can downgrade your access level and trigger 403 errors on Pro-only features
  3. Check for any emails from Perplexity about policy warnings or account restrictions
  4. If your account appears to be restricted, contact support@perplexity.ai with your account email and a description of when the errors started

Step 4. Clear Cookies and Log Back In

A corrupted session cookie can cause Perplexity's server to reject your requests with a 403 even when your account is fine. Clear the session completely and start fresh.

Chrome / Edge:

  1. Press Ctrl+Shift+Delete (Windows) or Cmd+Shift+Delete (Mac)
  2. Set time range to All time
  3. Check Cookies and other site data (also check Cached images and files)
  4. Click Clear data
  5. Reload perplexity.ai and log in again

Firefox:

  1. Press Ctrl+Shift+Delete
  2. Set time range to Everything
  3. Check Cookies and Cache
  4. Click Clear Now
  5. Reload and log in

For a targeted cookie clear in Chrome: go to Settings → Privacy and Security → Cookies and other site data → See all site data → search "perplexity" → click the trash icon to remove only Perplexity's data without affecting other sites.

Step 5. Try a Different Network

If the 403 persists after clearing cookies and disconnecting your VPN, your network itself may be the issue. Corporate networks, school networks, and some ISPs block access to AI services.

  1. Switch to your phone's mobile data hotspot and connect your computer to it
  2. Reload Perplexity in a fresh browser tab
  3. If it works on mobile data: your main network (router, ISP, or corporate firewall) is blocking Perplexity
  4. Contact your network administrator if you are on a corporate or school network, as these often require whitelist requests for AI services

Step 6. For API Users — Check Permissions and Endpoint

If you are receiving 403 via the API:

  1. Confirm your API key has the necessary permissions for the endpoint you are calling — some endpoints require specific subscription tiers
  2. Verify you are using the correct base URL: https://api.perplexity.ai
  3. Check that your account's API access is enabled at perplexity.ai/settings/api
  4. If you are on a free plan, note that API access requires a paid Perplexity subscription

Step 7. Contact Support

If none of the above steps resolve the 403:

  1. Go to perplexity.ai/contact or email support@perplexity.ai
  2. Include: your account email, the exact 403 error message, your location (country), whether you use a VPN, and when the error started
  3. For API users: include the endpoint URL, your request headers (with API key redacted), and the full response body

Why This Happens

A 403 Forbidden error means your identity is known but your access is denied. Unlike a 401 error where authentication is missing, a 403 tells you that Perplexity knows who you are but has decided your request cannot be fulfilled. The most common triggers are:

  • Geographic IP blocks: Perplexity checks the IP address of every incoming request against a list of allowed regions. If your IP — real or VPN-assigned — resolves to a restricted country, all requests return 403 regardless of your account status.
  • Content policy enforcement: Perplexity runs real-time content moderation. Queries that match patterns associated with prohibited content are blocked at the request level with a 403 before reaching the AI model.
  • Account-level restrictions: Repeated policy violations, unusual automated usage patterns, or payment failures can flag an account for restricted access, causing 403 errors across all requests from that account.

Common Mistakes to Avoid

  • Assuming 403 and 401 are the same — they require different fixes. A 401 means "who are you?" and is fixed by logging in. A 403 means "I know who you are but you cannot access this" and requires checking permissions, region, or account standing.
  • Switching VPN servers without fully disconnecting first — some VPN clients keep partial connections active even when "switching servers." Fully quit the VPN application before testing.
  • Retrying the same blocked query repeatedly — if Perplexity's content filter blocked your query, sending it again will not help and may escalate the restriction on your account.
  • Ignoring subscription status — a lapsed Pro subscription silently revokes access to Pro features and returns 403 errors on those endpoints. Check your billing status before deep troubleshooting.
  • Not testing on mobile data — testing on a completely different network (mobile hotspot) is the definitive way to determine whether the problem is your main network or your account.
  • Contacting support without testing basic steps first — Perplexity support will ask you to test these steps before escalating. Completing them first speeds up the resolution significantly.
  • Mixing up 403 and 401 — a 401 is fixed by logging in. A 403 means you are logged in but blocked. If you clear cookies and re-login and still get 403, do not just keep re-logging in — investigate account status or regional access.

Perplexity 403 and API Access Restrictions

API users encounter 403 errors for reasons different from web users. If you are building with the Perplexity API and receiving 403:

  • Free accounts cannot access the API — Perplexity requires a paid plan (Pro or API plan) for programmatic access. If your account is on a free tier, upgrade at perplexity.ai/settings/account.
  • Endpoint-specific access — some Perplexity API endpoints may require a higher subscription tier. Confirm which endpoints are included in your current plan.
  • IP rate limiting — exceeding API rate limits can temporarily return 403 responses. Check the API documentation for rate limits and implement exponential backoff in your request logic.
  • Deprecated endpoints — old API endpoint URLs that have been retired return 403. Confirm you are using the current base URL: https://api.perplexity.ai with the current endpoint paths.

Is Perplexity Available in Your Country?

Perplexity is accessible in most countries but has access restrictions in some regions. If you consistently get 403 errors without any VPN and across multiple networks in the same country, regional availability may be the cause. Signs that this is the issue:

  • The error appears on every network in your location (mobile data, home Wi-Fi, office Wi-Fi)
  • Other people in the same country report the same issue
  • The 403 disappears when you use a VPN with a US or European exit server

Contact support@perplexity.ai to inquire about access for your specific region, as restrictions can change.


Quick Summary: Perplexity 403 Fix Checklist

Work through this checklist in order — most 403 errors are resolved by step 3:

  1. Disconnect VPN completely and reload Perplexity
  2. Check perplexity.ai/settings/account — confirm account is active and subscription is current
  3. Clear all cookies for perplexity.ai and log back in fresh
  4. Switch to a different network (phone mobile hotspot) to rule out network-level blocking
  5. For API: confirm your account has API access and you are using the correct endpoint URL
  6. If all above fail: contact support@perplexity.ai with your account email and error details

View all Perplexity guides

Perplexity · Errors & Bugs

More Perplexity errors & bugs guides

Browse all guides in this category to troubleshoot related issues faster.

Browse all guides →

Frequently Asked Questions

HTTP 403 Forbidden means Perplexity's server received and understood your request, but is refusing to fulfill it because you do not have permission. This is different from a 401 error where the server cannot verify your identity. With 403, your identity is known but your access is restricted. Common reasons include geographic restrictions (your country or IP is blocked), account-level restrictions (plan limits, policy violations, or a suspended account), and content-level filters (the specific content you requested violates Perplexity's usage policies).

Related Guides

Continue with nearby guides in the same topic to rule out adjacent causes faster.

Perplexity Citations Not Loading or Sources Missing – How to Fix

Perplexity citations fail to load in over 70% of cases because an ad blocker or privacy extension is blocking the source-fetching requests that run alongside the AI response. Disable your ad blocker (uBlock Origin, AdGuard, Ghostery) for perplexity.ai, reload the page, and run your query again — citations should appear as numbered blue links below the answer. If the problem continues, switch from Pro Search to Standard Search as a quick test, then clear your browser cache.

Perplexity Error 401 – How to Fix Unauthorized Error

Perplexity error 401 means Unauthorized — your session has expired or your API key is invalid. For web users, log out at perplexity.ai/settings/account, clear cookies, and log back in. For API users, check that your key is active at perplexity.ai/settings/api and that you are sending it as a Bearer token in the Authorization header. A 401 error is never caused by Perplexity's servers — it is always an authentication issue on your end.

Perplexity Error 500 – How to Fix Internal Server Error

Perplexity error 500 is an Internal Server Error — the problem is entirely on Perplexity's servers, not your device or network. There is no local fix. Check perplexity.ai/status to see if an incident is active, then wait 5 to 15 minutes before retrying. Most Perplexity 500 errors resolve automatically within 15 minutes as the server recovers. If the error persists beyond 30 minutes, report it at perplexity.ai/contact.

Perplexity Error in Processing Query: Causes and Fixes

The 'Error in Processing Query' message on Perplexity appears when your query is too long or complex for the model to process, contains phrasing that triggers content filters, or when a backend service times out mid-response. The fastest fix is to shorten your query to under 500 characters, remove ambiguous or sensitive phrasing, and resubmit. If the error persists across multiple queries, check perplexity.ai/status for an ongoing service incident.

Perplexity Error Messages – What They Mean and How to Fix

Perplexity error messages fall into three groups: rate limit errors (too many requests — wait 60 seconds or upgrade your plan), service errors (something went wrong, network error — refresh the page or check perplexity.ai/status), and query errors (error processing query, content policy — rephrase or shorten your search). The fix depends on which error you see. This guide covers the 10 most common Perplexity error messages with specific solutions for each.

Perplexity 'Something Went Wrong': API Failures and Service Timeouts Fixed

The 'Something Went Wrong' error on Perplexity signals a technical failure in the backend — typically an API call failure, model endpoint timeout, or web retrieval service error — rather than a user-facing input problem. This error is distinct from the generic 'Error in Processing Query' message, which usually involves query content. For 'Something Went Wrong,' wait 30 to 60 seconds and retry; if the error persists for more than 5 minutes, check perplexity.ai/status for an active incident.