Skip to content
SkillModel-led3,386 tokens in use

n8n Self-Hosting

A guide for deploying production n8n on a fresh Linux server over SSH: Docker Compose behind Caddy with automatic HTTPS, single or queue mode, fresh secrets and Day-2 care.

6,686 stars on the repository MIT Licenseczlonkowski/n8n-skills · skills/n8n-self-hosting
/plugin install czlonkowski/n8n-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing n8n Self-Hosting costs

269tokens idle
3,386tokens in use
18,950tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: assets/init-data.sh.

Touches

shelldetectednetworkdetectedwrites filesdetectedcredentialsdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure19/25
  • Examples6/15
  • Output15/15
  • Size13/15
  • Resources13/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Fair
  • File that was not read−15

    a file the skill ships that was not read, so what it does is unknown

    assets/.env.queue.example
  • File that was not read−5

    a file the skill ships that was not read, so what it does is unknown

    assets/.env.single.example
  • File that was not read−5

    a file the skill ships that was not read, so what it does is unknown

    assets/Caddyfile
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    assets/init-data.sh, line 7
  • Reads credentials−15

    does this on the machine, and the frontmatter does not say so

    assets/init-data.sh, line 9

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity88
  • Maintenance92
  • Community60
  • Maturity36
  • Momentum40

n8n Self-Hosting is a skill for Claude that takes a fresh Debian or Ubuntu server to a running, HTTPS n8n over SSH. It asks first whether you want single mode (one n8n with SQLite) or queue mode (a main process, Redis, Postgres and workers), then collects the domain, TLS email, timezone and SSH details.

It follows a fixed flow: preflight checks for DNS and ports, Docker install, project files, fresh secrets generated on the server, firewall, launch and verification. It also covers task runners for Python Code nodes, managed OAuth credential overwrites, updates, backups and restores.

What You Get

  • A mode choice between single and queue, with the trade-offs and the RAM floor for queue
  • Docker Compose templates for each mode, a Caddyfile for automatic HTTPS and example environment files
  • A checklist that DNS points at the box and ports 80 and 443 are open before launch
  • Secret generation on the server, a rule to back up the encryption key off the box and a grep that catches leftover placeholders
  • Verification steps for health, certificate issue, public reachability and main and worker environment parity
  • Reference files for security hardening, queue mode, task runners, credential overwrites and Day-2 operations

Common Use Cases

  • Deploying n8n on a Hetzner, DigitalOcean or EC2 server with a domain and HTTPS
  • Moving from a single instance to queue mode with workers
  • Enabling Python Code nodes with a runners sidecar
  • Updating, backing up or restoring a self-hosted n8n
  • Setting up Sign in with Google without handing every user the OAuth client secret

What Makes It Unique

It covers the whole path from an empty server to a verified instance, including the early checks that catch a wrong A record or a closed cloud firewall. It treats the encryption key as the one secret that cannot be lost, tells Claude to claim the owner account before sharing the URL, and keeps queue workers and the main process on the same settings.

Under The Hood

The skill is instructions, six reference files and template assets. It has Claude connect to your server over SSH and run commands as root or a sudo user: it installs Docker with the official get.docker.com script, copies the compose, Caddy and environment files, generates secrets with openssl, edits the firewall with ufw, starts the stack with docker compose, and calls the health endpoints with curl. It writes files and changes server settings, and it fetches an installer script from the internet, so review each step against your server. One shipped shell script, init-data.sh, runs inside the Postgres container on first start in queue mode and creates the non-root database user from the password in your environment file. The Caddyfile and the example environment files are templates that hold placeholders and are filled in on the server.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers