These answers cover connecting and troubleshooting custom domains. For full reference, see Add a custom domain and Custom domains.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.
How do I connect a custom domain to my Replit app?
How do I connect a custom domain to my Replit app?
If you bought your domain through Replit, the DNS records are managed for you—open Publishing → Domains and follow the in-product setup. See Domain purchasing.To connect a domain from an external registrar:
- Open your project and go to Publishing → Domains.
- Select Connect your own domain, enter your domain, and continue.
- Replit shows an A record and a TXT record—copy both.
- Add both records at your DNS provider.
- Return to Replit and start verification.
- Both an A record and a TXT record are required for SSL. Apex (root) CNAMEs aren’t supported—use an A record for your root domain.
- Wildcard certificates (
*.example.com) aren’t supported; connect each subdomain individually. - On Cloudflare, set your A record to DNS only (the grey cloud) so proxy mode doesn’t block SSL setup.
- DNS changes can take up to 48 hours to propagate.
My domain isn't verifying or SSL isn't provisioning—how do I troubleshoot?
My domain isn't verifying or SSL isn't provisioning—how do I troubleshoot?
Work through these checks in order—most issues come from one of them:
- Wait for DNS to propagate. Changes can take up to 48 hours. Confirm your records are visible globally with a DNS lookup tool.
- Remove AAAA records. IPv6 (AAAA) records on the same hostname as your A record can block SSL.
- Remove old or conflicting A records. Keep only one A record at your root domain pointing to Replit.
- Set Cloudflare to DNS only. The orange cloud (proxy mode) interferes with SSL provisioning.
- Disconnect and reconnect the domain in Publishing → Domains → Manage to force a fresh certificate, then wait a few minutes and reload.
- Check CAA records. If you have CAA records, at least one must allow Let’s Encrypt as an issuer, since Replit issues certificates through it.
How do I set up Clerk authentication on a custom domain?
How do I set up Clerk authentication on a custom domain?
A few issues commonly come up when using Clerk authentication on a custom domain:
- “Clerk CNAME records required” warning. This is a Clerk integration requirement and doesn’t block your domain’s verification or SSL. Open Publishing → Domains, select Manage, find the authentication DNS setup section, and add each listed CNAME record exactly at your DNS provider. If the section doesn’t appear, disconnect and reconnect the domain.
- Domain stuck on Verifying after prior Clerk use. If the domain was attached to a different Clerk application, remove it there in your Clerk dashboard, then disconnect and reconnect the domain in Replit.
- Migrating to your own Clerk instance. Switching from Replit-managed Clerk to your own instance requires a manual step—contact Replit Support. See Clerk auth migration.