DEV Community

Fernando Chagas for Nuvits

Posted on Originally published at nuvits.net

How to install Coolify on an Ubuntu VPS

This guide installs Coolify on a clean Ubuntu 24.04 VPS, with the official script, and leaves the panel up on port 8000. At the end, the firewall applies to the ports Docker publishes, and you can see what the proxy answers on 80 and 443 before a domain exists.

The test ran on 18 November 2026 in a 64-bit Ubuntu 24.04.5 LTS virtual machine, with 2 vCPU, 2.9 GiB of RAM and a 40 GB disk, with no Docker and no panel already there. The installer finished in 1 min 27 s. There was no public domain pointing at that machine, so the production certificate was not issued: the domain section says exactly how far the check went.

What you need

  • A VPS running 64-bit Ubuntu 24.04 LTS, with SSH access. The installer runs as root.
  • The minimum the installation docs ask for today: 2 CPU cores, 2 GB of RAM and 10 GB of free disk, on amd64 or arm64. The same page recommends a fresh server, so the panel is not mixed with another Docker already in use.
  • A domain only when you are going to serve the panel or an application over HTTPS. You can create the account and use the panel by IPv4 before that.

The machine in this test had room for the panel on its own: after the install the disk had 4.5 GB used and 34 GB free. An application published next to Coolify needs memory and disk beyond that floor. The card beside the article points at a plan above the minimum.

If the plan offers the preinstalled application, you can ask for Coolify when you order. The path below is the official script, on an Ubuntu that arrives with only the system.

Whoever arrives first becomes the administrator. The docs warn that the first account has full access to the instance, including the server. Create that account as soon as the installer finishes. The window stays open for 10 minutes.

Run the official installer

Sign in as root, or use sudo. The command is the one in the docs:

curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bash
Enter fullscreen mode Exit fullscreen mode

The script installs whatever is missing of curl, wget, git, jq and openssl, checks OpenSSH, installs Docker Engine when the system does not have it yet, writes the daemon configuration, downloads the Coolify files and starts the containers. On this image the packages from the first step were already there, and that step finished immediately. OpenSSH was already installed, with PermitRootLogin without-password on port 22, and the script recorded that root login by key was allowed.

The install log kept what the stable channel chose:

| Operating System  | ubuntu 24.04
| Docker            | latest
| Coolify           | 4.7.5
| Helper            | 1.0.19
Enter fullscreen mode Exit fullscreen mode

In the terminal, the end was this:

Coolify is ready!  Installed in 1m 27s
Enter fullscreen mode Exit fullscreen mode

It also prints one or more addresses with port 8000. Use the VPS public IPv4, in the form http://VPS_IP:8000.

The docs say to remove Docker installed by snap before running the script, if that is the case. The installer refuses that package. On this machine Docker was not installed, and the script used the Docker Engine installer. The version that remained was 29.10.0, with Compose v5.8.0:

Docker Compose version v5.8.0
Enter fullscreen mode Exit fullscreen mode

The daemon was left with log rotation and an address range for Docker networks. The file it wrote was this:

{
  "default-address-pools": [
    {
      "base": "10.0.0.0/8",
      "size": 24
    }
  ],
  "log-driver": "json-file",
  "log-opts": {
    "max-file": "3",
    "max-size": "10m"
  }
}
Enter fullscreen mode Exit fullscreen mode

Create the root account

Open http://VPS_IP:8000 in the browser. With no account, the panel leaves /login and opens the registration form. On this install, GET / answered 302 to /login, and /login arrived at /register with 200. The page title is Coolify, and the text asks for the instance root account: name, email, password and the password again. The page itself requires at least 8 characters, with upper case, lower case, a number and a symbol.

I submitted that form inside the 10-minute window. The response was 302 to /settings, and /settings then went to /onboarding, with the title "Onboarding | Coolify". Onboarding offers to connect the server or skip. The installer had already left a local server and the proxy running; the onboarding click was not required for the panel to answer.

If the page says the window closed, the installer says to restart the container and try again:

sudo docker restart coolify
Enter fullscreen mode Exit fullscreen mode

What stayed up

Right after the installer, sudo docker ps showed these healthy containers. The "Up" times are from that minute:

NAMES                       IMAGE                       STATUS                        PORTS
coolify-proxy-error-pages   busybox:musl                Up 16 seconds
coolify-proxy               traefik:v3.7                Up 22 seconds (healthy)       0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 0.0.0.0:443->443/udp, [::]:443->443/udp
coolify-sentinel            coollabsio/sentinel:1.1.5   Up 23 seconds (healthy)
coolify                     coollabsio/coolify:4.7.5    Up 57 seconds (healthy)       8000/tcp, 8443/tcp, 0.0.0.0:6001-6002->6001-6002/tcp, [::]:6001-6002->6001-6002/tcp, 9000/tcp, 0.0.0.0:8000->8080/tcp, [::]:8000->8080/tcp
coolify-db                  postgres:15-alpine          Up About a minute (healthy)   5432/tcp
coolify-redis               redis:7-alpine              Up About a minute (healthy)   6379/tcp
Enter fullscreen mode Exit fullscreen mode

What that means in practice:

  • The panel is coollabsio/coolify:4.7.5. Port 8000 on the server is port 8080 in the container. Ports 6001 and 6002 are published too.
  • The proxy is traefik:v3.7, on ports 80 and 443. It also publishes 8080 and 443/udp.
  • Postgres 15 and Redis 7 do not publish a port on the host. The PORTS column only shows the internal port.
  • The image coollabsio/coolify-helper:1.0.19 was pulled and did not stay as a permanent container.
  • The local server the installer registered is named localhost, points at host.docker.internal on port 22, with the user root. That server's proxy was left as Traefik, running.

Check on your server with:

sudo docker ps
sudo docker compose version
Enter fullscreen mode Exit fullscreen mode

Firewall

Docker publishes a port on its own, and ufw does not block that traffic. The Docker docs describe the bypass, and the Coolify firewall page says not to trust ufw on its own. The test with Apache, the timeout and the rule that actually closes the port are in The Docker port stays open with ufw.

On this machine ufw 0.36.2 was configured after Coolify, which is the order that leaves Docker already up so ufw-docker can see the DOCKER-USER chain. The tested copy of ufw-docker is commit 020a8699f95592561f254d8d4ad1bb40d401dfc7 (18 May 2026 in the repository, checked again on 18 November 2026). The SHA-256 of the downloaded file was 643e56b080567c567b4aa28650196849b2a2da5dd0473fd3e5216b0886035ab0.

sudo apt update
sudo apt install ufw
sudo ufw allow 22/tcp
sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw --force enable

sudo curl -fsSL -o /usr/local/bin/ufw-docker \
  https://raw.githubusercontent.com/chaifeng/ufw-docker/020a8699f95592561f254d8d4ad1bb40d401dfc7/ufw-docker
sudo chmod 755 /usr/local/bin/ufw-docker
sha256sum /usr/local/bin/ufw-docker
sudo ufw-docker install
sudo ufw reload
Enter fullscreen mode Exit fullscreen mode

ufw allow 22/tcp comes before ufw enable so SSH is not dropped. ufw-docker install changes /etc/ufw/after.rules and /etc/ufw/after6.rules, writes a copy of each and asks for sudo systemctl restart ufw. I ran sudo ufw reload, and the block was already in effect.

The ufw-docker rule looks at the container port, not the host port. That is why the panel's port 8000, which is 8080 in the container, does not open with ufw route allow on 8000. The rules below are the ones I tested. 22 stays on ufw allow, because SSH is not a container port.

sudo ufw route allow proto tcp from any to any port 80
sudo ufw route allow proto tcp from any to any port 443
sudo ufw route allow proto tcp from any to any port 8080
sudo ufw route allow proto tcp from any to any port 6001
sudo ufw route allow proto tcp from any to any port 6002
sudo ufw status numbered
Enter fullscreen mode Exit fullscreen mode

The test request left a network namespace with the address 203.0.113.10, outside the private ranges that ufw-docker lets through. Before the route rules, the panel on port 8000 and the proxy on 443 timed out. After:

  • http://203.0.113.1:8000/ answered HTTP/1.1 302 Found to /login.
  • http://203.0.113.1/ answered HTTP/1.1 503 Service Unavailable.
  • https://203.0.113.1/ answered HTTP/2 503.
  • http://203.0.113.1:6001/ and http://203.0.113.1:6002/ answered HTTP/1.1 404 Not Found. The 404 shows the port accepts a connection. It is not a panel page.

The 503 on ports 80 and 443 is the proxy with no domain configured. Port 8080, which Traefik also publishes, refused the connection in this test (curl: (7) Failed to connect), unlike 8000.

If the VPS has a firewall in the provider's panel, the Coolify docs say to use that firewall and allow only what the instance uses: 22/tcp, 80/tcp, 443/tcp and, while the panel is not on a domain, 8000/tcp, 6001/tcp and 6002/tcp. That firewall drops the packet before the server. ufw on its own does not.

Domain and HTTPS

Without a domain, the proxy listens on 443 with Traefik's default certificate. I checked from the server itself:

echo | openssl s_client -connect 127.0.0.1:443 -servername coolify.example.com 2>/dev/null | openssl x509 -noout -subject -issuer -dates
Enter fullscreen mode Exit fullscreen mode
subject=CN = TRAEFIK DEFAULT CERT
issuer=CN = TRAEFIK DEFAULT CERT
notBefore=Nov 18 10:11:11 2026 GMT
notAfter=Nov 18 10:11:11 2027 GMT
Enter fullscreen mode Exit fullscreen mode

Do not use that certificate for the panel. The DNS docs and the instance settings docs say the following, and this lab did not get to run it because there was no public name pointing at the machine:

  1. Create an A record from the hostname to the VPS public IPv4. If you will use IPv6 end to end, also create the AAAA.
  2. Wait until the name resolves to that address.
  3. In the panel, under Settings, enter the full URL starting with https://, for example https://coolify.example.com, and save.
  4. Coolify's proxy, which on this install is Traefik, issues the certificate when the name points at the server and ports 80 and 443 are reachable.

The docs warn that the URL cannot have a path (https://example.com/coolify does not work) and should not reuse an application's domain. With DNS validation on, Coolify checks the name first. Once the panel opens on the domain, the same firewall page says you can close public access to ports 8000, 6001 and 6002.

While the name does not exist, what can be confirmed is what this test saw: 80 and 443 up, 503, and Traefik's default certificate.

Keep the .env

The installer asks you to copy /data/coolify/source/.env off the server. That file has the APP_KEY and the database and Redis passwords. Without it, a database backup will not open again.

On this install the file existed, at 680 bytes, and the directory /data/coolify was mode 700, owner 9999. Check the mode and take a copy somewhere else. Do not paste the contents into a ticket, a chat or a repository.

sudo ls -ld /data/coolify /data/coolify/source
sudo ls -l /data/coolify/source/.env
Enter fullscreen mode Exit fullscreen mode

A copy that stays only on this disk is lost with the VPS. Keep the .env in a password manager or on another machine. Do not run a command that deletes /data/coolify to "reinstall clean" without that copy.

The instance stayed on the stable channel, with automatic updates on and the schedule 0 0 * * *. The panel can update itself. If there is a date when an update must not happen, read the release notes before relying on that.

Common problems

The root account form no longer opens

The installer says so at the time: the first account is only accepted in the 10 minutes after startup. Once that window passes, run sudo docker restart coolify and reload http://VPS_IP:8000. Create the account before you share the address.

Port 8000 does not open, or it opens to the whole internet

These are two different problems. If the provider's firewall does not allow 8000/tcp, the panel does not open from outside. If only ufw is active, the port Docker published stays open even with ufw deny 8000/tcp. The Docker port stays open with ufw shows both HTTP responses, before and after ufw-docker.

To open the panel with ufw-docker already installed, the rule is on the container port:

sudo ufw route allow proto tcp from any to any port 8080
Enter fullscreen mode Exit fullscreen mode

The proxy answers 503

That is what http://127.0.0.1/ and https://127.0.0.1/ answered before any domain: 503 Service Unavailable. The proxy is up and does not have anywhere to forward yet. The 503 goes away when an application, or the panel itself, gets a real hostname. It is not a lack of memory or a stopped container: sudo docker ps showed coolify-proxy healthy.

The certificate is Traefik's default

If the browser complains about the certificate and openssl shows CN = TRAEFIK DEFAULT CERT, the domain has not been saved on the instance yet, or the name does not point at this VPS. Go back to the domain section. Do not import that certificate as if it were the production one.

Next step

With the account created, the panel's onboarding asks for the server, Docker and the first project. The local server is already registered by this installer. From there Coolify publishes an application from Git, on the proxy that is already listening on 80 and 443.

The plan and what the order includes are at VPS for Coolify. If you are going to publish something else on the same Docker, without the panel, the Compose path is in How to install n8n with Docker on a VPS.


Originally published at https://nuvits.net/en/blog/install-coolify-ubuntu-vps

Top comments (0)