Skip to main content

T2. Domain not working

What this page helps you do​

Debug the common reasons your domain does not reach the app correctly.

Why it matters​

A lot of launch stress comes from not knowing whether the problem is the app, the hosting provider, the DNS records, or the HTTPS layer.

You should already have​

  • a deployed app
  • a domain you control

Skip this page if​

  • the app itself is not healthy yet

Then go to T1. App works locally but not online.

What to do​

Check these in order:

  1. Is the app reachable on the platform URL or server IP?
  2. Is the custom domain added inside the hosting platform if required?
  3. Does the DNS record point to the correct target?
  4. Are you editing DNS in the correct provider?
  5. Has enough time passed for the change to spread?
  6. Is the HTTPS layer failing after the DNS part is already correct?

Common patterns:

  • wrong A or CNAME record
  • Cloudflare is active, but the nameservers were never changed
  • the root domain works but www does not
  • the domain points correctly, but the host has not accepted that domain yet

Change one DNS thing at a time and write down what changed.

Common mistakes​

  • changing records in two places
  • checking too soon and assuming failure
  • forgetting that email-related DNS records may also matter during a provider move

Next step​

If the domain points correctly but secure loading still fails, go to T3. HTTPS not working.

Advanced notes​

When in doubt, prove the chain one step at a time: app works, platform URL works, custom domain is added, DNS points correctly, HTTPS finishes successfully.