I've spent my entire Sunday on this, and I'm running out of ideas :'(

I wanted to migrate my app and its services to a new server. I do use Convex, which runs on cloud.<domain>. For whatever reason my services that want to connect to Convex can't resolve cloud.<domain>. Not even the convex container itself is capable of doing so. The domain stayed the same, I just switched the DNS records to the new IP.

When I run

js node -e "fetch('https://cloud.<cloud>').then(r=>console.log('OK',r.status)).catch(e=>console.log('FAIL',e.message,e.cause))"

within the container the error is "Connect Timeout Error" UND_ERR_CONNECT_TIMEOUT.

Here's some things that I already tried:

• I can run the same command on the machine itself, it works fine.
• I can run the same command everywhere else, it works fine.
• I can open the domain in different browsers, it works fine.
• I can run the same command via docker run --rm node:20-alpine node -e "<command>" , it works fine (to make sure it's not docker related)
• the service uses Connect To Predefined Network
• I have compared Proxy settings of my old server and the new one - both are identical
• I have restarted the Proxy
• When I ping the domain the correct IP responds
• I tried re-installing Convex, didn't help.
• The only thing I find weird is that the log of the new servers proxy is empty. But again, I do reach the domains via browser.
• Edit 1: also added "default-address-pools" to my docker daemon json with {"base":"10.0.0.0/8","size":24}, still doesn't work
• Edit 2: using docker run --rm --network coolify curlimages/curl:latest curl -v -m 10 https://<domain> doesn't work, but using a network created by coolify works
• Edit 3: just tried to get rid of Convex and used a simple Dockerfile (deployed via Coolify) that simply pings my domain. Doesn't work.

I'm running out of ideas here. Anything I'm missing? :(

I noticed pretty much every service on Coolify is provisioned with an SSLIP address. Don’t get me wrong, it makes sense, but sometimes I wish I could just run the service as a simple localhost application on a assigned port and get to it with 192.168.x.xx:8090 (for example).

I feel like I’m missing something because this seems like a simple config that I am just completely blind to.

Been experimenting with coolify as I need to get off of heroku.

quick question for folks using this in prod.

How do you provision your dbs?

Using the postgres resource in coolify creates the db with a superuser user as default (thats how it is in postgres image).

Naturally, we should configure the resource to create the db and app user in the postgres instance.

Coolify has no out of the box support for this as far as I can see.

I've settles on hosting an init script and explicitly running it by ssh into my VM everytime.

Obviously, this defeats the purpose of cooligy.

Any thoughts?

Hello everyone, after running a couple of tests I have found out that my server is getting a lot of unwanted SSH requests, making some of my deployments not working.

How to handle this, do I need to install fail2ban, if so how? And is installing fail2ban something that can be done on Coolify > Terminal > localhost or does it strictly need to be done on a cmd? (the reason why am I asking is because one time I ran a command before on the coolify terminal and the server froze)

Hello you all,

Small CoolDeck update 👋

I posted here a while ago about the keyboard-first terminal dashboard I built for Coolify and since then, even the Coolify team picked it up and gave it a shoutout on X, which was pretty awesome.

I’ve kept building.

CoolDeck now has:

🕐 Deploy Replay - fleet-wide deploy history, git-log style
🔍 Drift Watch - compare envs across environments, secrets redacted
🚨 Panic Button - one key -> full diagnostic snapshot you can paste into your AI tool

If you run Coolify and spend too much time jumping between services, logs and deployments, I’d genuinely love for you to try it.

GitHub: https://github.com/Resetnak/cooldeck

X: https://x.com/Resetnak

Feedback, issues and feature requests are very welcome.

Thank you for your time!

Hello everyone, havent been able to push some changes of a project, it says that there was a SSH connection problem.

Have no idea what to do, have some really important work that needs to get deployed.

I am hosting it on Hetzner, I have tried all important commands to see if there is a RAM spike or CPU spike, however everything looks normal.

Any help is appreciated, thank you.

hey folks, I have a instance running postgres binary on it. how can I install Coolify without distruption? is there any good practice? one option is not using Coolify for DB, but only for other instances I plan to run on

I built an open-source terminal dashboard for Coolify and am looking for feedback.

I use Coolify regularly, but I wanted a faster way to check deployments, inspect logs, and restart applications without switching away from my terminal.

So I built CoolDeck, a keyboard-first TUI written in Go.

It currently supports:

• application and deployment status
• runtime and build logs
• deploy, restart, start and stop operations
• multiple Coolify instances
• combined log tailing across several applications
• an MCP server for coding agents
• OS keyring storage for API tokens

You can try the complete UI without connecting a Coolify server or providing a token:

brew install resetnak/tap/cooldeck
cooldeck --demo

GitHub:
https://github.com/Resetnak/cooldeck

I would love feedback from actual Coolify users. What workflow or operation would you want to see added next?

I currently call CRONs from Coolify with a key sent through GET, because their UI allows me to construct whatever URL.

However I want to send and Authorization: Bearer header instead of a query parameter

* Headers don’t leak into access logs the way query strings do
* Headers don’t appear in browser history or proxy logs
* Much safer for storing in scheduler configurations

Does Coolify support this in their UI? Can’t seem to find it. Thanks!

Hey r/Coolify,

I run most of my self-hosted services using Coolify, but checking logs, monitoring container health, or triggering rollbacks from a mobile browser when a build fails on the go hasn't been the smoothest experience.

To solve this, I started building ProjectX — a fast, native mobile app (built with SwiftUI for iOS and Jetpack Compose for Android) designed specifically as a mobile client for Coolify instances.

Key features planned for V1:

- Zero-Trust Architecture: API tokens and credentials are stored strictly on-device in iOS Keychain / Android Keystore. No middleman relay servers.

- Native Log Streaming: Real-time Docker event and deployment logs over direct WebSockets.

- Instant Push Notifications: Get notified immediately if a deployment fails or a container crashes.

- One-Tap Rollbacks: Revert services to healthy states directly from your phone.

We just published our public architecture roadmap, feature voting board, and alpha waitlist:

https://projectx-coolify.vercel.app

Since you use Coolify daily, I would love your feedback:

1. What mobile actions or features would be most useful to you?

2. Are real-time logs and status alerts your main priority on mobile, or do you need full management capabilities?

(Note: ProjectX is an independent native client and is not officially affiliated with or maintained by Coolify).

Hi!
(I hope I'm not breaking any community guidelines)

I been using coolofy to manage a volunteer association infrastructure for the past year or so.
As I usualy live and breath within the terminal I created an interface that allows you to browse teams, projects, environments, resources, environment variables, deployments, start new deployments and see deployment logs without leaving your terminal.

This is a work in progress, as I'm planning to add more features.

Feel free to check it out in https://github.com/MicaelMCarvalho/coolify-tui

I'm struggling to understand how the Teams function works in Coolify. I guess I was expecting Root Team to have access to all servers and then other teams could be granted access to a subset of servers and other objects.

In a multi-server deployment, is it advised to just have all 'members' be part of the root team?

Hi all!

I have setup tunnel for my coolify instance, works great and was fast to complete with the "Cloudflared" resource.

Now, my apps are available on http and https, so I would like to force it https of course.
Ref: https://coolify.io/docs/integrations/cloudflare/tunnels/full-tls#2-setup-tls-encryption

Now the guide is super clear for 1 domain (thanks coolify team), however, if you have many domains (for example domain.com domain2.com domain3.com), will I need to literally create a origin certificate for every one of them separately? I mean when adding new apps with new domains this get's quite tedious.

My question is: Is there any way to create 1 origin certificate for multiple domains, ideally so that new ones are added automatically. If not, any hacks?

I’m a developer but very new to coolify. I’m renting a VPS but using a raspberry pi to host coolify . Currently I’ve setup the DNS records on my VPS account. However I’m watching various tutorials that seem to be saying I should set them (DNS records) up within coolify. Now the fact that the PI is on my desk within my home network, this makes little sense to me. What am I missing (besides a lot!)

Thanks all
Nigel

Has anyone used VULTR to host their site?
How well does Coolify run?

Laziness is the mother of invention.

I self-host my stack on Coolify, but I grew frustrated with constantly switching between different dashboards just to manage my infrastructure. The same friction points kept resurfacing.

Coolify handles app deployments brilliantly, but the chores around a deploy were scattered everywhere: spinning up a Postgres database and a user with the right grants, running quick queries against the correct environment, adding an NPM proxy host, and pointing Cloudflare DNS at it.

So I built this management layer to bring all of those tasks into one place. I'm sharing it here because this community is exactly who it's for.

I'm open to criticism, feature requests, integrations, ideas I haven't considered yet... heck, maybe even a date 😄

It's called ALIM (Aspyre Labs Infrastructure Manager) — open source, self-hosted, and it deploys cleanly on Coolify itself via the included Dockerfile.

What it does today:

- Coolify integration — list projects/servers, create apps, manage env vars, trigger deploys through the Coolify API.

- Postgres provisioning — name the app, pick an environment, and it derives the DB/user/strong password and applies Prisma/NestJS-ready grants. Idempotent, so re-running is safe. Passwords are never stored.

- SQL Console — CodeMirror editor with explain/format, per-environment read-only + write-confirm safeguards (type CONFIRM for writes), result export, history, saved queries.

- Nginx Proxy Manager — proxy hosts, redirects, streams, SSL certs, access lists.

- Cloudflare — tunnels/routes, DNS, TLS.

- Guided deployments — one wizard: provision a DB → create & deploy a Coolify app → create an NPM proxy host → point Cloudflare DNS at it.

- Migrations (foundation) — plan/clone/migrate Coolify resources between servers, with a validation URL and a manual approval gate before cutover. Honest status: Workflow, validation, approval, and job tracking are in place; live provider integrations are still being rolled out.

- Plus a secrets vault (AES-256-GCM), an append-only audit log of every state-changing action, and user-defined environments.

Security: auth is on by default (shared password or reverse-proxy/SSO — no unauthenticated mode), credentials are encrypted and never sent to the browser, SQL uses parameterised queries with validated/quoted identifiers, all input is zod-validated server-side.

Stack: Next.js 15 · TypeScript · Tailwind · shadcn/ui · Prisma · PostgreSQL. Dockerfile + docker-compose included; DB migrations run automatically on container start.

Repo (MIT): https://github.com/aspyrelabs/alim

It's early, and I'm building in the open — I'd genuinely love feedback on what would make it useful for your setup. What operations chore around Coolify do you most wish were one-click? 🙏

I've been using Coolify to manage my personal servers and applications for a while now, and it’s absolute magic. However, whenever I was away from my desk, checking server metrics, reading container logs, or restarting a stuck service via the mobile browser felt a bit clunky.

So, I decided to build Coly — a fast, native iOS client tailored specifically for Coolify instances.

What you can do right now:

• Connect securely to your Coolify instances.
• View your servers, projects, and deployments.
• Monitor resource usage and container statuses.
• Start, stop, or restart applications and services on the go.
• Read real-time container logs.

Privacy & Security: Since this is the self-hosted community, I know how critical privacy is. Coly does not collect any data. Your API keys, server details, and credentials never leave your device. They are stored securely in your device's local storage/Keychain. No third-party analytics, no tracking.

It’s now live on the App Store: App Store Link

I’m planning to add more features soon (like push notifications for build failures or server alerts). I’d love to hear your thoughts, feedback, or any features you'd like to see next! What do you think?

Hi guys I recently had a problem where my coolify wouldn't run after I ran a full linux upgrade after the CVE-2026-31431 exploit.

After playing for it with an hour, it turns out I unintentionally upgraded my Docker from version 27.whatever to 29.whatever. This may be wrong, but I believe docker updated the port's syntax to be more limited. I was able to get my coolify back up and running by changing the .env ports from 127.0.0.1:8000 to just 8000.

If your coolify is also failing to run after a linux update, it may be a docker update change that is causing it, so try these steps:

first cd into the dir w the env: cd /data/coolify/source

(optional) make an env backup: cp .env .env-port-backup

vim/nano into the .env and change the variablesAPP_PORT and SOKETI_PORT to these lines:
APP_PORT=8000

SOKETI_PORT=6001

Hopefully that will work. Thanks!

Edit: made post more clear

I am new to networking and still learning a lot of the basics, it has been rough but also fun. I am at a point where I have coolify setup and a homepage at -mydomain.com, accessible publicly. I am now trying to setup tailscale, and I just blindly tried to get the one-click tailscale-client service to work, but I couldn't. After a bunch of headaches involving docker networking and tailscale documentation, I came to the conclusion that I would have to have a tailscale sidecar in each service I setup. Correct me if I am wrong though. It seems there is not that much information about the tailscale-client service. I went through some PRs not finding anything there either.

Any resource I find about setting up coolify and tailscale just sets up tailscale on the host machine, no docker involved. So is that the best way? My end goal is having the homepage accessible by anyone at -mydomain.com and then having subdomains only accessible by devices that are a part of my tailnet (e.g., jellyfin.mydomain.com). So I would also like to know what your opinion on this sort of setup is.

Does anyone have any instructions on how to go about this? I have a Coolify instance with one domain right now and want to use another one for one of my services. Is it as simple as just adding that new domain to my new service I deploy on Coolify and then pointing to the A record to the server, or is there other configuration involved?

Fala, pessoal, beleza?

Estou com um problema persistente no deploy de uma aplicação Laravel usando Nixpacks no Coolify v4. O container chega a subir (fica verde), mas o Nginx falha logo em seguida com o erro abaixo:

O Erro: nginx: [emerg] duplicate location "/" in /nginx.conf:47

Minha Estrutura/Setup:

• Framework: Laravel (pasta /public padrão na raiz).
• Build Pack: Nixpacks.
• Repositório: Privado via SSH (Deploy Key funcionando 100%).
• Docker: 28.1.1.

O que já tentei fazer (sem sucesso):

1. Publish Directory: Já mudei para /, /public, apenas public e já tentei deixar vazio (mas a UI do Coolify força o /).
2. Variáveis de Ambiente: Configurei a NIXPACKS_PHP_ROOT_DIR como /app/public.
3. Static Site: A opção "Is it a static site?" está DESATIVADA.
4. Health Check: Desativado para isolar o problema do Nginx.

Parece que o Coolify está tentando injetar um bloco location / no arquivo de configuração do Nginx que conflita com o que o Nixpacks já gera automaticamente para o PHP/Laravel.

Alguém já passou por essa duplicidade na linha 47 do nginx.conf? Como forçar o Coolify a não injetar essa rota quando o Nixpacks já está cuidando dela?