-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
β Have you read and understood the above guidelines?
Yes
π What is the name of the script you are using?
ct/n8n.sh
π What was the exact command used to execute the script?
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/n8n.sh)"
βοΈ What settings are you using?
- Default Settings
- Advanced Settings
π₯οΈ Which Linux distribution are you using?
Debian 12
π Provide a clear and concise description of the issue.
During npm update -g n8n, the install fails due to a ENOTEMPTY error while renaming the n8n module directory. This happens at the final step of the script execution (line 38).
This issue seems to be caused by leftover temp folders (e.g., .n8n-*) in /usr/lib/node_modules β possibly from a prior interrupted install or npm permission issue.
π Steps to reproduce the issue.
π Steps to Reproduce
- Run the script with default settings
- Wait for npm update -g n8n to begin
- Encounter failure with rename error
β Paste the full error output (if available).
____ ( __ )____
/ __ \/ __ / __ \
/ / / / /_/ / / / /
/_/ /_/\____/_/ /_/
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-06-16T14_10_02_814Z-debug-0.log
β Updating n8n LXC
[ERROR] in line 38: exit code 0: while executing command $STD npm update -g n8n
root@n8n:~#
πΌοΈ Additional context (optional).
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working