n8n
How to Fix n8n Workflows That Stopped Working After an Update
n8n workflows broke after updating? Fix the six real causes: failed migrations, lost keys, renamed variables, removed nodes, and broken webhooks.
n8n workflows broke after updating? Fix the six real causes: failed migrations, lost keys, renamed variables, removed nodes, and broken webhooks.
Migrate n8n from npm to Docker before n8n 3.0 drops npm support. Back up ~/.n8n, protect the encryption key, and boot a pinned 2.x image first.
Upgrading to n8n 3.0? This checklist covers every breaking change: Docker-only deployment, 35+ removed nodes, security defaults, and a staged upgrade path.
Update self-hosted n8n safely: Docker Compose, Docker, and npm upgrade paths with backups, database migrations, rollback steps, and five real fixes.