SSL Certificates
Configure HTTPS with self-signed or Let's Encrypt certificates
Astervis uses HTTPS by default. Choose between self-signed certificates (quick setup) or Let's Encrypt (production).
Certificate Types
| Type | Best For | Requirements |
|---|---|---|
| Self-Signed | Testing, internal use | None |
| Let's Encrypt | Production | Domain name, DNS access |
| Custom | Enterprise | Your own certificate files |
Self-Signed (Default)
Generated automatically during installation. Works immediately but shows browser warning.
Regenerate Certificate
Certificate Location
Browser Warning
Users will see "Your connection is not private" warning. Click Advanced → Proceed to continue.
Self-signed certificates are secure for encryption. The warning only means the certificate isn't verified by a Certificate Authority.
Let's Encrypt
Free, trusted certificates. Requires a domain name pointing to your server.
Prerequisites
- Domain name (e.g.,
pbx.company.com) - DNS A record pointing to your server IP
- Port 80 accessible (for verification)
DNS Challenge with DNSimple
If port 80 is blocked, use DNS challenge:
1. Get DNSimple API Token
Go to dnsimple.com → Account → API Tokens → Generate
2. Configure Astervis
Add:
3. Request Certificate
HTTP Challenge
If port 80 is open:
Certificate Renewal
Let's Encrypt certificates expire every 90 days. Astervis auto-renews every 60 days.
Check renewal status:
Manual renewal:
Custom Certificate
Use your own certificate files.
Copy Certificate Files
Set Permissions
Restart Nginx
Verify Certificate
Check Certificate Info
Check Expiration
Test HTTPS
Troubleshooting
Certificate Not Trusted
Cause: Self-signed certificate or Let's Encrypt not properly configured.
For self-signed: Expected behavior. Users must accept the warning.
For Let's Encrypt: Check DNS records point to correct IP:
Port 80 Blocked
Solution: Use DNS challenge instead of HTTP challenge:
Certificate Renewal Failed
Check logs:
Common causes:
- DNS records changed
- API token expired
- Port 80 blocked (for HTTP challenge)
Mixed Content Warning
Cause: HTTP resources loaded on HTTPS page.
Solution: Ensure all URLs use HTTPS. Check BETTER_AUTH_URL in .env: