Prerequisites
Your custom domain must point to Bunny using a CNAME record before SSL validation can succeed. See Custom Hostname for setup instructions.Free Let’s Encrypt certificate
1
Add your custom hostname
Open your Pull Zone in the dashboard, navigate to General > Hostnames, and add your custom hostname if you haven’t already.
2
Enable SSL
Find your hostname in the Linked Hostnames section and click Enable.

3
Select free certificate
Choose Add Free Let’s Encrypt Certificate and click Continue.
Bunny issues and installs the certificate automatically. Renewal is handled for you.

4
Confirm CNAME configuration
Verify your CNAME record is correctly configured and click Continue to complete validation.

5
Verify it's working
Visit your domain using
https:// and confirm the certificate is valid. You can also use SSL Labs to test.Custom certificate
Use this option for wildcard domains (*.yourdomain.com) or certificates from commercial providers.
1
Prepare your certificate files
Bunny requires Nginx-compatible format. Combine your certificate chain into a single file by placing your domain certificate at the top, followed by intermediate certificates in order. Save as a single
.pem file (e.g., fullchain.pem). You’ll also need your private key file.2
Enable SSL
Open your Pull Zone, go to Hostnames, find your hostname, and click Enable.
3
Select custom certificate
Choose Upload your own certificate and click Continue.

4
Upload the certificate
Paste your certificate chain and private key into the respective fields, then click Upload.
Wait for the certificate to propagate across the network.

Let’s Encrypt wildcard certificates are not supported through Bunny’s
automatic issuance. For wildcards, generate the certificate yourself (e.g.,
using certbot with DNS validation) and upload it manually.
Troubleshooting
SSL validation fails
Common causes:- DNS not propagated: Use dnschecker.org to confirm your CNAME is resolving globally
- Cloudflare proxy enabled: Disable the orange cloud icon on your CNAME record
- Geolocation blocks: Let’s Encrypt validates from multiple regions (including USA and Europe). If you’ve blocked these regions via Traffic Manager or Edge Rules, validation will fail
- CAA records: If your domain has CAA DNS records, add
letsencrypt.orgto the allowed issuers
Rate limiting
Requesting certificates too many times in a short period can trigger Let’s Encrypt rate limits (up to one week). Be patient when troubleshooting DNS issues before retrying.Root domains
CNAME records aren’t allowed at the apex level (yourdomain.com) by most DNS providers. You have two options:
- Use a subdomain like
www.yourdomain.comwith a CNAME, then redirect the apex to it - Use Bunny DNS with CDN Acceleration, which handles this automatically