Install n8n on a VPS (Docker + SSL)

Why Self-Host n8n (vs n8n.cloud Pricing)

Four steps, one evening:

1. VPS prep — fresh Ubuntu, Docker and the Compose plugin installed, UFW allowing 22/80/443 only.
2. Run n8n — create /opt/n8n/docker-compose.yml with image n8nio/n8n:latest, restart: unless-stopped, port bound to 127.0.0.1:5678, a persistent volume for /home/node/.n8n, and WEBHOOK_URL set to your domain.
3. Domain, Nginx and SSL — server block proxying to 127.0.0.1:5678, then certbot --nginx for HTTPS (webhooks require valid TLS).
4. Secure — strong owner credentials, database persistence, scheduled backups of the volume.

Self-hosting beats n8n.cloud's execution-based pricing for chatty workflows: your VPS counts runs, not executions.

Step 1: VPS Prep (Docker, UFW)

VPS Prep (Docker, UFW). Do this on one site or a staging copy first, then check the public URL in a private window so cache does not hide the result. Stop if the page errors, and email support@webji.services with the step name and the exact error before you repeat it on every account. WebJi® support mail is staffed 24/7 in Hindi and English; the phone line +91 141 4941811 is business hours only.

Step 2: Run n8n With Docker Compose

Two practical notes on workflow automation: it interacts directly with caching and database response, and misconfiguration is the most common cause of 'hosting is slow' tickets. WebJi® support checks it as part of standard migrations.

Step 3: Domain, Nginx and SSL

On Docker Compose install, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Securing: Basic Auth, Backups, Updates

How this plays out with webhook URLs: settings that look cosmetic usually decide page speed and uptime under real traffic. The defaults WebJi® ships are tuned for Indian network conditions, and support can review your setup on request.

VPS Cost in India (INR)

The cost frame and scaling path:

A 2 GB VPS comfortably runs n8n with dozens of active workflows; the 8 GB cloud tier runs n8n alongside websites and other containers. Scale to queue mode when executions pile up concurrently — workers plus Redis split the load. Either way the monthly bill is flat, which is the whole argument against per-execution cloud pricing.