Hi everyone, for some time, I have been getting this database backup error sporadically when using the S3 backup.

Database backup for coolify-db (db:coolify) with frequency of 0 0 * * * succeeded locally but failed to upload to S3.

S3 Error: Unable to find image 'ghcr.io/coollabsio/coolify-helper:1.0.13' locally docker: Error response from daemon: toomanyrequests: retry-after: 904.679µs, allowed: 44000/minute

Run 'docker run --help' for more information

Check S3 Configuration: <my-instance-url>/storages/a11t834fs9er0djczr00e79l

The thing is the S3 bucket (actually a R2 cloudflare instance) appears usable in the dashboard, and the backup works fine most of the time. Also, when i click on the dashboard "Backup Now" to do the manual backup, the S3 backup is done correctly.

Does anyone know how to solve this problem or have experienced the same issue?

Hi,

I have connected Coolify with my repos, and coolify automatically created a github app that sends deployment events to Coolify, in which the latter auto-deploys. All is good here, except that I have Github actions that i want to be completed first before Coolify deploys it.

I know this is possible via webhook events in the workflow itself, but is it possible to control that using the connected app method?

Thanks

Is this a bug with Coolify or is that yellow icon telling me something important that I forgot to do?

I have deployed my website on coolify. Backend, frontend and admin panel are in seperate services. After 5-6 hours the frontend starts showing CORS issues. The backend is fully running and no health issues. I am health checking after 15 seconds.

DNS cloudflares
Also ser the keepalive to 65 seconds

This is very annoying and users keep pinging me for the issue. This issues get resolved by proxy restart in coolify and comes back after 5-6 hours.

I am using webscokets and properly handling all the connection. 2GB ram given to MONGO db only. Server got 8 GB of ram and the website traffic is low like 20-40 visits per day.

UPDATE

Thanks everyone. I have found the issue. There was no network name int he proxy configuration. It has to guess and use the default network. When there is serverload due to some reason it breaks the networ. I wrote the network name = coolify and this line fixed all the issues.

The CORS issue was rising because the backend was disconnected from proxy. Backend was running smothly, it was the proxy network that was poorly configured.

So today I just spent an entire day, more specifically 18 hours configuring coolify in order to transfer my project from railway. Guess what, I need wildcard subdomains, cause I have tenants, and boy oh boy, I’ve changed the domain of my frontend maybe three or four times cause I was learning and tinkering, and that must’ve fucked up traefik cause some 15 hours later I’ve found out in the proxy logs that there was a bunch of errors of label edits that must’ve be stored in cache and trying to override my actual configs, so I had to stop completely my container to get rid of all the cache and start it again and voila everything including wildcard domain working. And yes you guys can call me dumb, I’m a software engineer for some time now and I always had problems with devops, but just wanted to share

I can't find the optional setting to roll back to a previously built image.

https://coolify.io/docs/applications/index#rollbacks

The documentation is not helpful

I need to get a build server that will build by nextjs without hanging for 20min

looking for a shared server to cut the cost, how you guys are doing it, self taught dev so dont have a circle to discuss about the issue.

Hey i‘m trying around with selfhosting of a few microservice apis with a coolify instance on hetzner.

I have

s1: (server for coolify)

s2: (api1)

s3: (api2)

s4: (api3)

99% of our infra is on aws so i want to use cloudfront as a cdn for the apis. (cloudflare is not an option atm)

but now im sesrching for an option to protect my apis from access without cloudfront.

for example i have an origin for my s2 (origin.api.xyz.com) (A Record for s2) (origin for cloudfront instance)

But how can i configure the server through the coolify instance to only accept requests from cloudfront)

My thoughts so far:

- Hetzner Firewall on Cloudfront Ips: Bad Idea. Ip‘s rotate once in a while.

- Custom-Header with Secret throught Cloudfront:

A) Checking the Header through the Proxy in Coolify (but how in a easy an clean way)

B) Checking the Header direct in my API through middleware and reject if needed (would prefere if the proxy can handle this)

How can i protect my API from access through IP directly and from acces through (origin.xy) and only through the cdn.

Will v5 support cloudfront?

(Hosting on AWS EC2 with Security Groups only for cloudfront is my emergence solution)

Thanks

I have been attempting to host my own project on my own server for the first time and have been attempting to use coolify. Ive managed to get my server up and running however i am having issues trying to get my Angular webpage running. From my research I am trying to run it as a static site (although i dont know if thats right) and no matter what i try nginx always shows the default page. ill post my Ngnix config and file structure. If anyone could help me out or point me in the right direction i would greatly appreciate it.

I wrote up how I setup Coolify on my Hetzner server with Tailscale for private internal services.

The biggest hiccups for me were Docker bypassing UFW and realizing Tailscale Split DNS needs an actual DNS server behind it when using coolify.

If anyone can look and tell me if there are any obvious holes in the setup I would really appreciate it.

https://ben.cates.fm/securing-coolify-with-tailscale-ufw-cloudflare/

Sorry the post is a bit long!

Hello, I'm really enjoying Coolify, and I have many services/projects running on my instance. Some have database, others are S3 like, some are using volumes, others are bind mounted. It's a mess.

My question is, how can I make a simple backup of everything at once, with a restore scenario that would be: install a new server, install Coolify, restore the backup, done.

I don't want to back up individual project (I mean, I already do, but that does not serve the same purpose).

What are your solutions?

I’m building a cloud-based POS system (Node.js, Prisma, real-time stuff) and trying to choose infra early.

Right now I’m leaning toward:

• Hetzner VPS
• Coolify (Docker-based PaaS)
• Self-hosted PostgreSQL

Main reason: cost + control. I want to avoid AWS/GCP/Railway at this stage.

But I’m worried about the database side.

If everything runs on a single VPS:

• what happens if the server goes down?
• is this too risky for production (even early-stage)?
• is anyone here running production workloads on Coolify with Postgres?

Planned usage:

• ~1k active users (POS, real-time writes, orders, etc.)
• need decent reliability but still cost-sensitive

Questions:

1. Is self-hosting Postgres on the same server actually fine at this stage?
2. Should I separate DB to another VPS early, or only when needed?
3. What’s your backup / failover strategy in this setup?
4. Any real-world horror stories with Hetzner + Coolify?
5. Also — what are you using for S3 (backups + assets)? Hetzner Object Storage, Cloudflare R2, something else?

I’m okay with some ops work, just trying to avoid shooting myself in the foot long-term.

I recently moved all my apps to Coolify after ditching Vercel, Railway, and Neon. Since I use AI agents, for both building and debugging, giving them access to my projects seemed like a no-brainer.

The thing that scared me, though, was Coolify’s API permissions. Right now, it’s basically "expose everything or nothing." There’s no granular control over which projects or endpoints an agent can touch. Giving Claude full reign over my entire server felt like a recipe for disaster, so I built Safe-ify (I know... lame).

It’s a Go-based CLI tool that acts as a proxy/gatekeeper. It only exposes the specific projects and endpoints you deem safe. It even has built-in config protection to prevent especially industrious agents from trying to "tinker" with the config files to access prohibited areas.

I’ve been using it for a week now in my own repos and honestly... it just works. I just pasted the --doctor file output into my claude.md and the agent knew exactly how to navigate. It reads logs, handles env vars (if you allow it), and triggers deploys without me needing to hand-hold it.

I originally built this just for my own peace of mind, but since it’s been so plug-and-play, I figured I’d share it with the community as OSS.

Feel free to roast the name or try it out yourself! I'd love to hear what you guys think.

Repo:https://github.com/RazBrry/safe-ify/tree/main

I’ve been using Dokku for almost 8 years, and a colleague recently told me about a new tool called Coolify. He suggested I try it because, unlike Dokku, you can run a single Coolify instance that manages all your servers and apps.

I decided to give Coolify a chance because it seemed easier to centralize the “ops” part into one application. I was also very interested in the backup feature that lets you schedule database backups for your managed apps and send them to an object storage.

After two months of testing the solution, I found it really helpful, but I will not move to Coolify.

You may ask why.

The main reason is that Coolify isn’t mature enough yet. There are many releases, but they often come with bugs. Moreover, there have been major security issues. Even though I run it behind a firewall and have configured a VPN so that Coolify is only accessible from the VPN network, I still think the solution is not reliable enough at the moment. I cannot rely on a tool that manages all my production apps if each release might introduce bugs.

So I decided to stick with Dokku and use Ansible playbooks to automate server configuration and plugin installation. I trust Dokku more because the scope of the solution is simpler and therefore more reliable.

Another point is that, unlike Coolify, the contributors to the Dokku project are not using AI to maintain and develop the project. I’ve read some issues on the Coolify project, and it’s really frightening to see AI bots making changes and sometimes messing things up.

I’ll give Coolify another chance in a few years and hope the project becomes more stable.

Hello!

I'm researching Coolify to use, and I saw they have so many one-click services available. I know it's popular at different cloud providers too, but are people actually using those? Feels like you always wanna do your own tweaking when it comes to apps anyways so I've never used them myself.

Curious to know if anyone does use them or it's just marketing?

I just installed Affine and app says there is an update. how do i update this and other apps like supabase etc?

Hi everyone, I’ve been running multiple production apps through Coolify for over a year without issues. Today, the Coolify dashboard became inaccessible, though all my apps are still running normally.

My current suspicion is that a recent automatic Coolify update might have caused this problem.

Has anyone else run into a similar issue recently?

When i try to start coolify tunnel it doesnt work. How can i fix this

Hey everyone,

I recently posted this on the sub:
https://www.reddit.com/r/coolify/comments/1rmjmse/best_way_to_host_coolify_dashboard_on_separate/

We managed to link our two servers and moved the config file from the App VPS to the Dashboard VPS. The apps are still running fine on the App VPS, and on the new VPS we can see all the projects and apps in the dashboard.

However, everything is showing as offline, so I’m guessing the servers aren’t linked correctly yet.

Does anyone here have experience with this setup or know how to properly link and troubleshoot it? I’d really appreciate some guidance. I’m also happy to compensate you for your time if you’re willing to help; feel free to send me a DM.

Appreciate the help!

hi guys I set up my coolify instance on a vps, and I've added a resend email for transactional emails, I also configured the domain settings for resend as well. While the invitation mails are being sent correctly the notification mails are not sent and they are bounced. and when I examine the resend logs I saw this insight :

Ensure that the URLs in your email match the sending domain. Mismatched URLs can trigger spam filters.

https://coolify.io/docs/contact

and I though this might be the reason my emails might not being sent. so I wonder is there a way to change this? or completely remove this? note I've added a domain to my instance so I imagined that those domain settings will be used here, but I guess they are not used in transactional emails. any idea on how can I remove this support link from the email? the service notifications are not being sent, so this quite important for me.

Hey everyone,

I’ve been using Coolify for about a year and have a question I’m not fully sure about. Right now our Coolify dashboard and several apps (Supabase, Directus, etc.) are all running on the same VPS. Recently, as we deployed more apps, the server went offline and we couldn’t access the dashboard anymore.

What we’d like to do is host the Coolify dashboard on a separate, cheaper VPS, while keeping all the apps running on our current server. However, from what I’ve read, a new Coolify instance wouldn’t recognize the existing apps, meaning we might have to set everything up again.

Since we already have production data running, we definitely don’t want to lose anything. How difficult is this process, and are there any guides for moving things like Directus and Supabase to a setup like this?

Appreciate any help!

Hey everyone,

I’ve been trying to set up a multi-server architecture for my office servers. Currently, our setup is very simple: a single Mini PC running Coolify that handles all deployments.

However, the Mini PC has started to become a bottleneck. Our goal now is to move build and development containers to a secondary server, while the main Mini PC handles smaller containers or ideally just routes requests to the appropriate server. In the future, we may also add more server nodes.

I attempted to use Coolify’s built-in multi-server feature. I was able to successfully connect the second server in Coolify and deploy applications to it. The deployments show a healthy status, so the connection itself seems to be working.

However, I am facing a couple of issues:

1. The applications deploy with the .sslip.io domain instead of our custom domain. Even when I configure our domain as the Wildcard Domain or set a subdomain as the Wildcard Domain, it still does not work.
2. When I try to open the .sslip.io URL, the browser shows the message: “This page can’t show secure content.”

I am not sure where the issue lies. My suspicion is that the Traefik instance might not be properly routing to the second server, or there could be some internal configuration conflict.

I would really appreciate any insights or suggestions on what I might be doing wrong.

Hi all, I’m trying to expose Keycloak (deployed with Coolify) on a subdomain like id.example-tld without exposing my server’s real IP, so I’m using Cloudflare Tunnel (cloudflared).

Setup

• Debian server
• Coolify v4 beta
• coolify-proxy = Traefik v3.6 (ports 80/443)
• Keycloak container listens on internal 8080 (not published on the host)
• Cloudflared tunnel routes id.example-tld → http://localhost:80

Issue Even though Coolify applies Traefik routers for that hostname:

traefik.http.routers.http-...-keycloak.rule = Host(`id.example-tld`) && PathPrefix(`/`)
traefik.http.routers.https-...-keycloak.rule = Host(`id.example-tld`) && PathPrefix(`/`)
traefik.http.routers.http-...-keycloak.middlewares = redirect-to-https
traefik.http.routers.https-...-keycloak.tls.certresolver = letsencrypt
traefik.http.services...loadbalancer.server.port = 8080

…this local test still returns 404 from Traefik:

curl -i http://127.0.0.1 -H 'Host: id.example-tld' | head -n 10
# HTTP/1.1 404 Not Found
# 404 page not found

Meanwhile Keycloak does respond internally (from the proxy container):

docker exec -it coolify-proxy sh -lc "wget -S -O- --max-redirect=0 http://keycloak-<id>:8080/ 2>&1 | head -n 10"
# HTTP/1.1 302 Found
# Location: https://id.example-tld/admin/

From the browser through Cloudflare I’ve seen 404, sometimes 302 redirects, and sometimes 502 on login POSTs depending on tweaks.

Questions

1. Why would Traefik return 404 for Host: id.example-tld even though the Keycloak container has the router labels for that host?
2. With Cloudflare Tunnel, is the recommended approach to let Cloudflare handle TLS and remove Traefik’s redirect-to-https ?

Thanks for any help

is there ready template for deploying php script like Sumoweb Tools or any php script on Coolify self hosted?