Custom Domain Not Connecting to Base44 App

You've configured a custom domain for your Base44 app, but visiting the domain shows an error page, a default hosting page, or the connection times out entirely. The app continues to work on the default Base44 URL but not on your custom domain.

Custom domain configuration involves DNS settings that must be precisely correct, and errors in this process are common. The issue may be compounded by DNS propagation delays that make it hard to tell if your changes have taken effect.

Some users experience a partially working state: the domain loads but shows SSL certificate warnings, or it works without www but not with www (or vice versa).

Error Messages You Might See

  • DNS_PROBE_FINISHED_NXDOMAIN
  • ERR_SSL_PROTOCOL_ERROR
  • This site can't be reached
  • SSL certificate problem: unable to get local issuer certificate

[DNS_PROBE_FINISHED_NXDOMAIN](/content/guides/search?q=DNS_PROBE_FINISHED_NXDOMAIN "Search for this error"/index.html)
[ERR_SSL_PROTOCOL_ERROR](/content/guides/search?q=ERR_SSL_PROTOCOL_ERROR "Search for this error"/index.html)
[This site can't be reached](/content/guides/search?q=This%20site%20can%27t%20be%20reached "Search for this error"/index.html)
[SSL certificate problem: unable to get local issuer certificate](/content/guides/search?q=SSL%20certificate%20problem:%20unable%20to%20get%20local%20issuer%20certificate "Search for this error"/index.html)

Common Causes

  1. The CNAME or A record was not set correctly in the domain registrar's DNS settings
  2. DNS propagation has not completed yet (can take up to 48 hours)
  3. The custom domain was configured in Base44 but the DNS records point to the wrong target
  4. SSL certificate has not been provisioned yet for the custom domain
  5. The www and non-www versions are not both configured, causing one to fail

How to Fix It

Verify your DNS records using a tool like dnschecker.org to confirm the CNAME or A record is correctly set and has propagated. The target should match exactly what Base44's custom domain instructions specify.

If the DNS is correct but SSL shows a warning, the SSL certificate may still be provisioning. This can take up to an hour after DNS propagation completes.

For persistent custom domain issues, especially with subdomains, wildcard certificates, or complex DNS setups involving other services (like email on the same domain), a developer can help configure everything correctly.

Frequently Asked Questions

How long does it take for a custom domain to work with Base44?

DNS propagation can take up to 48 hours, and SSL certificate provisioning can take an additional hour after that. Wait at least 24 hours before troubleshooting further.

What DNS records do I need for a custom domain on Base44?

You typically need a CNAME record pointing to the Base44-provided target URL. Check the exact instructions in your Base44 app's domain settings for the correct target value.