Custom domain troubleshooting
If a custom domain is not working yet, it is almost always DNS still propagating or one record entered slightly wrong. Here is what to check.
Common causes
- The records were only just added. They are still spreading across the internet, which can take a few minutes to a few hours.
- The Name or Value has an extra space or a typo. A single stray character stops a record from matching.
- The wildcard prefix was put in the wrong field. It belongs in the Name, not the Value.
- The certificate is still being issued. While this is happening, the status shows as Securing.
What to do
- Re-check both records against what SiteViewer shows. Compare the Name and the Value character by character, with no extra spaces.
- Wait a few minutes and refresh the status in Settings. DNS changes are not instant, so give them time to spread.
- The shared link stays on your built-in address until the certificate is verified, then it switches automatically. You do not have to do anything for that switch to happen.
Tip
A brand new domain can briefly show a security warning while the certificate spreads. SiteViewer keeps your client link on the safe built-in address until it is fully live, so a client never gets a broken link.
Was this helpful?Thanks for the feedback.