Auto-SSL - Replov Docs
Skip to main content

Automatic SSL Certificates

Free, automatic SSL/TLS certificates for all your services

Replov automatically provisions and renews SSL certificates for all services using Let's Encrypt. Every service gets HTTPS by default with zero configuration required.

Automatic Issuance

Certificates issued within minutes of deployment

Auto-Renewal

Renewed automatically before expiry

TLS 1.2+

Modern encryption standards enforced

How It Works

1

Service Deployment

When you deploy a service, it's automatically assigned a unique URL

https://your-service.Replov.app
2

Certificate Request

Replov automatically requests a certificate from Let's Encrypt

3

Domain Validation

Let's Encrypt validates domain ownership via HTTP-01 challenge

4

Certificate Installation

Certificate is installed and your service is accessible via HTTPS

5

Automatic Renewal

Certificate renewed automatically 30 days before expiry

Zero Configuration
You don't need to do anything! SSL certificates are automatically managed for all default Replov URLs.

Custom Domain SSL

When you add a custom domain, SSL certificates are automatically provisioned for it too:

Step 1: Add Custom Domain

Navigate to your service settings:

text
Dashboard → Your Service → Settings → Domains → Add Custom Domain

Step 2: Configure DNS

Add CNAME record at your domain registrar:

TypeNameValue
CNAMEwwwyour-service.Replov.app

Step 3: Verify Domain

Click "Verify Domain" in the dashboard. Once DNS propagates, the SSL certificate is automatically issued.

✓ Certificate Status: Active
Issued by Let's Encrypt • Valid until Dec 20, 2024
DNS Propagation
DNS changes can take 1-48 hours to propagate. Certificate issuance begins once DNS is verified.

Certificate Details

Certificate Authority

  • • Issuer: Let's Encrypt
  • • Type: Domain Validated (DV)
  • • Validity: 90 days
  • • Renewal: 30 days before expiry

Encryption Standards

  • • Protocol: TLS 1.2, TLS 1.3
  • • Key Size: RSA 2048-bit
  • • Cipher Suites: Modern, secure
  • • HSTS: Enabled by default

Wildcard Certificates

Wildcard certificates (*.yourdomain.com) are supported for custom domains:

bash
# Add wildcard domain via API
curl -X POST https://api.Replov.com/api/services/SERVICE_ID/domains \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"domain": "*.yourdomain.com",
"wildcard": true
}'

Wildcard Certificate Benefits

  • • Secure unlimited subdomains with one certificate
  • • Ideal for multi-tenant applications
  • • Automatic SSL for dynamically created subdomains
  • • Simplified certificate management
DNS Validation Required
Wildcard certificates require DNS-01 validation. You'll need to add a TXT record to verify domain ownership.

HTTP to HTTPS Redirect

All HTTP traffic is automatically redirected to HTTPS:

bash
# HTTP request
curl -I http://your-service.Replov.app
# Response
HTTP/1.1 301 Moved Permanently
Location: https://your-service.Replov.app
Strict-Transport-Security: max-age=31536000

HSTS (HTTP Strict Transport Security)

HSTS is automatically enabled, instructing browsers to only use HTTPS for your domain.

text
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

This header tells browsers to always use HTTPS for 1 year, including all subdomains.

Certificate Monitoring

Monitor your SSL certificates in the dashboard or via API:

bash
# Get certificate status
curl -H "Authorization: Bearer YOUR_API_KEY" \
https://api.Replov.com/api/services/SERVICE_ID/ssl
# Response
{
"certificates": [
{
"domain": "your-service.Replov.app",
"status": "active",
"issuer": "Let's Encrypt",
"issued_at": "2024-09-20T10:00:00Z",
"expires_at": "2024-12-20T10:00:00Z",
"days_until_expiry": 45,
"auto_renew": true
},
{
"domain": "www.yourdomain.com",
"status": "active",
"issuer": "Let's Encrypt",
"issued_at": "2024-10-01T14:30:00Z",
"expires_at": "2024-12-30T14:30:00Z",
"days_until_expiry": 55,
"auto_renew": true
}
]
}

Certificate Alerts

  • • 30 days: Renewal scheduled notification
  • • 7 days: Renewal in progress notification
  • • Renewed: Success confirmation
  • • Failed: Manual intervention required (rare)

Security Best Practices

1. Always Use HTTPS

Never serve sensitive data over HTTP. Replov enforces HTTPS by default.

javascript
// Ensure HTTPS in your application
app.use((req, res, next) => {
if (req.header('x-forwarded-proto') !== 'https') {
res.redirect(`https://${req.header('host')}${req.url}`);
} else {
next();
}
});

2. Use Secure Cookies

Set the Secure flag on cookies to ensure they're only sent over HTTPS.

javascript
// Set secure cookies
res.cookie('session', sessionId, {
secure: true, // Only send over HTTPS
httpOnly: true, // Not accessible via JavaScript
sameSite: 'strict', // CSRF protection
maxAge: 3600000 // 1 hour
});

3. Implement CSP Headers

Use Content Security Policy to prevent XSS attacks.

javascript
// Add CSP headers
app.use((req, res, next) => {
res.setHeader(
'Content-Security-Policy',
"default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';"
);
next();
});

4. Monitor Certificate Expiry

While auto-renewal is reliable, set up monitoring alerts as a backup. Check certificate status regularly.

Troubleshooting

Certificate Not Issued

Possible causes:

  • • DNS not properly configured
  • • DNS not yet propagated (wait 1-2 hours)
  • • Domain validation failed
  • • Rate limit reached (5 certs/week per domain)

Solution: Verify DNS settings, wait for propagation, then click "Retry" in dashboard.

Certificate Expired

This is extremely rare as auto-renewal happens 30 days before expiry.

Solution: Contact support immediately. Manual renewal will be triggered.

Mixed Content Warnings

Symptom: Browser shows "Not Secure" despite having SSL

Cause: Loading HTTP resources (images, scripts) on HTTPS page

Solution: Ensure all resources use HTTPS or protocol-relative URLs (//example.com/image.jpg)

SSL Handshake Errors

Symptom: "SSL handshake failed" errors

Solution: Check that your application supports TLS 1.2+. Update SSL libraries if needed.

Custom Certificates (Enterprise)

Enterprise customers can upload their own SSL certificates:

bash
# Upload custom certificate
curl -X POST https://api.Replov.com/api/services/SERVICE_ID/ssl/custom \
-H "Authorization: Bearer YOUR_API_KEY" \
-F "certificate=@certificate.crt" \
-F "private_key=@private.key" \
-F "ca_bundle=@ca_bundle.crt"

Custom Certificate Requirements

  • • Valid X.509 certificate in PEM format
  • • Private key must be unencrypted
  • • Certificate must match the domain
  • • Include full certificate chain (CA bundle)
  • • Minimum 2048-bit RSA or 256-bit ECC
Manual Renewal Required
Custom certificates are not auto-renewed. You're responsible for renewing and re-uploading before expiry.

Next Steps