VERCEL ERRORS

Vercel domain connected but not loading: DNS, TLS or app error?

Your custom domain says connected but the site will not load. Compare the production deployment URL, DNS, certificate and redirect behavior to isolate the failure.

Domain connected, website not loading

Compare two URLs first

Open the production deployment URL and the exact custom hostname. If both fail with the same application error, investigate the app. If only the custom hostname fails, focus on DNS, domain assignment and TLS.

Checks in order

  1. Check the domain belongs to the intended Vercel project and its production deployment, rather than an old project or preview.
  2. Compare the authoritative DNS records with the values currently shown in Vercel. Do not copy an old IP address from a tutorial.
  3. Test the apex domain and www separately. Check certificate status, conflicting records and any proxy at the DNS provider.
  4. Inspect redirects for a loop between apex and www or between two applications. Keep one intended destination.

Connected is not an application health check

A dashboard configuration label does not prove that every route, login callback or API responds correctly.

Verify the actual destination

Request the homepage and a nested route over HTTPS from a fresh browser session. Keep the observed error and hostname when asking for help.

What a DeployDoctor scan can check

A repository scan can flag visible configuration risks. It cannot inspect dashboard settings, private credentials, DNS propagation or live service responses. Confirm the result in the deployed environment.

Sources

Documentation last checked 2026-11-15. Vercel can change its documentation; confirm against the linked pages.