SSL Certificates
Automatic HTTPS encryption for all your domains with zero configuration.
Overview
SailOps provides free, automatic SSL certificates for all your domains:
- Automatic provisioning - Certificates issued within minutes
- Auto-renewal - Renewed automatically before expiration
- Industry standard - Let's Encrypt certificates trusted by all browsers
- Zero configuration - Works out of the box
How It Works
When you create an HTTPS listener on a gateway:
- Configure your DNS to point to the gateway IP
- Create an HTTPS listener with your domain
- SailOps automatically provisions and installs the certificate
- Your domain is secured with HTTPS
Certificates are renewed automatically before expiration.
Configure DNS → Add HTTPS listener → Certificate provisioned → HTTPS active
Automatic Certificates
Adding an HTTPS Listener
When you add an HTTPS listener to your gateway:
- Configure DNS - Point your domain to the gateway IP (A record)
- Create the listener - Select HTTPS protocol and enter your hostname
- Wait for provisioning - Certificate is issued automatically (1-5 minutes)
- HTTPS is active - Your domain is now accessible via HTTPS
Certificate Status
View certificate status in your gateway's Listeners section:
| Status | Description |
|---|---|
| Pending | Awaiting domain verification |
| Provisioning | Certificate being issued |
| Active | Certificate is valid and in use |
| Renewing | Auto-renewal in progress |
| Failed | Provisioning failed |
TLS Configuration
TLS Termination
SailOps gateways terminate TLS at the edge, meaning:
- Encrypted traffic from clients to the gateway
- Internal traffic to containers can be HTTP or HTTPS
- Certificates are managed at the gateway level
TLS Versions and Ciphers
SailOps uses secure defaults:
| Version | Status |
|---|---|
| TLS 1.3 | Enabled (preferred) |
| TLS 1.2 | Enabled |
| TLS 1.1 | Disabled |
| TLS 1.0 | Disabled |
Modern cipher suites are enabled automatically for optimal security.
SSL Labs Rating
SailOps gateways achieve an A+ rating on SSL Labs:
- Modern TLS versions only
- Strong cipher suites
- Perfect forward secrecy
- OCSP stapling enabled
Test your domain: SSL Labs Test
Certificate Renewal
Automatic Renewal
Certificates are renewed automatically:
- Renewal starts before expiration
- No downtime during renewal
- No action required from you
Renewal Notifications
You'll be notified if:
- Renewal fails
- Manual action required (e.g., DNS issue)
- Certificate is about to expire
Requirements
Domain Verification
For certificates to be provisioned successfully:
- DNS must be configured - A record pointing to your gateway IP
- Port 80 must be accessible - Required for automatic domain verification
- No CAA restrictions - Or Let's Encrypt must be allowed
Wildcard certificates are supported when a DNS provider is configured in your project settings. Wildcard certificates require DNS-01 challenge validation, which is handled automatically through your configured DNS provider. Without a DNS provider, only individual domain certificates are available via HTTP-01 challenge.
Troubleshooting
Certificate Not Provisioning
Domain not verified:
- Check DNS configuration points to your gateway IP
- Wait for DNS propagation (up to 10 minutes)
- Verify with
digcommand:
dig app.example.com A
Port 80 blocked:
- Ensure HTTP traffic can reach your gateway
- Check firewall rules allow port 80
- Automatic verification requires port 80 access
Rate limit exceeded:
- Let's Encrypt has rate limits
- Wait 1 hour and retry
- Contact support for urgent needs
CAA record blocking:
- Check for CAA DNS records that might block Let's Encrypt
- Add Let's Encrypt to allowed issuers:
CAA 0 issue "letsencrypt.org"
Certificate Errors in Browser
NET::ERR_CERT_COMMON_NAME_INVALID:
- Domain mismatch between certificate and URL
- Check the exact domain is configured in your listener
- Include both
example.comandwww.example.comif needed
NET::ERR_CERT_DATE_INVALID:
- Certificate may have expired
- Check the Events tab for renewal issues
- Verify system clock is correct
NET::ERR_CERT_AUTHORITY_INVALID:
- Incomplete certificate chain
- Clear browser cache
- Try a different browser to confirm
Mixed Content Warnings
Your site loads some resources over HTTP:
- Update all URLs in your application to HTTPS
- Use relative URLs or protocol-relative URLs
- Check for hardcoded HTTP URLs in your code
Certificate Verification Failed
If automatic verification fails:
- Verify domain is reachable from the internet
- Check no firewall is blocking port 80
- Ensure the gateway is running and healthy
- Check the Events tab for specific error messages
Security Best Practices
Use HTTPS Listeners
Always create HTTPS listeners for production:
- All traffic is encrypted
- Certificates are managed automatically
- No additional configuration needed
Multiple Domains
For applications with multiple domains:
- Create a separate listener for each domain
- Each domain gets its own certificate
- All certificates are managed automatically
Monitor Certificate Events
Check the Events tab regularly for:
- Certificate provisioning issues
- Renewal failures
- Validation errors