Common Issues
deployment
SSL Certificate Error or Site Not Secure Warning
Your app shows a 'Not Secure' warning in the browser, or visitors see a full-page SSL/TLS certificate error warning them the site is unsafe. This scares users away and can break functionality like payments and auth.
Common Causes
- SSL certificate not installed or expired
- Custom domain not properly configured with your hosting provider
- Mixed content — HTTPS page loading HTTP resources
- DNS records not pointing to the correct server
- Hosting provider doesn't auto-provision SSL for custom domains
How to Fix It
- Check if your hosting provider offers free SSL (most do — Vercel, Netlify, Railway auto-provision)
- Verify your DNS records are correct (A record or CNAME pointing to your host)
- If using a custom domain, check the hosting provider's domain settings for SSL status
- Look for mixed content warnings in the browser console and update HTTP URLs to HTTPS
- Wait up to 24 hours after DNS changes for SSL to provision
Real developers can help you.
Describe what's wrong in plain English. No technical knowledge needed.
Get HelpFrequently Asked Questions
My site shows 'Not Secure'. Will this affect my business?
Yes. Browsers warn users away from non-HTTPS sites, payment providers require HTTPS, and Google penalizes non-HTTPS sites in search rankings. Fix this as soon as possible.
I added a custom domain and now SSL is broken. What happened?
Your hosting provider needs to provision an SSL certificate for your custom domain. Check their domain settings — most do this automatically but it can take a few hours.