Page type

self hosting

15 candidate pages in this template family.

self-hosted

N8N Backup and Restore Guide

Back up the active database, n8n user data, encryption key, and any external binary storage before upgrades or infrastructure changes.

n8n backup restore
self-hosted Docker Compose

n8n Docker Compose Setup for Self-Hosting: Volume, .env, Postgres, and Webhooks

Build a safer n8n Docker Compose setup with persistent storage, private env files, Postgres planning, public webhook URLs, HTTPS, and backup checks.

n8n docker compose
self-hosted Docker

n8n Docker Installation: Persistent Volume, Timezone, and Production Readiness

Install n8n with Docker while keeping /home/node/.n8n persistent, aligning timezone settings, and preparing for HTTPS, backups, and public webhooks.

n8n docker installation
Docker self-hosted

n8n Docker Volume Persistence: Avoid Losing Workflows and Credentials

Fix n8n Docker persistence by mounting /home/node/.n8n, protecting SQLite data, preserving community nodes, and testing container recreation.

n8n docker volume persistence
self-hosted

n8n Postgres Setup: Environment Variables, Permissions, and Queue Mode Readiness

Configure n8n with Postgres using DB_TYPE and DB_POSTGRESDB variables, database permissions, Docker networking, backups, and queue mode planning.

n8n postgres setup
self-hosted

N8N Upgrade Guide

Update self-hosted n8n regularly, check release notes for breaking changes, and test important upgrades in a separate environment before touching production.

n8n upgrade guide
self-hosted

N8N VPS Hosting Guide

A VPS is a good starting point for self-hosted n8n when it has enough memory, persistent storage, backups, public HTTPS, and room to move to Postgres or queue mode later.

n8n vps hosting
self-hosted

N8N Community Nodes Security Risks

Community nodes can extend n8n, but they install third-party npm code into your instance, so production systems should treat them as supply-chain and runtime risk.

n8n community nodes risks
self-hosted

N8N Configuration Methods

Self-hosted n8n can be configured with environment variables, a configuration file, or the database, and environment variables are usually the clearest option for container deployments.

n8n configuration methods
self-hosted and cloud

N8N Custom Domain Setup

A custom domain for self-hosted n8n needs DNS, reverse proxy routing, HTTPS, and endpoint environment variables that make editor and webhook URLs use the same public host.

n8n custom domain
Docker Compose

N8N Docker Compose .env File

A Docker Compose env file keeps n8n deployment settings separate from the Compose service definition and makes it easier to avoid committing secrets.

n8n docker compose env file
self-hosted

n8n Queue Mode Setup: Redis, Postgres, Workers, and Encryption Key Checklist

Set up n8n queue mode with Redis, Postgres, worker processes, shared N8N_ENCRYPTION_KEY, version parity, and binary data cautions.

n8n queue mode setup
self-hosted

N8N Redis Setup

Redis is the message broker for n8n queue mode; the main process pushes execution IDs to Redis and workers pick them up for processing.

n8n redis setup
self-hosted

N8N Reverse Proxy Setup

When n8n runs behind a reverse proxy, configure the public host, protocol, and webhook base URL so editor links and incoming webhook URLs match the external domain.

n8n reverse proxy
self-hosted

N8N SSL Setup

For public n8n deployments, use HTTPS either through a reverse proxy or n8n's SSL settings, then make sure generated editor and webhook URLs also use HTTPS.

n8n ssl setup