Certificate Status Issues
Certificate shows “error” status
Cause: We couldn’t establish a connection to retrieve the certificate. Solutions:- Verify the domain is publicly accessible (try
curl -v https://yourdomain.com) - Check if your firewall allows inbound HTTPS connections
- Ensure DNS is properly configured for the domain
- Verify the server is running and accepting connections on the specified port
”Connection timeout” error
Cause: The server didn’t respond within 10 seconds. Solutions:- Check if the server is under heavy load
- Verify network connectivity to the server
- If your server legitimately needs more time, contact us
”DNS resolution failed”
Cause: We couldn’t resolve the hostname to an IP address. Solutions:- Verify the hostname is spelled correctly
- Check your DNS configuration
- Ensure the domain’s DNS records are publicly accessible
”Connection refused”
Cause: The server actively refused our connection. Solutions:- Verify the port is correct (default is 443)
- Ensure the service is running on that port
- Check firewall rules allow inbound connections
Wrong certificate detected
Cause: A CDN, load balancer, or proxy is serving a different certificate. Note: The certificate we see is exactly what your users see. If this differs from your origin certificate, check your CDN/proxy configuration.Notification Issues
Not receiving alerts
Solutions:- Go to Settings → Channels and verify the channel is enabled
- Click “Test” to send a test notification
- Check the channel’s last error message for details
- Verify alert routing rules include your certificates
Slack notifications not working
Cause: The webhook URL may be invalid or expired. Solutions:- Go to your Slack workspace settings and create a new incoming webhook
- Update the webhook URL in Settings → Channels
- Click “Test” to verify it works
Email notifications going to spam
Solutions:- Add
[email protected]to your email contacts - Mark our emails as “Not spam” in your email client
- Check your organization’s email filtering rules