Skip to main content
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 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.

Deployments

Failed builds, startup failures, 502 errors, and differences from Preview.

App authentication

Identify your auth provider and troubleshoot sign-in and environment issues.

Databases

Connection errors, paused endpoints, missing data, and safe recovery checks.

Domains

DNS verification, HTTPS, wrong-site responses, and auth-related domain errors.

​
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.
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.

​
When to contact Support

Contact Replit 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.