"Your connection is not private" after going live
Security & SSL
Just switched your site to its real domain and now seeing a browser warning like "Your connection is not private", NET::ERR_CERT_COMMON_NAME_INVALID, or "Not secure"? Don't worry — your site and your data are fine. This almost always just means the secure certificate for your domain is finishing its setup, or your browser is holding on to a cached copy of the old version.
Fix it in two steps
- Wait about 5 minutes. When a domain goes live, the secure certificate can take a few minutes to finish activating.
- Do a hard refresh. Close the browser tab completely
and reopen it, or press
Ctrl+Shift+R(Windows) /Cmd+Shift+R(Mac). This clears the cached version your browser is still showing.
Trying it in a private/incognito window is another quick way to confirm — if it loads securely there, your browser was just caching the old page.
Still seeing it?
If the warning is still there after waiting a few minutes and refreshing, open a support ticket and let us know your domain. We'll take care of it on our side — there's nothing you need to configure.
For WordPress
Make sure your WordPress URL settings use https://:
- Go to Settings → General
- Ensure both URL fields start with
https:// - Save changes
Mixed content warnings
If your browser shows a "Not Secure" warning despite having SSL, you likely have mixed content — some resources (images, scripts) loading over HTTP. Use a plugin like "Really Simple SSL" to fix this automatically.