coolify: [Bug]: Ghost one-click deploy `SSL_PROTOCOL_ERROR` with Caddy
Error Message and Logs
Am currently at v4.0.0-beta.370. Instead of a 404, I’m getting a (failed) net::ERR_SSL_PROTOCOL_ERROR when using Ghost one-click deploy.
Note: I’m using Caddy instead of Traefik`.
I verified SERVICE_FQDN_GHOST_2368 points to my domain at https://blog.scottsus.dev, and url points to $SERVICE_FQDN_GHOST_2368. Both Ghost and Mysql running and healthy.
Any suggestions?
Steps to Reproduce
- New resource
- Production
- Ghost
- Change service name to ghost-cms
- Services -> settings -> https://blog.scottsus.dev:2368
- Verify
SERVICE_FQDN_GHOST_2368->https://blog.scottsus.dev - Browser visit
https://blog.scottsus.dev (failed) net::ERR_SSL_PROTOCOL_ERROR.
Example Repository URL
No response
Coolify Version
v4.0.0-beta.370
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 24.04.1 LTS
Additional Information
No response
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 18 (2 by maintainers)
Ok that issue is now fixed and I was able to deploy and also get an SSL error.
Ghost docker logs look normal, proxy logs don’t.
Proxy logs:
@subflow
I can see you have the same issue I had. Feel free to check my last solution: https://github.com/coollabsio/coolify/issues/4809#issuecomment-2605858583
Feel free to let me know if this worked. I already did that a few times and besides that, I may found some issues and hope Coolify devs will look at it and try to check, clarify some stuff, and maybe fi itx.
This is maybe another issue, but i did what @olamide-olaniyan suggested and ot works to reach the site. I have tried several times to do fresh install of ghost but i get this error:
Anyone else having this issue?
Here is how I solved this.
Then click on localhost or wherever Coolify runs.
The click on Proxy, the click on Dynamic Configurations
Then click on Add, and it will show a popup that looks like this. Add a new caddy file called “anything.caddy”, I called mine blog.caddy The in the content, add the code below, as seen in the screenshot below, don’t forget to update your blog url
I got the exact same proxy logs (here’s a prettified version).