Updated November 2026
Setting up HTTPS with Coolify
Coolify’s proxy (Traefik, in the usual install) can request a free Let’s Encrypt certificate for you. Almost every failure is DNS, port 80, or a hostname typo — not “HTTPS is hard.”
What you need first
- A VPS with Coolify installed, public IPv4, and ports 80 and 443 open to the internet. A Hostinger KVM VPS works for this because you control the firewall and those ports; any comparable KVM box does too.
- A domain you control. Coolify will not issue a trusted cert for a random IP address.
- An A record for the exact hostname you will type in Coolify (for example
app.example.com) pointing at the VPS. If an AAAA record exists, it must also point at this server.
Wait until the name resolves publicly. Let’s Encrypt checks from their servers, not from your laptop.
The happy path
- In Coolify, open the resource (or the application) and set the domain to the hostname you created, including
https://. - Make sure the app is running and bound to the proxy network Coolify expects. A default Coolify install already has this.
- Deploy or restart only that resource if Coolify asks you to. You should not need to restart the whole server or unrelated apps.
- Visit
http://your-hostnamefirst if HTTPS is not ready yet. The HTTP-01 challenge uses port 80. Once the cert is issued, the site should redirect to HTTPS and the browser padlock should be clean.
On many setups the certificate appears within a minute or two of DNS being correct. If it does not, fix the checklist below rather than clicking “renew” in a loop.
When the certificate does not issue
| Symptom | Usual cause |
|---|---|
| ACME timeout or “connection refused” | Port 80 is closed in the cloud firewall, ufw, or another process is bound to it |
| “No valid A record” / wrong site | The hostname is not pointing at this VPS, or you typed www in one place and the apex in another |
| Works on IPv4, fails for some visitors | A stale or wrong AAAA record |
| Certificate for the wrong name | The Coolify domain field does not match the DNS name exactly |
| Other apps broke after a change | Someone edited the shared proxy config or restarted the proxy stack. Change only the new host’s config. |
Do not stop or restart existing applications to “make HTTPS work.” The proxy can request a cert for a new hostname without taking other sites down.
HTTP-01 in one sentence
Let’s Encrypt connects to your hostname on port 80 and expects the Coolify proxy to answer a /.well-known/acme-challenge/… URL. If that request never arrives, there will be no certificate. After it succeeds once, renewals use the same path, so leave port 80 open.
If you are still choosing a server, pick one with root access and unfiltered 80/443, then follow the Coolify VPS sizing notes so the proxy and your apps have enough RAM to stay up.