blog.dopana

Back

Let’s Encrypt has become the standard for free SSL certificates, but sometimes you need alternatives. Maybe you want to reduce management overhead, need longer certificate validity, or are looking for better integration with your existing infrastructure.

Why Consider Let’s Encrypt Alternatives?#

Let’s Encrypt is great but has some limitations:

  • Short validity: Only 90 days, requires frequent renewal
  • No web interface: Must use command line
  • Rate limiting: Limited number of certificates
  • No OV/EV support: Only Domain Validation (DV)

[!TIP] If you’re experiencing issues with Let’s Encrypt or want to explore other options, here are the best alternatives available today.

1. Cloudflare SSL (Best Proxy/CDN Solution)#

If you point your DNS to Cloudflare, they provide free SSL certificates without manual renewal on your server.

Universal SSL#

  • Automatically activated for every domain proxied through Cloudflare
  • No installation required on your hosting
  • Publicly trusted certificates accepted by browsers immediately

Origin CA Certificate#

  • Cloudflare issues certificates installed directly on your server
  • Valid for up to 15 years
  • Encrypts data from Server to Cloudflare
  • No expiration worries every 3 months like Let’s Encrypt
graph LR
    A[Browser] --> B[Cloudflare Edge]
    B --> C[Origin Server]
    B -.->|Universal SSL| A
    C -.->|Origin CA| B
    style B fill:#f9f,stroke:#333,stroke-width:2px

[!WARNING] Origin CA is only trusted by Cloudflare, not publicly trusted. Browsers will show errors if accessing the server directly bypassing Cloudflare.

When to Use Cloudflare SSL?#

  • Website runs through Cloudflare proxy
  • Want to minimize SSL management effort
  • Need additional CDN, DDoS protection benefits
  • Don’t want to configure certbot on server

2. ZeroSSL (Direct ACME Competitor)#

ZeroSSL is Let’s Encrypt’s biggest competitor, also using ACME protocol for automation.

Advantages#

  • Free: 90 days, up to 3 certificates via web interface
  • Unlimited: If configured with ACME automation
  • Intuitive web interface: Easier to use than command line
  • Full ACME port support: HTTP-01, DNS-01, TLS-ALPN-01

Limitations#

  • Wildcard SSL only in paid plans
  • Stricter rate limits in free tier
# Configure ZeroSSL with Certbot
certbot certonly --authenticator dns-zero_ssl \
  --dns-zero_ssl-credentials ~/.secrets/zero_ssl.ini \
  -d example.com -d *.example.com
bash

When to Use ZeroSSL?#

  • Want user-friendly web management interface
  • Need wildcard SSL (paid plan)
  • Already familiar with ACME but want better UI

3. SSL For Free (Now Part of ZeroSSL)#

Previously a tool for creating Let’s Encrypt certificates manually via web. Now integrated into ZeroSSL.

  • Still usable for creating free 90-day SSL certificates
  • No command line needed
  • Backend system is ZeroSSL

When to Use SSL For Free?#

  • Need SSL quickly without ACME configuration
  • Only need 1-2 simple certificates
  • Want simple manual process

4. Buypass Go SSL (European ACME Alternative)#

Reputable Certificate Authority (CA) from Norway.

Key Advantages#

  • 180-day validity: Double Let’s Encrypt/ZeroSSL
  • ACME compatible: Easy migration from Let’s Encrypt
  • Publicly trusted: All browsers accept
  • Free wildcard: Via ACME v2

Limitations#

  • Only supports single domain (no multi-domain SAN)
  • Requires Buypass account
  • No web interface
# Migrate from Let's Encrypt to Buypass
# Just change server URL
# From: https://acme-v02.api.letsencrypt.org/directory
# To: https://api.buypass.com/acme/directory
bash

When to Use Buypass?#

  • Want longer certificate validity (180 days)
  • Need free wildcard SSL
  • Located in Europe, want local CA
  • Already have ACME infrastructure

5. SSL from Cloud Providers#

If you run infrastructure on cloud platforms, they have integrated free SSL.

AWS Certificate Manager (ACM)#

  • Free for Load Balancer (ALB) and CloudFront
  • Automatic perpetual renewal
  • Public certificates for Elastic Load Balancing
  • Private certificates for internal applications

Google Managed SSL#

  • Free for App Engine, GKE, Cloud Run
  • Automatic lifecycle management
  • Integrated with Google Cloud Load Balancing

Azure Key Vault#

  • Managed SSL certificates
  • Integrated with Application Gateway
  • Auto-renewal
graph TD
    A[Cloud Provider] --> B[AWS ACM]
    A --> C[Google Managed SSL]
    A --> D[Azure Key Vault]
    B --> E[ALB/CloudFront]
    C --> F[App Engine/GKE]
    D --> G[Application Gateway]
    style A fill:#e1f5fe,stroke:#01579b,stroke-width:2px

When to Use Cloud Provider SSL?#

  • Infrastructure on corresponding cloud platform
  • Want deep integration with cloud services
  • Need managed service without maintenance
  • Large scale, many applications

Detailed Comparison Table#

CriteriaLet’s EncryptCloudflare SSLZeroSSLBuypass
Validity90 daysPerpetual / 15 years (Origin)90 days180 days
OperationDirect Server InstallProxy CDNServer or Web UIDirect Server Install
Web InterfaceNo (CLI only)Very intuitiveHas dashboardNo (CLI only)
Wildcard SSLYes (DNS-01)Yes (free)Paid plans onlyYes (ACME v2)
Multi-domainYes (SAN)YesYes (paid)No
ACME SupportYesNo (Origin CA)YesYes
Public TrustYesYes (Universal)YesYes
Rate Limit50/weekUnlimited3 freeUnclear

Migration Guide from Let’s Encrypt#

Migrating to Cloudflare SSL#

  1. Point DNS to Cloudflare
# Update nameservers
nslookup -type=NS example.com
bash
  1. Enable Universal SSL
  • Go to Cloudflare Dashboard > SSL/TLS
  • Select “Full” or “Full (strict)” mode
  • Universal SSL activates automatically
  1. Install Origin CA (if needed)
# Download Origin CA certificate from Cloudflare
# Install on server
sudo cp origin.pem /etc/ssl/certs/
sudo cp origin.key /etc/ssl/private/
# Configure Nginx/Apache to use this certificate
bash

Migrating to ZeroSSL#

  1. Create ZeroSSL Account
  • Sign up at zerossl.com
  • Get API key
  1. Configure Certbot
# Install ZeroSSL plugin
sudo apt install python3-certbot-dns-zero-ssl

# Create credentials file
echo "dns_zero_ssl_api_token = YOUR_API_TOKEN" > ~/.secrets/zero_ssl.ini
chmod 600 ~/.secrets/zero_ssl.ini

# Request certificate
certbot certonly --authenticator dns-zero_ssl \
  --dns-zero_ssl-credentials ~/.secrets/zero_ssl.ini \
  -d example.com -d *.example.com
bash

Migrating to Buypass#

  1. Create Buypass Account
  • Sign up at buypass.com
  • Get EAB credentials
  1. Configure ACME client
# With Certbot
certbot register --account-key ~/.secrets/buypass.key \
  --email your@email.com \
  --server https://api.buypass.com/acme/directory

# Request certificate
certbot certonly --server https://api.buypass.com/acme/directory \
  -d example.com
bash

Frequently Asked Questions#

Which solution should I choose?#

Choose Cloudflare SSL if:

  • Website runs through Cloudflare
  • Want “set and forget” solution
  • Need additional CDN/DDoS protection

Choose ZeroSSL if:

  • Want user-friendly web interface
  • Need wildcard SSL (paid plan)
  • Already familiar with ACME

Choose Buypass if:

  • Want 180-day validity
  • Need free wildcard
  • Located in Europe

Choose Cloud Provider SSL if:

  • Infrastructure on AWS/GCP/Azure
  • Want managed service
  • Large scale

Is Origin CA safe?#

Origin CA is safe when:

  • All traffic goes through Cloudflare proxy
  • Using “Full (strict)” SSL mode
  • Never access origin server directly

Not safe when:

  • Direct traffic to origin exists
  • Cloudflare experiences downtime
  • Need publicly trusted certificate

Can I combine multiple solutions?#

Yes! For example:

  • Cloudflare Universal SSL for public traffic
  • Origin CA for Cloudflare → Origin
  • Let’s Encrypt for direct access routes

Conclusion#

Let’s Encrypt remains an excellent choice for many use cases, but it’s not the only solution. Depending on your specific needs:

  • Least effort: Cloudflare SSL
  • Independent, no proxy: ZeroSSL or Buypass
  • Cloud native: AWS ACM, Google Managed SSL
  • Quick, manual: SSL For Free

Key takeaway: Choose the solution that fits your architecture and workflow, not necessarily the “popular choice.”

References#