Self-Hosted n8n on Hostinger: A Step-by-Step Setup for Reliable Automations

Automation is no longer a “nice-to-have.” For operations, marketing, finance, HR, and analytics teams, automations are now a core capability to reduce manual work, improve turnaround time, and enforce process consistency. 

To learn about How to Build Agentic AI Automations without Coding, join Intellisoft’s 2 Day WSQ Funded course with upto 70% WSQ Funding.

n8n stands out because it gives you powerful workflow automation with the option to self-host, which means:

• You control your data and credentials

• You decide performance and scaling

• You can run unlimited workflows without per-task costs (within your server limits)

Self-hosting does add responsibility—security, updates, backups—but if you set it up properly, it becomes a dependable automation backbone.

This guide shows you how to host n8n successfully on Hostinger, using either Hostinger’s one-click template or a production-style Docker Compose deployment.

What is n8n (and why teams are adopting it)?

n8n is an open-source workflow automation platform that connects apps, databases, and APIs to create end-to-end automations—everything from lead capture → CRM updates → email notifications → reporting pipelines. Hostinger also describes n8n as an open-source automation tool, and provides deployment templates to simplify installation.

Why n8n often beats “basic” automation tools

• Self-hosting for privacy and control (especially if you handle customer data)

• Advanced workflows: branching, error handling, retries, scheduling, and complex logic

• Extensibility: connect to almost anything via HTTP/API nodes

• Cost control: pay for a VPS instead of per-task automation pricing

Recommended: If you want a reliable VPS option for self-hosting n8n, check out my Hostinger-ready recommendation here:

Host n8n on Hostinger (Recommended Setup)

Practical n8n automations (high-ROI use cases)

If you’re new to n8n, here are workflows that typically deliver immediate value:

1. Lead capture to CRM

   • Web form → validate → deduplicate → insert/update MySQL/CRM → notify sales

2. Customer onboarding

   • New signup → create folders → generate welcome email → add to mailing list → assign tasks

3. Operations approvals

   • Request form → manager approval → create ticket → update status → audit log

4. Finance automation

   • Invoice data capture → approvals → generate PDF → send → store in Drive/S3

5. Reporting pipelines

   • Pull data nightly → transform → load into Sheets/DB → Slack summary

n8n hosting options: Cloud vs self-hosted

n8n can be run as a managed service or self-hosted. The official n8n hosting docs highlight that self-hosting requires technical knowledge around servers, containers, security, and configuration.

Quick comparison

n8n Cloud

• Faster setup

• Less infrastructure work

• Higher recurring cost at scale (depending on usage)

Self-hosted n8n

• More control and privacy

• Usually cheaper long-term

• You own uptime, security, updates, and backups

If your workflows touch customer data, internal DBs, or proprietary processes, self-hosting is often the better operational decision.

Why Hostinger is a strong choice for hosting n8n

Hostinger is attractive for n8n hosting because it supports:

• VPS hosting with root access

• Docker-friendly deployment

• A ready-made n8n VPS template for faster setup

• Practical documentation on Docker installation and n8n deployment

Pre-flight checklist (before you install n8n)

1) VPS sizing

Hostinger’s guidance for n8n VPS requirements cites minimums like 1 vCPU, 2 GB RAM, and 20 GB SSD, and recommends higher specs for better performance/scalability.

A practical starting point for business use is typically 2 vCPU / 4 GB RAM, especially if you plan to run multiple workflows frequently.

2) Domain planning

Decide whether you’ll access n8n as:

• n8n.yourdomain.com (recommended), or

• via server IP (not recommended for production)

3) Security basics

Plan for:

• Firewall rules (only open what you need)

• Strong passwords / SSH keys

• SSL termination (HTTPS)

Recommended: If you want a reliable VPS option for self-hosting n8n, check out my Hostinger-ready recommendation here:

Host n8n on Hostinger (Recommended Setup)

Option A: Install n8n using Hostinger’s VPS template (fastest path)

Hostinger offers an “Ubuntu 24.04 with n8n” VPS template where n8n comes preinstalled inside Docker, designed for quick deployment.

High-level steps:

1. Provision a Hostinger VPS and choose the Ubuntu 24.04 with n8n template

2. Connect to the server via SSH

3. Validate the container is running

4. Configure domain + SSL (recommended)

5. Set key environment variables (Base URL, encryption key, etc.)

This is ideal if you want a working deployment quickly and prefer a guided template.

Option B: Manual production-style install on Hostinger VPS (Docker Compose)

For long-term stability, Docker Compose is a widely recommended approach because it standardizes config, persistence, restart policies, and upgrades. n8n’s docs provide official Docker and Docker Compose guidance.

Step 1 — Install Docker (Hostinger VPS)

Hostinger provides a step-by-step guide to install Docker on Ubuntu (manual method or using their VPS template).

Step 2 — Create persistent folders

You want n8n data to survive restarts and upgrades (volumes).

Step 3 — Create a Docker Compose file (example)

Below is a practical baseline. You can adapt it based on whether you use SQLite (simple) or PostgreSQL (recommended for serious usage).

Notes:

• n8n documents many configuration options via environment variables (including deployment-related settings).

• For heavier workloads, use PostgreSQL and consider queue mode (more on that below).

Secure access: domain + SSL + reverse proxy

In production, you typically:

• Run n8n on an internal port

• Put a reverse proxy (Nginx/Caddy) in front

• Terminate SSL (HTTPS)

• Set correct webhook URLs

Hostinger’s n8n Docker guide includes a step specifically about securing n8n with SSL and an NGINX reverse proxy.

n8n’s docs also cover configuring webhook URLs behind a reverse proxy.

This prevents common webhook failures and avoids sending credentials over plain HTTP.

Critical n8n settings (don’t skip these)

1) Set a strong encryption key

n8n uses encryption for stored credentials. In self-hosted production, you should set a stable encryption key via environment variables. n8n’s environment variable documentation covers configuration through env vars and deployment settings.

2) Set Base URL and WEBHOOK_URL correctly

If these are wrong, you’ll see issues like:

• OAuth callback failures

• Webhooks not firing correctly

• Redirect loops after login

3) Backups (minimum viable approach)

At minimum:

• Backup your n8n volume (.n8n) or your named Docker volume

• If using PostgreSQL, backup the DB too

• Keep off-server copies (object storage or another server)

Operations: updates, backups, monitoring, and scaling

Updating n8n safely

n8n provides specific guidance on updating self-hosted deployments.

For Docker Compose, a typical update flow is:

• pull the latest image

• restart the container

• verify workflows

Scaling: when to consider queue mode

If you run high volume automations (frequent schedules, heavy API usage, lots of concurrent executions), you’ll eventually want:

• PostgreSQL

• queue mode execution model

• worker scaling

Hostinger explicitly mentions templates that support queue mode for better scalability.

Common issues & quick troubleshooting

1. Webhooks don’t trigger

   • Usually WEBHOOK_URL or reverse proxy config is wrong

2. OAuth errors

   • Base URL mismatch or wrong redirect URL

3. Server feels slow

   • Under-sized VPS, too many concurrent executions, no queue mode

4. Credentials broke after reinstall

   • Changed encryption key; keep it stable across restarts

Recommended For Your n8n AUtomation.

Because you asked to promote your affiliate URL, here are blog-safe placements (top, mid, and end). Since many CMS editors prefer clickable buttons/links, use this HTML snippet:

FAQ (for SEO + Featured Snippets)

Is n8n free to self-host?

Yes. Self-hosting n8n is commonly done via Docker/Docker Compose, but you manage the infrastructure and maintenance.

What VPS size do I need for n8n?

A practical baseline is at least 1 vCPU, 2 GB RAM, 20 GB SSD, with 2+ vCPU and 4+ GB RAM recommended for better performance.

What’s the best way to host n8n on a VPS?

Docker Compose is a standard approach for stable configuration, storage persistence, and repeatable upgrades. n8n provides official Docker/Docker Compose documentation.

Do I need SSL for n8n?

If you access n8n over the public internet or use webhooks and OAuth, HTTPS is strongly recommended. Hostinger’s n8n Docker guide includes a step for SSL with a reverse proxy.