n8n - 💡(How to fix) Fix Community nodes not installed on all workers

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Bug Description

In self hosted mode, with two workers, installing a community node with the settings GUI only works for one worker. The other worker does not have the npm package installed. This means that at execution, the node will fail if executed on the wrong worker.

To Reproduce

  1. install n8n with 2 workers on kubernetes
  2. install a community node with the GUI (settings/...): for example n8n-nodes-cron-parser
  3. go to all workers with a kubctl exec
  4. verify that second worker does not have the package installed

Expected behavior

The npm package should be installed on ALL workers.

Debug Info

n8n-nodes-cron-parser not found or like...

Operating System

Ubuntu 5.15.0-177-generic

n8n Version

2.17.8

Node.js Version

11.12.1

Database

PostgreSQL

Execution mode

queue

Hosting

self hosted

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The npm package should be installed on ALL workers.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Community nodes not installed on all workers