After connecting a custom domain to your Website Studio site, you may occasionally see errors such as:
404 Page Not Found
Your connection is not private
This site canβt be reached
DNS not resolving
In most cases, this does not mean the setup failed. These issues usually happen while DNS changes or SSL certificates are still being processed.
Below are the most common causes and how to fix them.
π Understanding How Domain Connections Work
π Understanding How Domain Connections Work
Before troubleshooting, it's helpful to understand how your domain connects to Website Studio.
When someone visits your domain, the following process happens:
Visitor enters your domain
β
βΌ
DNS provider resolves your domain
β
βΌ
CNAME record points to Website Studio hosting
β
βΌ
Website Studio serves your site
β
βΌ
SSL certificate secures the connection
If any step in this chain is incomplete or misconfigured, your site may show errors.
π§© Cause 1 β DNS Has Not Fully Propagated
π§© Cause 1 β DNS Has Not Fully Propagated
The most common reason for domain errors is DNS propagation delay.
After adding your CNAME record, DNS updates must propagate across global DNS servers.
Typical propagation time:
β± A few minutes
β± Up to 24β48 hours
During this time, different users may see different results.
Some visitors may see:
the old website
a DNS error
a 404 page
while others already see the new site.
π How to Check DNS Propagation
You can verify your DNS record using:
https://dnschecker.org
Steps:
Enter your domain name
Select CNAME from the dropdown
Run the lookup
If your DNS record appears globally, propagation is complete.
π Cause 2 β SSL Certificate Is Still Being Generated
π Cause 2 β SSL Certificate Is Still Being Generated
After DNS is configured, Website Studio automatically creates an SSL certificate so your site can load securely via HTTPS.
Until SSL is issued, browsers may display:
Your connection is not private
or
NET::ERR_CERT_COMMON_NAME_INVALID
This is normal while SSL is provisioning.
π§ How to Trigger SSL Generation
Inside Website Studio:
1οΈβ£ Open your project
2οΈβ£ Go to Custom Domains
3οΈβ£ Click:
I have added the DNS records
The system will begin generating the SSL certificate.
Typical SSL activation time:
a few minutes
up to 1 hour
Once completed, your domain will load securely.
Example:
https://yourdomain.com
β Cause 3 β Incorrect CNAME Configuration
β Cause 3 β Incorrect CNAME Configuration
Another common issue is an incorrectly configured DNS record.
Verify that your DNS record looks like this:
Type | Name | Target |
CNAME | @ | yourproject.searchatlas.app |
Key points to verify:
β Type must be CNAME
β Target must match the Website Studio URL exactly
β No extra spaces or characters
β Only one CNAME exists for the same host
Some providers require using www instead of @.
Example:
Type | Name | Target |
CNAME | www | yourproject.searchatlas.app |
β οΈ Cause 4 β Conflicting DNS Records
β οΈ Cause 4 β Conflicting DNS Records
If your domain previously hosted another website, it may still contain old DNS records.
Common conflicting records include:
A records pointing to old hosting
existing CNAME records
default hosting provider records
These records may override the Website Studio configuration.
π§ How to Fix Conflicts
Open your DNS management panel and look for records such as:
A record β yourdomain.com
CNAME β www
Remove any records that conflict with your Website Studio setup.
Then keep only the required CNAME configuration.
π Cause 5 β DNS Managed by Another Provider
π Cause 5 β DNS Managed by Another Provider
Sometimes the domain registrar and DNS provider are different.
Example scenarios:
Domain purchased in GoDaddy
DNS managed in Cloudflare
or
Domain purchased in Namecheap
DNS managed in Hostinger
If you edit DNS in the wrong location, the changes will not apply.
π How to Check Your Nameservers
Go to your domain settings and review the nameserver configuration.
Example:
Nameservers
ns1.cloudflare.com
ns2.cloudflare.com
If Cloudflare nameservers are listed, DNS must be edited inside Cloudflare, not the domain registrar.
π§ Cause 6 β Browser Cache
π§ Cause 6 β Browser Cache
Sometimes your browser caches the old domain configuration.
Try the following:
refresh the page
open the site in Incognito mode
clear your browser cache
You can also test the domain from another device or network.
π¨ Cause 7 β Website Not Published Yet
π¨ Cause 7 β Website Not Published Yet
Your domain cannot connect if the Website Studio project is not published.
Verify that your site is accessible through the Website Studio public URL.
Example:
https://yourproject.searchatlas.app
If this link does not load, publish the site first.
Once DNS propagation and SSL generation are complete, your Website Studio site will load using your custom domain.
Example:
https://yourdomain.com
Your site will now be:
π Publicly accessible
π Secured with HTTPS
π Connected to your brand domain
