Troubleshooting
Custom Domain Not Resolving
Fix a custom domain that does not load or shows a TLS error by copying the exact DNS record, waiting for propagation, and binding it to an HTTP port.
After adding a custom domain, it can take a little while to work. Most issues come down to DNS.
Checklist
- Use the exact record shown. Open the DNS dialog for your domain and copy the record exactly. A subdomain uses a CNAME, and a root domain uses an A record.
- Wait for propagation. DNS changes take 5 to 30 minutes to take effect. A new certificate is issued automatically once the record resolves, so an early TLS warning usually clears on its own.
- Connect it to an app and port. A domain that is not bound to an application shows as not routed. Bind it to an HTTP or H2C port. A TCP port cannot take a custom domain.
- Check the path. If you route by path, make sure the path matches. The path
/.well-known/acme-challengeis reserved for certificate renewal.
A new or changed route applies on the application's next deployment.
Related
Port Not Detected
Fix an app that shows Running but whose URL times out or returns nothing by binding to 0.0.0.0, matching the port, and making the port public.
Can't Connect to PostgreSQL
Fix connection errors between your app and managed PostgreSQL by using the console's connection string, requiring SSL, and checking the role and database.