[Bug]: Instance Domain Is Not Using LetsEncrypt Certificate Using A Self Signed Certificate Instead

[DanyaalMajid]

Error Message and Logs

After setting up a custom domain for the Coolify v4 dashboard, the interface is accessible through the configured domain but is using a self-signed certificate instead of a proper Let's Encrypt certificate. This causes browser security warnings when accessing the dashboard.

Environment:
Installation method: One-click installer
No external reverse proxy/nginx
Direct domain configuration in Coolify settings

Current Behavior:
Dashboard is accessible via configured domain
Browser shows security warning due to self-signed certificate
SSL is not properly configured with Let's Encrypt

Expected Behavior:
Dashboard should be accessible via configured domain
Should use valid Let's Encrypt SSL certificate
No browser security warnings

Steps to Reproduce

1. Install Coolify v4 using one-click installer
2. Configure DNS A record pointing to server IP
3. Set custom domain in Coolify dashboard settings
4. Access dashboard via configured domain
5. Observe browser security warning due to self-signed certificate

Example Repository URL

No response

Coolify Version

v4.0.0-beta.394

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.10

Additional Information

No response

[Cinzya]

Hey there,

check your proxy logs for potential errors, sometimes they can give you a hint why it failed generating the certificate. You can find them under Servers > localhost > Proxy > Logs.

Here are a few steps you can try to resolve the issue:

1. Make sure port 80 and 443 are open in your firewall (both in- and outbound)
2. Restart your proxy under Servers > localhost > Proxy
3. If the LetsEncrypt certificate was still not generated run rm /data/coolify/proxy/acme.json. WARNING: This will remove all current LetsEncrypt certificates from the proxy, but forces the proxy to attempt generating them again.
4. Restart the proxy as mentioned above