Automatic HTTPS, Zero effort
Webdock issues and renews your SSL/TLS certificates automatically via Let’s Encrypt and ACME. Certbot is preinstalled on our standard stacks, so your domains are secured without scripts or support tickets.
Free SSL Certificates
HTTPS security on every site. Included with Webdock
Get free SSL on your websites. No manual certificates. No extra fees. Just security and better SEO.
If you are paying for certificates today, it is time to switch.
Why it matters
-
Encrypted traffic. Protect logins, forms, API calls and checkout.
-
Better SEO. Google prefers secure sites.
-
Trust. The padlock improves conversions and credibility.
-
Low maintenance. Auto renewals every 60-90 days by default.
-
Full control. One place to manage everything in the Webdock Control Panel.
How it works
-
Point your domain to your server.
-
Test the domain in Server Identity to confirm DNS.
-
Enable Free SSL. We issue the certificate automatically.
-
We keep it renewed. You do not need to do anything.
Free vs paid SSL – What is the difference
-
Encryption. Same modern TLS encryption.
-
Validation. Let’s Encrypt is DV. Paid certificates can be OV or EV.
-
Validity. Let’s Encrypt renews automatically about every 90 days. Paid certs can have longer terms.
-
Warranty and site seal. Typically only with paid certificates.
For most websites, Free SSL via Let’s Encrypt is the right choice. If you need EV or audit-specific compliance, bring your own certificate and use it on Webdock.
Included with every Webdock server
Create a server. Point your domain. Enable Free SSL in the Webdock Control Panel. That is it.
ACME automation with Certbot
NGINX SSL configuration included
Auto renewals via systemd timer
HTTP to HTTPS redirection built in
Works with both LEMP and LAMP
No. It is included.
No. We renew automatically. You can run a manual renewal any time.
Yes. Add both in your server block and let Certbot issue for both.
Yes. Upload your files and point your config to them.
TLS is fast on modern hardware and often faster than http due to HTTP/2.
