Self-host n8n on a VPS in one click

Why self-host n8n

n8n connects APIs, webhooks and databases. Size the VPS for concurrent workflows; data sent to external services follows those services’ terms.

Check required software features, resource usage and the current project license before choosing self-hosting.

Step 1 — One click at server creation

Create an account, Servers → New server: pick a region, an Ubuntu or Debian image, a small plan, and tick n8n in the one-click apps. First boot installs Docker and starts n8n in a container, published on port 80 with a persistent n8n_data volume for your workflows and credentials.

Step 2 — Create the owner account

Open http://<server-ip>/ — n8n asks you to create the owner account on first visit. Do it right away; until then, the setup screen is open to anyone who finds the IP. The post-install notes live on the server in /root/n8n-info.txt.

Step 3 — Put it behind HTTPS before real credentials

N8N_SECURE_COOKIE=true
N8N_PROTOCOL=https
WEBHOOK_URL=https://n8n.example.com/

Connect a domain and configure HTTPS before using real accounts or credentials. The application container and reverse proxy must use different host ports.

HTTPS also unlocks the practical stuff: webhook triggers from external services want a real, certificated URL.

Operating notes

• Workflows and credentials live in the n8n_data Docker volume — snapshot the server from the panel before upgrades.
• Update by pulling the new image and recreating the container; check n8n's release notes first, major versions occasionally migrate the database.
• docker logs n8n answers "why didn't my workflow run" more often than the editor does.