[← All docs](/docs)

# My domain isn’t working — troubleshooting

Common things that go wrong, and what to do about each. If none of these match, email [support@webegg.ai](mailto:support@webegg.ai) with your domain name and a screenshot of the error.

## “This site can’t provide a secure connection” / SSL error

**Most likely cause:** you typed the bare domain (`yourdomain.com`) but the SSL certificate hasn’t been issued there yet — usually because you skipped the URL forwarding step. Try the `www` version: `https://www.yourdomain.com`. If that works, you just need to add URL forwarding for the bare domain (Step 2 of the [Connect a custom domain](/docs/custom-domain) guide).

**Less likely cause:** the DNS record was added very recently and the certificate is still being issued. Wait 15–30 minutes and try again.

## “Cloudflare Error 1001” / “DNS resolution error”

Same root cause as the SSL error above — you’re visiting the bare domain but it isn’t set up to serve traffic. Set up URL forwarding from the bare domain to the www version (Step 2 in the [setup guide](/docs/custom-domain)).

## “DNS_PROBE_FINISHED_NXDOMAIN” / “This site can’t be reached”

Your browser can’t find the domain at all. Two possibilities:

- **The DNS record hasn’t saved or hasn’t propagated.** Check at [dnschecker.org](https://dnschecker.org) — type your domain, set the type to `CNAME`, and look up `www.yourdomain.com`. If it’s missing globally, the record didn’t save. Re-add it at your registrar.

- **You typo’d the domain.** Worth double-checking.

## www works but the bare domain doesn’t (or vice versa)

You probably did Step 1 (the `CNAME www` record) but skipped Step 2 (the URL forwarding). Go back to your registrar and set up the forwarding for the bare domain.

## Dashboard says “AWAITING DNS” for over an hour

That usually means one of:

- The `CNAME` record at your registrar has a typo — double-check the value against what’s shown in your dashboard.

- You added the record under the wrong hostname — it should be `www`, not `@` or the full domain.

- There’s a conflicting `A` record on `www` blocking the `CNAME`. Most registrars warn you about this; if not, delete the `A` record and the `CNAME` should take effect.

## My old domain works for a few hours, then breaks

This usually means DNS still has a cached pointer to your old site. Wait it out — the cache expires based on the old record’s TTL (usually 1–24 hours). Once it expires, the new record takes over and your site stabilizes.

## Email stopped working after I connected the domain

This shouldn’t happen with the standard setup (we don’t touch email records). But if you changed nameservers as part of an unrelated change, your `MX` and `TXT` records may have been left behind. See the [email guide](/docs/email-on-your-domain), then email [support@webegg.ai](mailto:support@webegg.ai) — we can help you recover the records.

## I see the wrong content on my domain

Try an incognito / private window first — browsers cache aggressively and may be showing you an old version. Also try your phone on cellular (not Wi-Fi). If the content is still wrong after that, email us with the domain and a screenshot.

## None of the above

Email [support@webegg.ai](mailto:support@webegg.ai) with:

- Your domain name

- What you see in the browser (a screenshot is perfect)

- Whether `www.yourdomain.com` works (yes / no)

- Whether `yourdomain.com` (no www) works (yes / no)

We respond same day.

[← Back to all docs](/docs)