Skip to content

Commit 2861ee8

Browse files
Added Coolify not using Wildcard SSL Certificates troubleshoot guide - Closes #165
1 parent e969dfe commit 2861ee8

File tree

2 files changed

+52
-0
lines changed

2 files changed

+52
-0
lines changed

docs/.vitepress/config.mts

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -532,6 +532,13 @@ export default defineConfig({
532532
{ text: 'Crash During Build ', link: '/troubleshoot/server/crash-during-build' },
533533
]
534534
},
535+
{
536+
text: 'DNS & Domains',
537+
collapsed: true,
538+
items: [
539+
{ text: 'Wildcard SSL not working', link: '/troubleshoot/dns-and-domains/wildcard-ssl-certs' },
540+
]
541+
},
535542
],
536543
},
537544
{
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
title: Coolify not using Wildcard SSL Certificates
3+
---
4+
5+
# Coolify not using Wildcard SSL Certificates
6+
If your wildcard SSL certificate isn't working with your domain, it may be due to configuration problems. Here's how you can check and fix it.
7+
8+
9+
## 1. Check the SSL Certificate Validity
10+
- **Verify the Certificate:** Make sure the SSL certificate is valid for the domain.
11+
- Confirm the Common Name (CN) matches your domain.
12+
- Double-check that your wildcard certificate is not expired.
13+
14+
15+
## 2. Verify Certificate Installation
16+
- **File Extensions:** Make sure the SSL certificate file ends with `.cert` and the key file ends with `.key`.
17+
- Some providers give files in `.pem` format, which must be converted to `.cert` and `.key` before adding them to your server (simply rename the files to `.cert` for the certificate and `.key` for the key)
18+
- **File Location:** Make sure your `.cert` and `.key` files are located in the `/data/coolify/proxy/certs` directory.
19+
20+
21+
## 3. Check the Coolify Proxy Configuration
22+
- **Add Certificate in Dashboard:** Make sure you have added the SSL certificate configuration in the Coolify proxy via the dashboard. More details can be found [here](/knowledge-base/proxy/traefik/custom-ssl-certs).
23+
- **Check File Mounts:** If you have modified the proxy configuration, verify that the `/data/coolify/proxy` directory is mounted correctly.
24+
25+
26+
## 4. Remove Old Certificates
27+
- **Old Certificate Issue:** The Coolify proxy may be using an old certificate stored in the `acme.json` file.
28+
- **Action:** Delete the `acme.json` file from the `/data/coolify/proxy` directory and restart the Coolify proxy from the dashboard by clicking the restart proxy button.
29+
30+
31+
## 5. Clear Your Browser Cache
32+
- **Cache Issue:** Your browser might be caching an old SSL certificate.
33+
- **Action:** Check your website using a different browser or network.
34+
- You can also use sandbox tools like [Browserling ↗](https://www.browserling.com?utm_source=coolify.io) to test your site.
35+
36+
37+
## 6. Verify DNS Challenge Configuration
38+
- **DNS Challenge Check:** If you are using a DNS challenge, confirm that it is set up correctly.
39+
- **Action:** Verify that you have selected the correct DNS provider, API Keys and check the challenge settings are properly configured.
40+
41+
42+
## Support
43+
If none of the above steps work, try these additional options:
44+
- **Community Help:** Join our [Discord community ↗](https://coolify.io/discord) and post in the support forum channel.
45+
- **What to Share:** Include a description of your issue, screenshots of your configuration, any error messages, and the steps you have already tried.

0 commit comments

Comments
 (0)