SSL certificate issues
Why a certificate is not issued, why the browser shows a warning, and how to fix validation without hitting rate limits.
Certificates on Zoophost are free and automatic. Almost every problem is one of three things: DNS does not point here, a proxy is in the way, or the request was retried too often.
First, identify the symptom
| Symptom | Likely cause |
|---|---|
ERR_CERT_AUTHORITY_INVALID |
No certificate issued for this name; the server is presenting a default |
NET::ERR_CERT_COMMON_NAME_INVALID |
Certificate exists for a different hostname |
ERR_CERT_DATE_INVALID |
Certificate expired or the client clock is wrong |
| “Not secure” with a valid certificate | Mixed content (assets loaded over HTTP) |
| Redirect loop | Force HTTPS plus an upstream that also forces HTTPS |
Works on www, fails on apex |
Only one of the two is attached |
Check what the server presents
openssl s_client -connect yoursite.com:443 -servername yoursite.com </dev/null 2>/dev/null \
| openssl x509 -noout -subject -issuer -dates
- Subject should be your hostname.
- Issuer should be a public CA (Let's Encrypt).
- Dates should cover today.
If the subject is a different site, the hostname is not attached to your app and the platform is using its default certificate.
The common causes
DNS does not point at Zoophost
A certificate cannot be issued for a name that resolves elsewhere. Check the app's Domains card:
- Points here — good.
- Does not point here — fix the record.
- No A record yet — create it.
- Not a hostname — the value is malformed.
A proxy is in front of the origin
If the domain uses Cloudflare or another proxy, HTTP validation may reach the proxy instead of the origin.
- Set the record to DNS only while the certificate is issued.
- Re-enable proxying after the certificate is active.
- Make sure the proxy's SSL mode reaches the origin over HTTPS.
You retried too often
Let's Encrypt limits failed validations to 5 per hostname per hour. Once you hit it, every retry fails until the window passes, even after DNS is fixed.
Fix the cause, wait for the window, then try once. Do not click “retry” in a loop.
Port 80 is blocked
Validation uses HTTP on port 80 by default. A firewall, a redirect rule, or a proxy that only forwards 443 breaks it.
www and apex are separate
They are separate hostnames with separate certificates. Add both to the app and create both DNS records.
Mixed content
The certificate is fine but the page requests http:// resources. Browsers block them and show “Not secure”.
- Update absolute URLs to
https://or to relative paths. - Set the framework's public URL/base URL to the HTTPS domain.
- Check hard-coded image, script and font URLs in the database or CMS settings too.
Redirect loops
A loop usually means both layers redirect:
- The app redirects HTTP to HTTPS.
- The proxy also redirects, or the app sees the request as HTTP because the forwarded header is missing.
For apps behind the Zoophost proxy, make sure the app trusts the X-Forwarded-Proto header, or disable the app-level redirect and let Force HTTPS handle it.
HSTS
If you enabled HSTS, browsers will refuse HTTP for that hostname until the max-age expires. Be careful with long max-age values before the certificate is confirmed working. There is no quick undo: you must serve a valid certificate and wait, or ask users to clear HSTS settings.
After fixing DNS
- Wait for propagation. Test with a public resolver.
- Confirm the name resolves to the Zoophost address.
- Let the platform retry once, or open a ticket with the hostname and the time you fixed DNS.
- Re-enable any proxy after the certificate is live.
When to contact support
Open a ticket with the hostname if:
- DNS points here and the certificate still has not issued after an hour.
- You hit the validation rate limit and need help waiting it out.
- The certificate is valid but the browser still warns, and mixed content is ruled out.
- A domain shows as attached but no certificate appears for it.
Next
- ssl
- tls
- certificate
- lets encrypt
- https
- mixed content
- hsts
Ready to use this
If the guide did not fix it, tell us what you already tried.
- A real support thread, not a bot loop
- Support in IST

