Let's Encrypt SSL

​

When to use Let’s Encrypt

• You have a custom domain (cdn.yoursite.com) on a Tenbyte CDN distribution.
• Domain Validation (DV) is sufficient — no green-bar EV / OV needed.
• You want zero-touch renewal.

​

How it works

​

Prerequisites

• Custom domain configured on the distribution. See SSL settings.
• A DNS CNAME from your domain to the distribution hostname:
  cdn.yoursite.com.   300   IN   CNAME   your-distribution.tenbytecdn.com.
  
• DNS resolves publicly — Let’s Encrypt verifies from the public internet.

dig +short cdn.yoursite.com CNAME
# cdn.yoursite.com.   CNAME   your-distribution.tenbytecdn.com.

​

Issue the certificate

1. Open the distribution → SSL tab.
2. Choose Let’s Encrypt.
3. Click Issue certificate.
4. Status moves through: Pending validation → Issuing → Active.

​

Verify

openssl s_client -connect cdn.yoursite.com:443 -servername cdn.yoursite.com </dev/null \
  2>/dev/null | openssl x509 -noout -subject -issuer -dates

subject=CN = cdn.yoursite.com
issuer=C = US, O = Let's Encrypt, CN = R3
notBefore=May  9 00:00:00 2026 GMT
notAfter=Aug  7 23:59:59 2026 GMT

​

Renewal

​

Limitations

• DV only. No organizational identity in the cert.
• No wildcards by default. Use a custom cert if you need *.yoursite.com.
• Public DNS only. Internal-only domains can’t validate; use a custom cert from your internal CA.
• Rate limits. Let’s Encrypt limits per registered domain (50 certs / week / domain). Plenty for production but worth knowing for spin-up scripts.

​

Troubleshooting

​

Related

• SSL Overview — pick the right cert type.
• SSL settings — toggle HTTPS redirect, HTTP/2, HTTP/3.
• Custom certificates — bring your own.