starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 15 Packages Projects Releases 10 Wiki Activity

can not update n8n #1621

New Issue
Closed
opened 2026-02-05 01:47:03 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-05 01:47:03 +03:00
Owner
Copy Link

Originally created by @cblinq on GitHub (Sep 13, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

n8n

📂 What was the exact command used to execute the script?

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

8.4.13

📝 Provide a clear and concise description of the issue.

n8n won't update using the helper script "update" without manual intervention. I did previously update by removing some files, I can't remember specifically. I think I also uninstalled n8n from npm, and later reinstalled it with the "update" script

🔄 Steps to reproduce the issue.

start update by using the helper script "update"

❌ Paste the full error output (if available).

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @n8n/typeorm@0.3.20-12
npm warn Found: @sentry/node@9.46.0
npm warn node_modules/n8n/node_modules/@sentry/node
npm warn   @sentry/node@"^9.42.1" from n8n@1.110.1
npm warn   node_modules/n8n
npm warn     n8n@"*" from the root project
npm warn   2 more (@n8n/task-runner, n8n-core)
npm warn
npm warn Could not resolve dependency:
npm warn peerOptional @sentry/node@"<=8.x" from @n8n/typeorm@0.3.20-12
npm warn node_modules/n8n/node_modules/@n8n/typeorm
npm warn   @n8n/typeorm@"0.3.20-12" from n8n@1.110.1
npm warn   node_modules/n8n
npm warn   3 more (@n8n/backend-test-utils, @n8n/db, @n8n/n8n-nodes-langchain)
npm warn
npm warn Conflicting peer dependency: @sentry/node@8.55.0
npm warn node_modules/@sentry/node
npm warn   peerOptional @sentry/node@"<=8.x" from @n8n/typeorm@0.3.20-12
npm warn   node_modules/n8n/node_modules/@n8n/typeorm
npm warn     @n8n/typeorm@"0.3.20-12" from n8n@1.110.1
npm warn     node_modules/n8n
npm warn     3 more (@n8n/backend-test-utils, @n8n/db, @n8n/n8n-nodes-langchain)
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @browserbasehq/stagehand@1.14.0
npm warn Found: openai@5.12.2
npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/openai
npm warn   openai@"5.12.2" from @n8n/n8n-nodes-langchain@1.109.1
npm warn   node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain
npm warn     @n8n/n8n-nodes-langchain@"1.109.1" from n8n@1.110.1
npm warn     node_modules/n8n
npm warn   1 more (@langchain/community)
npm warn
npm warn Could not resolve dependency:
npm warn peer openai@"^4.62.1" from @browserbasehq/stagehand@1.14.0
npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@browserbasehq/stagehand
npm warn   peer @browserbasehq/stagehand@"^1.0.0" from @langchain/community@0.3.50
npm warn   node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community
npm warn
npm warn Conflicting peer dependency: openai@4.104.0
npm warn node_modules/openai
npm warn   peer openai@"^4.62.1" from @browserbasehq/stagehand@1.14.0
npm warn   node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@browserbasehq/stagehand
npm warn     peer @browserbasehq/stagehand@"^1.0.0" from @langchain/community@0.3.50
npm warn     node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @langchain/community@0.3.50
npm warn Found: @qdrant/js-client-rest@1.14.1
npm warn node_modules/n8n/node_modules/@qdrant/js-client-rest
npm warn   @qdrant/js-client-rest@"1.14.1" from @n8n/n8n-nodes-langchain@1.109.1
npm warn   node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain
npm warn     @n8n/n8n-nodes-langchain@"1.109.1" from n8n@1.110.1
npm warn     node_modules/n8n
npm warn   1 more (@langchain/qdrant)
npm warn
npm warn Could not resolve dependency:
npm warn peerOptional @qdrant/js-client-rest@"^1.15.0" from @langchain/community@0.3.50
npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community
npm warn   @langchain/community@"0.3.50" from @n8n/n8n-nodes-langchain@1.109.1
npm warn   node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain
npm warn
npm warn Conflicting peer dependency: @qdrant/js-client-rest@1.15.1
npm warn node_modules/@qdrant/js-client-rest
npm warn   peerOptional @qdrant/js-client-rest@"^1.15.0" from @langchain/community@0.3.50
npm warn   node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community
npm warn     @langchain/community@"0.3.50" from @n8n/n8n-nodes-langchain@1.109.1
npm warn     node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @langchain/community@0.3.50
npm warn Found: mongodb@6.11.0
npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/mongodb
npm warn   mongodb@"6.11.0" from @n8n/n8n-nodes-langchain@1.109.1
npm warn   node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain
npm warn     @n8n/n8n-nodes-langchain@"1.109.1" from n8n@1.110.1
npm warn     node_modules/n8n
npm warn
npm warn Could not resolve dependency:
npm warn peerOptional mongodb@"^6.17.0" from @langchain/community@0.3.50
npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community
npm warn   @langchain/community@"0.3.50" from @n8n/n8n-nodes-langchain@1.109.1
npm warn   node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain
npm warn
npm warn Conflicting peer dependency: mongodb@6.19.0
npm warn node_modules/mongodb
npm warn   peerOptional mongodb@"^6.17.0" from @langchain/community@0.3.50
npm warn   node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community
npm warn     @langchain/community@"0.3.50" from @n8n/n8n-nodes-langchain@1.109.1
npm warn     node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain
npm error code ENOTEMPTY
npm error syscall rename
npm error path /usr/lib/node_modules/n8n
npm error dest /usr/lib/node_modules/.n8n-seyU16Gs
npm error errno -39
npm error ENOTEMPTY: directory not empty, rename '/usr/lib/node_modules/n8n' -> '/usr/lib/node_modules/.n8n-seyU16Gs'
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-09-13T17_57_41_808Z-debug-0.log

[ERROR] in line 44: exit code 0: while executing command $STD npm update -g n8n

🖼️ Additional context (optional).

cat /root/.npm/_logs/2025-09-13T17_57_41_808Z-debug-0.log

7096 silly placeDep node_modules/n8n/node_modules/wiremock-rest-client agent-base@5.1.1 OK for: https-proxy-agent@4.0.0 want: 5
7097 silly placeDep node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain agent-base@6.0.2 OK for: https-proxy-agent@5.0.1 want: 6
7098 silly reify mark retired [ '/usr/lib/node_modules/n8n', '/usr/bin/n8n' ]
7099 silly reify moves {
7099 silly reify   '/usr/lib/node_modules/n8n': '/usr/lib/node_modules/.n8n-seyU16Gs',
7099 silly reify   '/usr/bin/n8n': '/usr/bin/.n8n-i29c3Ryl'
7099 silly reify }
7100 verbose stack Error: ENOTEMPTY: directory not empty, rename '/usr/lib/node_modules/n8n' -> '/usr/lib/node_modules/.n8n-seyU16Gs'
7100 verbose stack     at async Object.rename (node:internal/fs/promises:786:10)
7100 verbose stack     at async moveFile (/usr/lib/node_modules/npm/node_modules/@npmcli/fs/lib/move-file.js:30:5)
7100 verbose stack     at async Promise.allSettled (index 0)
7100 verbose stack     at async [reifyPackages] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:325:11)
7100 verbose stack     at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:142:5)
7100 verbose stack     at async Update.exec (/usr/lib/node_modules/npm/lib/commands/update.js:63:5)
7100 verbose stack     at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:207:9)
7100 verbose stack     at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:74:5)
7101 error code ENOTEMPTY
7102 error syscall rename
7103 error path /usr/lib/node_modules/n8n
7104 error dest /usr/lib/node_modules/.n8n-seyU16Gs
7105 error errno -39
7106 error ENOTEMPTY: directory not empty, rename '/usr/lib/node_modules/n8n' -> '/usr/lib/node_modules/.n8n-seyU16Gs'
7107 silly unfinished npm timer reify 1757786262128
7108 silly unfinished npm timer reify:retireShallow 1757786393660
7109 verbose cwd /opt
7110 verbose os Linux 6.8.12-13-pve
7111 verbose node v22.19.0
7112 verbose npm  v10.9.3
7113 verbose exit -39
7114 verbose code -39
Originally created by @cblinq on GitHub (Sep 13, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? n8n ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 8.4.13 ### 📝 Provide a clear and concise description of the issue. n8n won't update using the helper script "update" without manual intervention. I did previously update by removing some files, I can't remember specifically. I think I also uninstalled n8n from npm, and later reinstalled it with the "update" script ### 🔄 Steps to reproduce the issue. start update by using the helper script "update" ### ❌ Paste the full error output (if available). ``` npm warn ERESOLVE overriding peer dependency npm warn While resolving: @n8n/typeorm@0.3.20-12 npm warn Found: @sentry/node@9.46.0 npm warn node_modules/n8n/node_modules/@sentry/node npm warn @sentry/node@"^9.42.1" from n8n@1.110.1 npm warn node_modules/n8n npm warn n8n@"*" from the root project npm warn 2 more (@n8n/task-runner, n8n-core) npm warn npm warn Could not resolve dependency: npm warn peerOptional @sentry/node@"<=8.x" from @n8n/typeorm@0.3.20-12 npm warn node_modules/n8n/node_modules/@n8n/typeorm npm warn @n8n/typeorm@"0.3.20-12" from n8n@1.110.1 npm warn node_modules/n8n npm warn 3 more (@n8n/backend-test-utils, @n8n/db, @n8n/n8n-nodes-langchain) npm warn npm warn Conflicting peer dependency: @sentry/node@8.55.0 npm warn node_modules/@sentry/node npm warn peerOptional @sentry/node@"<=8.x" from @n8n/typeorm@0.3.20-12 npm warn node_modules/n8n/node_modules/@n8n/typeorm npm warn @n8n/typeorm@"0.3.20-12" from n8n@1.110.1 npm warn node_modules/n8n npm warn 3 more (@n8n/backend-test-utils, @n8n/db, @n8n/n8n-nodes-langchain) npm warn ERESOLVE overriding peer dependency npm warn While resolving: @browserbasehq/stagehand@1.14.0 npm warn Found: openai@5.12.2 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/openai npm warn openai@"5.12.2" from @n8n/n8n-nodes-langchain@1.109.1 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain npm warn @n8n/n8n-nodes-langchain@"1.109.1" from n8n@1.110.1 npm warn node_modules/n8n npm warn 1 more (@langchain/community) npm warn npm warn Could not resolve dependency: npm warn peer openai@"^4.62.1" from @browserbasehq/stagehand@1.14.0 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@browserbasehq/stagehand npm warn peer @browserbasehq/stagehand@"^1.0.0" from @langchain/community@0.3.50 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community npm warn npm warn Conflicting peer dependency: openai@4.104.0 npm warn node_modules/openai npm warn peer openai@"^4.62.1" from @browserbasehq/stagehand@1.14.0 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@browserbasehq/stagehand npm warn peer @browserbasehq/stagehand@"^1.0.0" from @langchain/community@0.3.50 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community npm warn ERESOLVE overriding peer dependency npm warn While resolving: @langchain/community@0.3.50 npm warn Found: @qdrant/js-client-rest@1.14.1 npm warn node_modules/n8n/node_modules/@qdrant/js-client-rest npm warn @qdrant/js-client-rest@"1.14.1" from @n8n/n8n-nodes-langchain@1.109.1 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain npm warn @n8n/n8n-nodes-langchain@"1.109.1" from n8n@1.110.1 npm warn node_modules/n8n npm warn 1 more (@langchain/qdrant) npm warn npm warn Could not resolve dependency: npm warn peerOptional @qdrant/js-client-rest@"^1.15.0" from @langchain/community@0.3.50 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community npm warn @langchain/community@"0.3.50" from @n8n/n8n-nodes-langchain@1.109.1 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain npm warn npm warn Conflicting peer dependency: @qdrant/js-client-rest@1.15.1 npm warn node_modules/@qdrant/js-client-rest npm warn peerOptional @qdrant/js-client-rest@"^1.15.0" from @langchain/community@0.3.50 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community npm warn @langchain/community@"0.3.50" from @n8n/n8n-nodes-langchain@1.109.1 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain npm warn ERESOLVE overriding peer dependency npm warn While resolving: @langchain/community@0.3.50 npm warn Found: mongodb@6.11.0 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/mongodb npm warn mongodb@"6.11.0" from @n8n/n8n-nodes-langchain@1.109.1 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain npm warn @n8n/n8n-nodes-langchain@"1.109.1" from n8n@1.110.1 npm warn node_modules/n8n npm warn npm warn Could not resolve dependency: npm warn peerOptional mongodb@"^6.17.0" from @langchain/community@0.3.50 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community npm warn @langchain/community@"0.3.50" from @n8n/n8n-nodes-langchain@1.109.1 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain npm warn npm warn Conflicting peer dependency: mongodb@6.19.0 npm warn node_modules/mongodb npm warn peerOptional mongodb@"^6.17.0" from @langchain/community@0.3.50 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community npm warn @langchain/community@"0.3.50" from @n8n/n8n-nodes-langchain@1.109.1 npm warn node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain npm error code ENOTEMPTY npm error syscall rename npm error path /usr/lib/node_modules/n8n npm error dest /usr/lib/node_modules/.n8n-seyU16Gs npm error errno -39 npm error ENOTEMPTY: directory not empty, rename '/usr/lib/node_modules/n8n' -> '/usr/lib/node_modules/.n8n-seyU16Gs' npm error A complete log of this run can be found in: /root/.npm/_logs/2025-09-13T17_57_41_808Z-debug-0.log [ERROR] in line 44: exit code 0: while executing command $STD npm update -g n8n ``` ### 🖼️ Additional context (optional). cat /root/.npm/_logs/2025-09-13T17_57_41_808Z-debug-0.log ``` 7096 silly placeDep node_modules/n8n/node_modules/wiremock-rest-client agent-base@5.1.1 OK for: https-proxy-agent@4.0.0 want: 5 7097 silly placeDep node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain agent-base@6.0.2 OK for: https-proxy-agent@5.0.1 want: 6 7098 silly reify mark retired [ '/usr/lib/node_modules/n8n', '/usr/bin/n8n' ] 7099 silly reify moves { 7099 silly reify '/usr/lib/node_modules/n8n': '/usr/lib/node_modules/.n8n-seyU16Gs', 7099 silly reify '/usr/bin/n8n': '/usr/bin/.n8n-i29c3Ryl' 7099 silly reify } 7100 verbose stack Error: ENOTEMPTY: directory not empty, rename '/usr/lib/node_modules/n8n' -> '/usr/lib/node_modules/.n8n-seyU16Gs' 7100 verbose stack at async Object.rename (node:internal/fs/promises:786:10) 7100 verbose stack at async moveFile (/usr/lib/node_modules/npm/node_modules/@npmcli/fs/lib/move-file.js:30:5) 7100 verbose stack at async Promise.allSettled (index 0) 7100 verbose stack at async [reifyPackages] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:325:11) 7100 verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:142:5) 7100 verbose stack at async Update.exec (/usr/lib/node_modules/npm/lib/commands/update.js:63:5) 7100 verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:207:9) 7100 verbose stack at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:74:5) 7101 error code ENOTEMPTY 7102 error syscall rename 7103 error path /usr/lib/node_modules/n8n 7104 error dest /usr/lib/node_modules/.n8n-seyU16Gs 7105 error errno -39 7106 error ENOTEMPTY: directory not empty, rename '/usr/lib/node_modules/n8n' -> '/usr/lib/node_modules/.n8n-seyU16Gs' 7107 silly unfinished npm timer reify 1757786262128 7108 silly unfinished npm timer reify:retireShallow 1757786393660 7109 verbose cwd /opt 7110 verbose os Linux 6.8.12-13-pve 7111 verbose node v22.19.0 7112 verbose npm v10.9.3 7113 verbose exit -39 7114 verbose code -39 ```
OVERLORD added the bug label 2026-02-05 01:47:03 +03:00
OVERLORD commented 2026-02-05 01:47:10 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Sep 13, 2025):

n8n is npm package. script executes update with npm update -g n8n.

If it fails its not a script issue. something is wrong with npm package

@tremor021 commented on GitHub (Sep 13, 2025): n8n is npm package. script executes update with `npm update -g n8n`. If it fails its not a script issue. something is wrong with npm package
OVERLORD commented 2026-02-05 01:47:14 +03:00
Author
Owner
Copy Link

@cblinq commented on GitHub (Sep 13, 2025):

rm -rf /usr/lib/node_modules/.n8n-* /usr/lib/node_modules/n8n
npm install -g n8n --force

This worked for me, putting it here in case someone is in the same boat.

@cblinq commented on GitHub (Sep 13, 2025): rm -rf /usr/lib/node_modules/.n8n-* /usr/lib/node_modules/n8n npm install -g n8n --force This worked for me, putting it here in case someone is in the same boat.
OVERLORD commented 2026-02-05 01:47:17 +03:00
Author
Owner
Copy Link

@bwh commented on GitHub (Sep 30, 2025):

I'm trying @cblinq's method and so far it seems to be working.

the error I initially had was:

"⠼ Updating n8n LXC
[ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1"

@bwh commented on GitHub (Sep 30, 2025): I'm trying @cblinq's method and so far it seems to be working. the error I initially had was: "⠼ Updating n8n LXC [ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1"
OVERLORD commented 2026-02-05 01:47:23 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Sep 30, 2025):

This is always a slippery slope. The method he uses to update the app is not the one described in official documentation for the app.
If we alter the script to use his method, we risk that every future issue with updates raised to the developers can be dismissed with "You are not using the commands from the official documentation".

We need to look into this...

@tremor021 commented on GitHub (Sep 30, 2025): This is always a slippery slope. The method he uses to update the app is not the one described in official documentation for the app. If we alter the script to use his method, we risk that every future issue with updates raised to the developers can be dismissed with "You are not using the commands from the official documentation". We need to look into this...
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1621
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?