Engineering notes
Run Coolify on a UK VPS: size, install, lock down and back up
How to run Coolify on a VPS. The hardware it asks for, which server size fits, the official installer on Ubuntu 24.04 or Debian 12, the ports to open and close, root SSH, and backups, from Coolify's own docs.
Coolify is a self-hosted platform for deploying applications, databases and services on your own servers. You point it at a Git repository or a Docker image, and it builds, runs and puts HTTPS in front of the result through its own proxy. It suits someone who wants the push-to-deploy workflow of a hosted platform but would rather pay for one server than per app.
This guide covers sizing, installing Coolify with its official installer, closing the ports you no longer need, and backing it up. The commands follow Coolify's documentation as we read it on 18 November 2026. We have not run this exact sequence on a Vozora server, so read each step against the linked page before you run it, in case it has changed since.
What it needs
Coolify's install page is direct about the floor: "Coolify needs 2 CPU cores, 2 GB RAM, and 10 GB disk space to run." The disk figure is free space, and the same page says to keep more for "Docker images, volumes, and backups". It adds that Coolify "can run on smaller servers (for example: 1 CPU core, 512 MB RAM, 4 GB disk), but this is not recommended", and warns that if you build applications on the same server as Coolify, high resource use "could make your server unresponsive" (Coolify docs, start with self-hosted, checked 2026-11-18).
Supported systems include Debian and Ubuntu. For Ubuntu the page says to "use an LTS release such as 20.04, 22.04, or 24.04", and it recommends a fresh server so Coolify does not clash with anything already installed.
Which Vozora size
- Small (2 vCPU, 4 GB RAM, 60 GB disk) is the smallest Vozora size that meets Coolify's stated minimum, with room for a few small applications and a database. This is where to start.
- Medium (4 vCPU, 8 GB, 120 GB) if Coolify builds your applications on the same server. Builds are the heavy part: compiling a Node or Rust project uses far more CPU and memory than running it.
- Nano has 1 vCPU, below Coolify's minimum. Don't use it for Coolify itself.
Current specifications and rates are on the pricing page. An hourly server can be resized to a larger size while it is stopped, but not to a smaller one, so start on Small and move up when you have measured the need. Our RAM sizing guide covers how to measure.
Pick Ubuntu 24.04 or Debian 12 when you create the server, and add your SSH key.
Before you install: root SSH
Coolify manages servers over SSH, including the one it runs on. The installer creates a key, adds it to the SSH authorized_keys of the user running it, and Coolify then connects back to the host as that user. With the automated installer, that user is root: the page lists "Use root user account" and "Requires root user access" for this method.
On Vozora you log in as the image's user (ubuntu or debian) with your SSH key and use sudo; direct root login is not how you connect. So check what the SSH server will allow for root before installing:
sudo sshd -T | grep -i permitrootlogin
The installer runs the same check and warns if root login is off. If the answer is no, Coolify's OpenSSH page gives the setting to use: PermitRootLogin prohibit-password, which "allows root to connect with an SSH key but prevents password-based SSH login" (Coolify docs, OpenSSH, checked 2026-11-18). Change it in /etc/ssh/sshd_config, then:
sudo sshd -t # prints nothing if the config is valid
sudo systemctl restart ssh # the unit is "ssh" on Ubuntu and Debian
Keep your current session open while you do this. If something goes wrong, the server's browser console in the Vozora dashboard still works. Root can then log in only with a key, and the only key for root that matters is the one Coolify adds. Restricting SSH to your own address in the Vozora firewall, below, narrows it further.
Install
Coolify's installer must run as root ("Please run this script as root or with sudo" is the first thing it checks). Become root with a login shell, so the key lands in root's home, then run the command exactly as the docs give it:
sudo -i
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash
The script installs the packages it needs and Docker Engine, sets up /data/coolify, and creates the SSH key for the localhost connection. If you would rather read it first, download it with curl -fsSL https://cdn.coollabs.io/coolify/install.sh -o install.sh, read it, then run bash install.sh. It is a long script, and it changes a lot.
When it finishes it prints the dashboard address, http://<your-server-ip>:8000.
Create the admin account straight away. Coolify's docs: "Anyone who reaches the registration page first can become the instance admin and gain root access to your server." It also says "Coolify accepts the first account only in the first 10 minutes after Coolify starts"; if you miss that window, run docker restart coolify and reload the page.
Save the installation secrets. The docs say to back up /data/coolify/source/.env, which holds APP_KEY, "used to encrypt Coolify database values. You need this file if you ever want to restore Coolify from a backup." Copy that line into a password manager now:
grep '^APP_KEY=' /data/coolify/source/.env
Ports and firewalls
Coolify's firewall page lists what the Coolify server uses (Coolify docs, firewall, checked 2026-11-18):
| Port | Used for |
|---|---|
| 8000/tcp | The dashboard at http://<server-ip>:8000 |
| 6001/tcp | Real-time dashboard updates when using the IP address |
| 6002/tcp | The web terminal when using the IP address |
| 22/tcp | SSH |
| 80/tcp | HTTP and certificate issuing through the Coolify proxy |
| 443/tcp | HTTPS through the Coolify proxy |
The page recommends the hosting provider's firewall where there is one, "because it blocks unwanted traffic before the traffic reaches your server". That matters more than usual here. Coolify runs everything in Docker, and Docker's documentation says traffic to published container ports "gets diverted before it goes through the ufw firewall settings" (Docker docs, packet filtering and firewalls, checked 2026-11-18). A host firewall such as ufw does not protect Coolify's ports on its own.
On Vozora, use a firewall in the dashboard. The default firewall every server starts in allows all traffic, so either edit its rules or create one for this server. A sensible set while you set up:
- TCP 22 from your own address only, for example
203.0.113.7/32. - TCP 8000, 6001 and 6002 from your own address only.
- TCP 80 and 443 from
0.0.0.0/0, and from::/0if your applications will answer on IPv6.
IPv4 and IPv6 rules are separate on Vozora, so a rule for 0.0.0.0/0 does not open IPv6.
Then put the dashboard behind HTTPS and close 8000, 6001 and 6002. The dashboard on port 8000 is plain HTTP. Point a name such as coolify.example.com at the server (Vozora hosts DNS free if you want it there), set it as the dashboard's domain in Coolify's settings, and once it loads over HTTPS, remove the rules for the three dashboard ports. Coolify's firewall page says that after the dashboard works through a domain, "you can close public access to ports 8000, 6001, and 6002."
Your applications get HTTPS the same way: give each one a domain in Coolify, point its DNS at the server, and Coolify's proxy requests the certificate over ports 80 and 443.
Backups
There are three separate things to protect, and Coolify only handles some of them.
Coolify's own data. Under Settings, then Backup, Coolify can back up its own database on a schedule, by default "one backup each day at midnight in the instance timezone", and copy it to S3-compatible storage. That backup "does not back up data stored inside your applications, databases, or volumes", and it does not include APP_KEY: "Without this key, restored secrets cannot be read" (Coolify docs, back up Coolify, checked 2026-11-18). The same page says: "Do not keep the only copy on the Coolify server."
Your databases. Each database Coolify deploys has a Backups tab with its own schedule, and can send copies to S3-compatible, SFTP, FTPS or WebDAV storage. Coolify's database backup page adds the caveat that "A successful backup only proves that Coolify created a file", and says to restore a copy into a disposable database before trusting it (Coolify docs, database backups, checked 2026-11-18).
The whole server. Vozora backups copy the server's disk: turn on daily backups (taken each night, newest 7 kept), and take one on demand with Back up now before you upgrade Coolify. Restoring puts the whole disk back as it was. These backups are stored on the same platform as the server, so they protect against a bad upgrade or a deleted directory, not against losing the account or the platform. Keep at least the Coolify backup, your database dumps and APP_KEY somewhere off the server as well. Our self-hosting guide sets up restic for that.
Short version
- Small or larger; Medium if Coolify builds on the same server.
- Check
PermitRootLogin; setprohibit-passwordif it isno. sudo -i, then run the installer from Coolify's docs.- Create the admin account within 10 minutes, and save
APP_KEYsomewhere else. - Vozora firewall: SSH and the dashboard ports from your address only, 80 and 443 open.
- Give the dashboard a domain, then close 8000, 6001 and 6002.
- Coolify instance backup, database backups and a Vozora disk backup, with copies off the server.
A Vozora server is billed by the minute from prepaid credit while it exists, including while it is stopped, so delete test servers when you are done. Sizes and current prices are on the pricing page. For the other jobs on a self-hosted server, see our self-hosting on a VPS guide and the new VPS checklist; for running n8n by itself rather than under Coolify, see n8n on a UK VPS.