How to Self-Host n8n on Hostinger (2026 Step-by-Step Guide)

If you want full control over your automations without paying per execution, self-hosting n8n on Hostinger is one of the most affordable, beginner-friendly ways to do it. A budget Hostinger VPS plus Docker gives you a private n8n instance for the price of a couple of coffees a month — and Hostinger even offers a one-click n8n template that does most of the setup for you.

This guide walks you through both paths (the one-click template and a manual Docker install), how to connect a domain with HTTPS, how to secure and back up your instance, and — importantly — how to update n8n on Hostinger when new versions ship. New to n8n entirely? Start with What is n8n? and the beginner's guide first, then come back here to deploy it.

Why self-host n8n on Hostinger?#

n8n is fair-code software you can run yourself for free — you only pay for the server. Hostinger is a popular choice because its KVM VPS plans are cheap, the control panel (hPanel) is beginner-friendly, and it ships a dedicated n8n application template.

The trade-off versus n8n Cloud is simple: self-hosting is cheaper at scale and gives you full data control, but you own updates, SSL, and backups. If that sounds fine, read on.

What you'll need#

• A Hostinger VPS plan (see the Hostinger tool page for plan guidance — KVM 2 with 8GB RAM is a comfortable sweet spot).
• A domain name you can point at the server (optional but strongly recommended for HTTPS).
• Basic comfort with SSH and the command line for the manual path. The one-click template needs far less.
• About 20–40 minutes.

Choosing a VPS plan#

n8n runs Node plus a database plus your workflows, so give it enough memory.

Path A: The one-click n8n template (easiest)#

Hostinger offers an n8n application template that provisions a VPS with n8n already installed via Docker. This is the fastest route and the one most beginners should take.

1. Buy a KVM VPS plan in your Hostinger account.
2. During setup (or later under VPS → Operating System / Applications), choose the n8n template instead of a bare OS.
3. Hostinger provisions the server and installs n8n automatically. Wait a few minutes for it to finish.
4. Open the access URL shown in hPanel (or your server IP on the n8n port) and complete the owner account setup in the n8n editor.
5. Add a domain and HTTPS (see the section below) so you're not running on a raw IP.

That's it for the easy path — skip to Add a domain and HTTPS. If you want full control over the configuration, use the manual Docker path next.

Path B: Manual install with Docker Compose#

This path gives you complete control and works on any Hostinger VPS running a plain Linux OS (Ubuntu LTS is a safe choice).

1. Connect to your VPS over SSH#

From your terminal, log in with the IP and root password from hPanel:

ssh root@YOUR_SERVER_IP

2. Install Docker and the Compose plugin#

On a fresh Ubuntu server, the official convenience script is the quickest way:

curl -fsSL https://get.docker.com | sh
docker --version
docker compose version

3. Create a Docker Compose file#

Make a folder for n8n and add a docker-compose.yml. This example runs n8n with a persistent volume and the critical encryption key set explicitly:

services:
  n8n:
    image: docker.n8n.io/n8nio/n8n
    restart: always
    ports:
      - "5678:5678"
    environment:
      - N8N_HOST=n8n.yourdomain.com
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - WEBHOOK_URL=https://n8n.yourdomain.com/
      - GENERIC_TIMEZONE=Europe/London
      - N8N_ENCRYPTION_KEY=replace-with-a-long-random-secret
    volumes:
      - n8n_data:/home/node/.n8n

volumes:
  n8n_data:

Generate a strong encryption key with openssl rand -hex 32 and paste it in.

4. Start n8n#

docker compose up -d
docker compose logs -f

n8n is now listening on port 5678. Don't expose it on a raw IP for long — add a domain and HTTPS next.

Add a domain and HTTPS#

Running n8n over plain HTTP on an IP is insecure and breaks some integrations (and OAuth logins). Put it behind a domain with a free SSL certificate.

1. In your DNS provider, create an A record pointing a subdomain (for example n8n.yourdomain.com) at your VPS IP.
2. Put a reverse proxy in front of n8n that handles HTTPS automatically. Popular options are Caddy (simplest — automatic Let's Encrypt) or Nginx Proxy Manager (a friendly web UI).
3. Point the proxy at localhost:5678 and let it issue the certificate.

How to update n8n on Hostinger#

n8n ships new versions frequently, with fixes, new nodes, and AI features. Keeping current is important — but don't update blindly: back up first (next section), and check the n8n release notes for any breaking changes.

Hostinger maintains an official, up-to-date walkthrough here: How to update n8n at Hostinger. Use it as the source of truth for your specific instance, because exact paths can differ between the template and a manual install.

Updating a Docker / template install via SSH#

Most Hostinger n8n setups run in Docker Compose, so the update is a two-command routine. Connect over SSH, change into the directory that holds your n8n docker-compose.yml (the template usually places it in a fixed folder — the Hostinger guide tells you exactly where), then:

# 1. Pull the latest n8n image
docker compose pull

# 2. Recreate the container with the new image
docker compose up -d

# 3. (Optional) remove the old, now-unused image
docker image prune -f

Your workflows and credentials are safe because they live in the persistent n8n_data volume, not in the container itself. Confirm the new version in the n8n editor (bottom of the left sidebar) or with:

docker compose logs -f

Pinning a specific version (optional)#

By default the compose file pulls latest. For predictable updates, pin a version tag and bump it deliberately:

    image: docker.n8n.io/n8nio/n8n:1.XX.X

Change the tag, then run docker compose pull and docker compose up -d again.

Securing and maintaining your instance#

Self-hosting means a few responsibilities are yours. None are hard, but skip them and you'll regret it:

• Firewall — allow only the ports you need (SSH and 80/443). Hostinger's panel and ufw both make this easy.
• SSH keys — disable password login and use key-based SSH.
• Enable HTTPS — never run n8n over plain HTTP in production.
• Keep the OS patched — run apt update && apt upgrade periodically.
• Set up basic auth or SSO if multiple people access the editor.

For a deeper look at connecting apps safely once you're running, see n8n credentials explained.

Back up your n8n data#

Two things must be backed up: your data volume (workflows, credentials, executions) and your encryption key.

# Snapshot the n8n data volume to a tarball
docker run --rm \
  -v n8n_data:/data \
  -v $(pwd):/backup \
  alpine tar czf /backup/n8n-backup-$(date +%F).tar.gz -C /data .

Even simpler: enable Hostinger's snapshots/automatic backups for the whole VPS so you can restore the entire server in one click. Store a copy of N8N_ENCRYPTION_KEY somewhere safe and separate.

Troubleshooting common issues#

• Can't reach the editor — check the firewall, that the container is running (docker compose ps), and that DNS has propagated.
• OAuth logins fail — n8n must be on HTTPS with the correct WEBHOOK_URL and N8N_HOST. Fix the domain/SSL setup first.
• Workflows lost after an update — almost always means the data volume wasn't persisted. Confirm the volumes: mapping in your compose file.
• Out of memory / sluggish — upgrade to a larger KVM plan; n8n wants 2GB+.

Is self-hosting right for you?#

If you value cost control and data ownership and don't mind a little maintenance, self-hosting on Hostinger is an excellent choice. If you'd rather never touch a server, n8n Cloud handles updates, SSL, and backups for you. There's no wrong answer — and migrating later is straightforward.

Compare the budget and developer-experience trade-offs on the Hostinger and DigitalOcean tool pages if you're still choosing a host.

Next steps#

You've got n8n running — now build something. Start with the beginner's guide, learn how webhooks and expressions work, then browse automation ideas for small businesses.