1. Make an SSH key
Your server has no password login. You log in with an SSH key, which is a pair of files: a private key that stays on your computer, and a public key you give us. If you already have one, skip to step 2.
On macOS, Linux, or Windows 10 and later (PowerShell), run:
ssh-keygen -t ed25519 -C "[email protected]"
Press Enter to accept the default file, and choose a passphrase. Then print the public key:
cat ~/.ssh/id_ed25519.pub
Copy the whole line that starts with ssh-ed25519 and paste it when you create your server. Never share the file without .pub.
2. Log in
When your server is ready, its IP address shows in the dashboard. Log in as root:
ssh [email protected]
The first time, SSH asks you to confirm the server's fingerprint. Type yes.
3a. Ubuntu: first steps
Bring the system up to date, then turn on the firewall and allow SSH so you don't lock yourself out:
apt update && apt upgrade -y
ufw allow OpenSSH
ufw enable
If you'll serve websites, allow HTTP and HTTPS too: ufw allow 80,443/tcp. Many people also create a normal user with sudo rights and log in as that user day to day.
3b. Docker Compose: run your app
Docker Engine and Compose are already installed. Copy your project over and start it:
scp -r ./myapp [email protected]:/root/
ssh [email protected]
cd myapp && docker compose up -d
docker compose ps
To serve it on your domain with HTTPS, add Caddy to your compose.yaml:
services:
caddy:
image: caddy:2
ports: ["80:80", "443:443"]
volumes:
- ./Caddyfile:/etc/caddy/Caddyfile
- caddy_data:/data
web:
build: .
volumes:
caddy_data:
And a Caddyfile next to it, with your domain and the port your app listens on:
example.com {
reverse_proxy web:3000
}
Caddy gets the certificate on its own once your domain points at the server (step 4). Keep databases off the public internet: don't publish their ports, and let your app reach them over the Compose network.
3c. Coolify: finish setup
Coolify is already running. Open this address in your browser straight away:
http://203.0.113.24:8000
Then connect GitHub, add your app, and set your domain in Coolify's settings. Coolify sets up HTTPS for domains that point at the server. Its own documentation lives at coolify.io/docs.
4. Point your domain
At your DNS provider, add an A record for your domain with your server's IP address as the value. Changes usually show up within minutes, sometimes longer. Check with:
dig +short example.com
When it prints your server's IP, HTTPS will work.