Skip to content

Commit 18f09f4

Browse files
Added LetsEncrypt not generating new certificate troubleshoot guide - Closes #168
1 parent 29e3095 commit 18f09f4

File tree

5 files changed

+70
-0
lines changed

5 files changed

+70
-0
lines changed

docs/.vitepress/config.mts

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -537,6 +537,7 @@ export default defineConfig({
537537
collapsed: true,
538538
items: [
539539
{ text: 'Wildcard SSL not working', link: '/troubleshoot/dns-and-domains/wildcard-ssl-certs' },
540+
{ text: "Let's Encrypt not working", link: '/troubleshoot/dns-and-domains/lets-encrypt-not-working' },
540541
]
541542
},
542543
],
37.2 KB
Loading
50.5 KB
Loading
63.3 KB
Loading
Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
---
2+
title: Let's Encrypt Not Generating SSL Certificates on Coolify
3+
---
4+
5+
6+
# Let's Encrypt Not Generating SSL Certificates
7+
If you are using the default settings for the Coolify proxy and your website suddenly shows a warning about an insecure connection, it is most likely that your website is using a self-signed certificate from the Coolify proxy. This guide will help you fix the issue.
8+
9+
10+
## 1. Understand the HTTP Challenge
11+
Coolify uses [Let's Encrypt ↗](https://letsencrypt.org?utm_source=coolify.io) under the hood to generate SSL certificates for your websites. By default, Let's Encrypt uses an HTTP challenge to verify domain ownership.
12+
13+
Let's Encrypt sends an HTTP request to your server that includes a unique token embedded in the URL. When your server returns the correct token, it confirms that you control the domain.
14+
15+
16+
## 2. Check Port 80 Accessibility
17+
Make sure your server’s port 80 is open and accessible from the internet. If port 80 is blocked, Let's Encrypt cannot complete the HTTP challenge. Unblocking port 80 should fix this issue.
18+
19+
20+
## 3. Usage of Third-Party Proxy
21+
If you are proxying your website through a third-party service like [Cloudflare ↗](https://www.cloudflare.com?utm_source=coolify.io), Let's Encrypt may not be able to verify your domain. In that case, you must either use a DNS challenge or stop proxying your domain through the third-party service.
22+
23+
24+
## 4. Note on Certificate Validity
25+
Let's Encrypt certificates are valid for 90 days. If the certificate stored on your server is valid, your domain may appear to work fine even if port 80 is closed or your domain is being proxied, because Coolify continues to use that valid certificate till it expires.
26+
27+
28+
## 5. Check Let's Encrypt Service Status
29+
Sometimes, Let's Encrypt might be having issues on their end. Check the Let's Encrypt status from [here ↗](https://letsencrypt.status.io?utm_source=coolify.io). If there is an issue, wait for them to fix it and try again once the issue is fixed.
30+
31+
32+
## 6. Force Regenerate Certificates
33+
If the certificates stored on your server are corrupted or outdated, you can delete them and force Coolify generate new ones.
34+
- Open your server terminal and run:
35+
```bash
36+
rm /data/coolify/proxy/acme.json
37+
```
38+
- Then, restart the Coolify proxy from the dashboard by clicking the Restart Proxy button.
39+
::: details Guide: How to Restart Proxy from Dashboard?
40+
41+
1. Select your server on the Coolify Dashboard
42+
<ZoomableImage src="/docs/images/troubleshoot/dns-and-domains/lets-encrypt-not-working/1.webp" />
43+
44+
2. Click on Restart Proxy button
45+
<ZoomableImage src="/docs/images/troubleshoot/dns-and-domains/lets-encrypt-not-working/2.webp" />
46+
:::
47+
48+
49+
## 7. Check Your WAF Settings
50+
If you are using a Web Application Firewall (WAF), make sure it is not blocking Let's Encrypt requests.
51+
52+
53+
## 8. Check Coolify Proxy logs
54+
On the Coolify proxy logs if you see an error message with a 429 status code, it means that Let's Encrypt has rate-limited your server's IP address.
55+
56+
In this case, wait for a while and check your domain again. Most users won't encounter this, but it can happen if you are using a shared IP address.
57+
::: details Guide: How to check Coolify proxy logs?
58+
59+
1. Select your server on the Coolify Dashboard
60+
<ZoomableImage src="/docs/images/troubleshoot/dns-and-domains/lets-encrypt-not-working/1.webp" />
61+
62+
2. Go to the proxy section and click the refresh button
63+
<ZoomableImage src="/docs/images/troubleshoot/dns-and-domains/lets-encrypt-not-working/3.webp" />
64+
:::
65+
66+
## Support
67+
If none of the above steps work, try these additional options:
68+
- **Community Help:** Join our [Discord community ↗](https://coolify.io/discord) and post in the support forum channel.
69+
- **What to Share:** Include a description of your issue, any error messages, and the steps you have already tried.

0 commit comments

Comments
 (0)