Why does my site show "Not Secure"?
If your browser shows a "Not Secure" warning when visiting your wedding website, it's usually related to SSL certificate configuration.
Short answer: SSL certificates are automatically provisioned but may take up to 24 hours. If using a custom domain, ensure DNS is configured correctly.
Common causes
1. SSL certificate is still being provisioned
When you first create your site or add a custom domain, the SSL certificate needs time to be issued:
- This typically takes 15-30 minutes
- In some cases, it can take up to 24 hours
- Try refreshing the page after waiting
2. Custom domain DNS not properly configured
If you're using a custom domain:
- Verify your CNAME records are set correctly
- Don't use "Forward with masking" - this prevents SSL from working
- Make sure both www and non-www versions point to WedSites
- Check that you only have one A record for @ pointing to 37.16.10.26 — extra A records from your registrar or other services can cause SSL warnings to appear intermittently
3. Mixed content on the page
If your site loads but shows a warning:
- You may have embedded content (images, scripts) using http:// instead of https://
- Check any custom HTML sections for insecure links
- External embeds should use https:// URLs
How to fix it
- Wait: If you just set up your domain, wait 24 hours for SSL provisioning
- Check DNS: Verify your CNAME records match what WedSites provided
- Contact support: If the issue persists after 24 hours, reach out for help
Tips
- Your wedsites.com subdomain always has SSL enabled
- Avoid domain forwarding or masking - use direct CNAME records
- Clear your browser cache after DNS changes propagate