> ## Documentation Index
> Fetch the complete documentation index at: https://docs.replit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting guides

> Find a safe troubleshooting path for publishing, app authentication, databases, and custom domains, and collect useful details before contacting Support.

Start with the symptom you can observe. A failed request alone does not tell you
whether the cause is your app, its configuration, an external service, or Replit.

Check [Replit Status](https://status.replit.com) for an incident matching your
symptoms. If one matches, follow its updates. If none matches, continue
troubleshooting: the absence of an incident does not rule out an isolated issue.

<CardGroup cols={2}>
  <Card title="Deployments" icon="rocket" href="/help/troubleshooting/deployments">
    Failed builds, startup failures, 502 errors, and differences from Preview.
  </Card>

  <Card title="App authentication" icon="lock" href="/help/troubleshooting/auth">
    Identify your auth provider and troubleshoot sign-in and environment issues.
  </Card>

  <Card title="Databases" icon="database" href="/help/troubleshooting/databases">
    Connection errors, paused endpoints, missing data, and safe recovery checks.
  </Card>

  <Card title="Domains" icon="globe" href="/help/troubleshooting/domains">
    DNS verification, HTTPS, wrong-site responses, and auth-related domain errors.
  </Card>
</CardGroup>

## Before changing anything

* Record the exact error and when you observed it, including your timezone.
* Compare Preview, the published `replit.app` URL, and any custom domain.
* Save relevant logs after removing credentials, personal data, and session tokens.
* Make one targeted change at a time and repeat the same check.

<Warning>
  Do not delete a database, authentication tenant, deployment, or domain as a
  general troubleshooting step. Recovery, migration, and deletion can affect
  production data and users. Understand the impact and preserve recoverable data first.
</Warning>

## When to contact Support

[Contact Replit Support](https://replit.com/support) when safe checks do not
resolve the problem, access to platform-managed configuration is needed, or
data loss is possible. You do not need to keep repeating unsuccessful steps.

Include your project URL, affected environment, sanitized error, time and
timezone, user impact, recent changes, and the checks you tried with their results.
Label anything you have not verified. Never include secret values, connection
strings containing credentials, login codes, or session cookies.