A big red warning instead of your website? "Your connection is not private" (NET::ERR_CERT_...) means the browser doesn't trust the SSL certificate it was given. Visitors get scared off, so let's fix it.
1. Was the domain just moved or pointed to Romeo?
An SSL certificate can only be issued after your domain points to Romeo. If you changed nameservers recently, wait for propagation, then ask Romeo to issue the certificate (or order the Letsencrypt SSL addon).
2. Check what the warning says
Click Advanced (or the warning text) to see the error code:
| Error | Usual cause |
|---|---|
| ERR_CERT_COMMON_NAME_INVALID | the certificate doesn't include this exact name, often www or a subdomain |
| ERR_CERT_DATE_INVALID | the certificate has expired, or your computer's date is wrong |
| ERR_CERT_AUTHORITY_INVALID | a self-signed or server certificate is being used instead of a real one |
3. Common fixes
- Missing www or subdomain: the certificate must cover every name you use. Ask Romeo to include www and your subdomains.
- Expired certificate: renew it (Let's Encrypt renews automatically once it's set up correctly).
- Your computer's clock is wrong: fix the date and time on your device.
- Cloudflare users: set SSL/TLS to Full, and make sure Romeo's server also has a valid certificate.
4. Mixed content (padlock missing, but no red warning)
That's a different issue: some images or scripts load over http://. See How to secure your website with SSL (HTTPS).
Still seeing the warning? Open a ticket with your domain and a screenshot of the error, and Romeo will put the padlock back.






