Deploying on Coolify?

[pfriedl]

Hey all, I've tried to deploy Fizzy on Coolify, but it continues to fail. Is there any SOP or guide for using it on a system like Coolify?

[monorkin]

Hi @pfriedl I haven't used Coolify before so I'm not familiar with how it work.
Can you tell me if you are running into an error of some kind? I assume it deploys our Docker container?

[SamuelAierizer]

@pfriedl - I was just thinking the same thing! 🙂 Before we make it a deploy with one click we could just create a docker compose that handles everything. From reading the issues I think here (#1801) it was also discussed to have a Prebuilt Docker Image so if we are able to pull it from a public registry then we could set this up to be a very easy deploy. I want to take a look at it when I have some time but if someone does it faster, then thank you in advance!

[pfriedl]

Here's what I'm trying to do with Coolify - which is just a glorified docker manager with a pretty UI You create a project and add a resource, and I'm selecting the GIT repo: <img width="856" height="436" alt="01" src="https://github.com/user-attachments/assets/f08d029b-dc21-4df7-968b-452cd13f6c5c" /> Next you can set the build pack to a DockerFile, and you give it the path to the file in the repo: <img width="856" height="436" alt="02" src="https://github.com/user-attachments/assets/1a1b18a8-8748-4a70-b453-67e33915cb04" /> When you deploy, it starts building the Docker image, and I end up with this issue in the logs and it ends up being an unhealthy deployment. I'm running a VPS with Ubuntu 24.04 and Coolify is the base install. Currently this server's running n8n, Baserow and several other apps without issue, so I'm not quite sure how to proceed - and I'm definitely not a server/git guy :) <img width="1123" height="664" alt="03" src="https://github.com/user-attachments/assets/01dda726-e931-4c8a-84c6-5fba17f8dddf" />

…

On Wed, Dec 3, 2025 at 7:07 AM Shamu ***@***.***> wrote: @pfriedl <https://github.com/pfriedl> - I was just thinking the same thing! 🙂 Before we make it a deploy with one click we could just create a docker compose that handles everything. From reading the issues I think here (#1801 <#1801>) it was also discussed to have a Prebuilt Docker Image so if we are able to pull it from a public registry then we could set this up to be a very easy deploy. I want to take a look at it when I have some time but if someone does it faster, then thank you in advance! — Reply to this email directly, view it on GitHub <#1828 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJAJNQYUHNIUROEDX5QRRL373OBNAVCNFSM6AAAAACN3R3KPCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJUHA3TGOI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[monorkin]

The images you added are broken in Github. Could you re-upload them?
If you have the option to use a regular Docker image, we have those pre-built: ghcr.io/basecamp/fizzy:main

[pfriedl]

Uploaded those initial images. In Coolify, we can't really execute CLI commands. If I use the Docker Image install and add the pull source ghcr.io/basecamp/fizzy:sha256-befd3706c06f8c312e622f276a017751dbd8ba999cd2d286873040f47242341d.sig then I end up with another issue:

[pfriedl]

OK, got a deployment, but there's something up with how the Docker sets up the server.

[pfriedl]

I think what needs to happen is that fizzy is binding to 127.0.0.1 and needs to bind to 0.0.0.0 for Coolify's proxy to reach it. Any ideas?

[monorkin]

The first error looks like a misconfigured image.

Fizzy binds to 0.0.0.0, can you provide some details about the server error?

[eddywashere]

Was tracking #1911 and noticed someone might have had this working in coolify. @arnsteinsm could you share any tips?

[eddywashere]

I missed that the fizzy template is there now. I am having a hard time configuring mailgun, might be a port issue on my host but I am curious what others used if they are using mailgun.

[SamuelAierizer]

I just saw this PR was merged and now Fizzy is part of Coolify one click install list: coollabsio/coolify#7468

Just tested it myself and it worked great. Think @pfriedl that we can close this?

[eddywashere]

I had an issue with email not sending. It seemed like the queue was not getting processed. Put up a pr to fix on coolify side, coollabsio/coolify#7612 but I’m curious how it worked for other folks and if I had something misconfigured. Afaik the SOLID_QUEUE_CONNECTS_TO was no longer referenced in the latest fizzy code.

[pfriedl]

This is awesome, and sorry for just getting to this. I'm testing a deployment myself and will report back!

[pfriedl]

The Coolify install works!
Caveat: you can't set the SMTP ENV variables in Coolify, they have to be set in the Docker compose file, and I just used:

MAILER_FROM_ADDRESS=[email protected]
SMTP_USERNAME=[email protected]
SMTP_PASSWORD=redacted
SMTP_ADDRESS=smtp.mailgun.org
SMTP_PORT=587

And deployed. All good now, thanks! @eddywashere Mailgun is working with these settings.

[eddywashere]

One last thing, TLS_DOMAIN will conflict with coolify proxy if that's handling ssl certs for you. So either fizzy (or likely thruster will need to be updated to allow setting just --host via env var or add another env var when setting TLS_DOMAIN that defers ssl to a higher level proxy.

I only noticed this because avatar images in the notifications pane (new notificatios) will include a "example.org" url prefix in the img file path instead of my apps actual domain.

The alternative I'm trying to avoid is having a cloudflare rule that changes my ssl setup for just this domain.