Install n8n on Vultr: Self-Host Your AI Automation in 3 Steps
To install n8n on Vultr, you run n8n with Docker Compose on an Ubuntu 24.04 server, put Nginx in front as a reverse proxy, and secure it with a Let’s Encrypt certificate from Certbot. That is the setup in Vultr’s own guide, last updated on September 11, 2026. You get your own n8n editor on your own domain, with HTTPS webhooks, instead of renting n8n Cloud. This article is based on Vultr’s and n8n’s documentation; we have not run this setup ourselves.
This is an affiliate link: it costs you nothing extra, and we may earn a commission.

Key Takeaways
- What you need: an Ubuntu 24.04 server, a non-root user with sudo, and a domain A record pointing at the server’s IP.
- Three steps: Docker and Docker Compose, then Nginx as a reverse proxy, then a TLS certificate from Certbot that renews automatically.
- Port: n8n listens on 5678; Nginx forwards your domain to it.
- Updating: two commands,
docker compose pullanddocker compose up -d. - Cost of the software: without a license key, self-hosted n8n runs as the free Community edition, according to n8n’s docs.
- Server price: Vultr’s cheapest plan available in Singapore is $5 a month (1 vCPU, 1 GB RAM), per Vultr’s public plan list on November 7, 2026.
Watch: a 30-second video summary.
Why self-host n8n instead of using n8n Cloud?
n8n is an open-source workflow automation tool. You connect apps and AI models with visual nodes, and it runs the steps for you: read an email, send it to a language model, post the answer to a chat app. n8n offers a hosted version (n8n Cloud) and a self-hosted one that, according to n8n, uses the same core product.
When you install n8n on Vultr, you rent the server and own everything on it: workflows, credentials and execution history stay on your disk. n8n’s docs say a self-hosted install without a license key runs as the free Community edition; Business and Enterprise license keys unlock those editions. The trade-off is that updates, backups and security are your job.
What do you need before you install n8n on Vultr?
Vultr’s guide lists only two prerequisites:
- An Ubuntu 24.04 server, accessed as a non-root user with sudo rights.
- A domain (for example
n8n.example.com) with an A record pointing to the server’s public IP.
The guide does not state a minimum RAM or CPU, and we have not measured how much memory n8n uses. Here are the cheapest Vultr Cloud Compute plans from Vultr’s public plan list (api.vultr.com/v2/plans), prices as of November 7, 2026:
| Plan | vCPU | RAM | SSD | Bandwidth | Monthly | Hourly | Singapore |
|---|---|---|---|---|---|---|---|
| IPv6 only | 1 | 512 MB | 10 GB | 0.5 TB | $2.50 | $0.003 | No |
| 1 GB | 1 | 1 GB | 25 GB | 1 TB | $5 | $0.007 | Yes |
| 2 GB | 1 | 2 GB | 55 GB | 2 TB | $10 | $0.014 | Yes |
| 2 vCPU / 2 GB | 2 | 2 GB | 65 GB | 3 TB | $15 | $0.021 | Yes |
| 4 GB | 2 | 4 GB | 80 GB | 3 TB | $20 | $0.027 | Yes |
If you install n8n on Vultr for testing only, you can also bill by the hour. Vultr’s pricing page blocked our reader, so these numbers come from the plan API. Check the price in the Vultr dashboard before you deploy. For the full breakdown, see our Vultr pricing 2026 guide.
How to install n8n on Vultr, step by step
Below are the steps to install n8n on Vultr from Vultr’s guide, in order. Replace n8n.example.com with your domain everywhere. No step needs a paid n8n plan; the only paid part is the VPS.
Step 1: Install Docker and create the n8n folders
Install Docker Engine, the CLI and the Compose plugin from Docker’s official repository:
sudo apt update
sudo apt install apt-transport-https ca-certificates curl software-properties-common -y
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-compose-plugin -y
sudo usermod -aG docker $USER
newgrp docker
docker --version
Then create the folders. The n8n container runs as user ID 1000, so the data folders must belong to that ID:
mkdir ~/n8n && cd ~/n8n
mkdir n8n-data local-files
sudo chown -R 1000:1000 n8n-data local-files
Step 2: Write docker-compose.yml and set up Nginx
Create ~/n8n/docker-compose.yml:
services:
n8n:
image: n8nio/n8n:latest
container_name: n8n
restart: unless-stopped
ports:
- "5678:5678"
environment:
- N8N_HOST=n8n.example.com
- N8N_PORT=5678
- N8N_PROTOCOL=https
- WEBHOOK_URL=https://n8n.example.com
- N8N_EDITOR_BASE_URL=https://n8n.example.com
- GENERIC_TIMEZONE=UTC
- N8N_USER_FOLDER=/home/node/.n8n
volumes:
- ./n8n-data:/home/node/.n8n
- ./local-files:/files
networks:
- n8n-network
networks:
n8n-network:
driver: bridge
WEBHOOK_URL matters: it is the public address that outside services call to trigger your workflows. If you are in Vietnam, you can set GENERIC_TIMEZONE=Asia/Ho_Chi_Minh; n8n’s docs say this variable controls the timezone for schedule nodes such as Schedule Trigger.
Install Nginx (sudo apt install nginx -y) and create /etc/nginx/sites-available/n8n.example.com:
server {
listen 80;
server_name n8n.example.com;
location / {
proxy_pass http://localhost:5678;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Port $server_port;
proxy_buffering off;
proxy_read_timeout 300s;
proxy_connect_timeout 75s;
}
}
The WebSocket headers keep the editor updating live, and the 300-second read timeout gives long workflows room to finish. Enable the site and open the firewall:
sudo ln -s /etc/nginx/sites-available/n8n.example.com /etc/nginx/sites-enabled/
sudo nginx -t
sudo systemctl reload nginx
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
Step 3: Get HTTPS with Certbot, then start n8n
sudo apt install certbot python3-certbot-nginx -y
sudo certbot --nginx -d n8n.example.com --email admin@example.com --agree-tos --non-interactive
sudo certbot renew --dry-run
Certbot edits the Nginx config for TLS and sets up automatic renewal. A successful dry run means renewal works. Now start n8n:
cd ~/n8n
docker compose up -d
docker compose ps
docker logs n8n
When the log shows n8n ready on https://n8n.example.com, open your domain, create the admin account (email, name, password) and you are in the workflow editor. The Templates section is a quick way to find a first workflow.
No Vultr account yet? Create one before Step 1: Try Vultr.
How do you update and look after n8n?
Vultr’s guide gives these commands:
- Live logs:
docker logs -f n8n - Stop:
docker compose down - Restart:
docker compose restart - Update:
docker compose pull, thendocker compose up -d
n8n’s own advice is to update at least once a month so you never jump many versions at once, and to read the release notes for breaking changes first. The current stable release listed in n8n’s Docker docs is 2.46.6. Because the compose file uses the latest tag, every pull moves you to the newest stable version.
By default n8n stores workflows, credentials and past executions in SQLite inside the .n8n folder (here, n8n-data). n8n’s docs say that folder also holds encryption keys, so back it up. For heavier use, n8n supports PostgreSQL.
Is it worth it to install n8n on Vultr?
Pros: the software is free in the Community edition, your data stays on your server, and the whole setup is standard tools (Docker, Nginx, Certbot) with plenty of documentation. Updates take two commands, and the docs to install n8n on Vultr are short and clear.
Cons: you need a domain and some comfort with the Linux command line. Vultr’s guide skips a few things: it never runs ufw enable or adds an SSH rule, and the compose file publishes port 5678 on all interfaces even though Nginx only needs localhost:5678. If you want n8n reachable only through Nginx, you can change the port line to "127.0.0.1:5678:5678". The guide also has no backup step and no minimum hardware spec.
Our take: install n8n on Vultr if you will run workflows every day, want webhooks on your own domain, and are fine owning updates and backups. If you just want to try n8n for an afternoon, n8n’s local Docker setup on your own computer costs nothing, and you can move to a VPS later. Don’t rent a server if nobody on your team will patch it once a month.
If you plan to add a local model, our guides to an n8n and Ollama email workflow and an n8n and Ollama RAG chatbot build on this setup. For a broader look at the host, read our Vultr review.
Install n8n on Vultr FAQ
Is self-hosted n8n free?
According to n8n’s docs, a self-hosted install without a license key runs as the free Community edition. You still pay for the server.
Which Vultr plan should I pick for n8n?
Vultr’s guide to install n8n on Vultr does not give a minimum spec. The cheapest plan available in Singapore is $5 a month with 1 GB RAM (as of November 7, 2026); a 2 GB plan is $10.
Do I need a domain?
Yes, in this setup. Certbot needs a domain A record pointing at your server to issue the HTTPS certificate.
Which port does n8n use?
Port 5678. Nginx receives traffic on 80 and 443 and forwards it to localhost:5678.
How do I update n8n?
Run docker compose pull and then docker compose up -d in the ~/n8n folder. n8n suggests updating at least monthly.
Sources
- Vultr Docs, “How to Install n8n on Ubuntu 24.04”
- Vultr API, “List Plans”
- n8n Docs, “Self-hosting n8n”
- n8n Docs, “Docker installation”
- n8n Docs, “Updating”
Last updated: November 7, 2026