▶️ n8n 3.0 Kills NPM Install

If you installed n8n with npm install -g n8n, that install route goes away in 3.0. Your install keeps running today. It just can't upgrade past that point.

Copy the .n8n folder into a Docker volume. The encryption key rides along inside it, so every credential still opens.
Skip export and import. It reports success, and then every credential is dead because the new instance encrypts with a different key.
Run the last version 1 release once before going to version 2. Straight to 2 and the workflow list comes up empty with no error.
Pin the image tag and set your timezone in the compose file. Schedules run on the container's clock.
The old folder is never touched, so starting the npm install again puts you right back where you began.

Docker Desktop on a Mac or Windows machine you sit at, Docker Engine and Compose on a headless server. Same container either way. The compose file is in the video description.

Any questions? Let me know.

Cheers,

Kawika

0 comments

▶️ n8n 3.0 Kills NPM Install

Self-Host Hub

skool.com/selfhosthub

Build automation infrastructure you own. Self-hosted workflows for images, video, and voice, running on your machine, where a retry costs nothing.

Leaderboard (30-day)