SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-30 17:46:15 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

n8n #1276

New Issue
Closed
opened 2025-11-20 05:07:26 -05:00 by saavagebueno · 14 comments
saavagebueno commented 2025-11-20 05:07:26 -05:00
Owner
Copy Link

Originally created by @jaainil on GitHub (Jun 16, 2025).

✅ 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

  1. Run the script with default settings
  2. Wait for npm update -g n8n to begin
  3. 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

Originally created by @jaainil on GitHub (Jun 16, 2025). ### ✅ 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? - [x] 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 1. Run the script with default settings 2. Wait for npm update -g n8n to begin 3. 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_
saavagebueno added the bug label 2025-11-20 05:07:26 -05:00
saavagebueno commented 2025-11-20 05:07:27 -05:00
Author
Owner
Copy Link

@spijkey87 commented on GitHub (Jun 16, 2025):

Yes have the exact same problem just now

@spijkey87 commented on GitHub (Jun 16, 2025): Yes have the exact same problem just now
saavagebueno commented 2025-11-20 05:07:27 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 16, 2025):

so only in update?

@MickLesk commented on GitHub (Jun 16, 2025): so only in update?
saavagebueno commented 2025-11-20 05:07:27 -05:00
Author
Owner
Copy Link

@jaainil commented on GitHub (Jun 16, 2025):

@MickLesk yes

@jaainil commented on GitHub (Jun 16, 2025): @MickLesk yes
saavagebueno commented 2025-11-20 05:07:27 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 16, 2025):

Can you try following:

npm uninstall -g n8n
npm install -g n8n

or this one:

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

so all userdata are exist?

@MickLesk commented on GitHub (Jun 16, 2025): Can you try following: ```bash npm uninstall -g n8n npm install -g n8n ``` or this one: ```bash rm -rf /usr/lib/node_modules/.n8n-* /usr/lib/node_modules/n8n npm install -g n8n --force ``` so all userdata are exist?
saavagebueno commented 2025-11-20 05:07:27 -05:00
Author
Owner
Copy Link

@jaainil commented on GitHub (Jun 16, 2025):

@MickLesk

root@n8n:~# rm -rf /usr/lib/node_modules/.n8n-* /usr/lib/node_modules/n8n
npm install -g n8n --force
npm warn using --force Recommended protections disabled.
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated @aws-sdk/signature-v4@3.374.0: This package has moved to @smithy/signature-v4
npm warn deprecated @aws-sdk/protocol-http@3.374.0: This package has moved to @smithy/protocol-http
npm warn deprecated google-p12-pem@4.0.1: Package is no longer maintained
npm warn deprecated gauge@4.0.4: This package is no longer supported.
npm warn deprecated gm@1.25.1: The gm module has been sunset. Please migrate to an alternative. https://github.com/aheckmann/gm?tab=readme-ov-file#2025-02-24-this-project-is-not-maintained
npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead
npm warn deprecated infisical-node@1.3.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

added 1684 packages in 4m

210 packages are looking for funding
  run `npm fund` for details
root@n8n:~#

it doesn't run show
**

Image

**

@jaainil commented on GitHub (Jun 16, 2025): @MickLesk ``` root@n8n:~# rm -rf /usr/lib/node_modules/.n8n-* /usr/lib/node_modules/n8n npm install -g n8n --force npm warn using --force Recommended protections disabled. npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead. npm warn deprecated npmlog@6.0.2: This package is no longer supported. npm warn deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported. npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated @aws-sdk/signature-v4@3.374.0: This package has moved to @smithy/signature-v4 npm warn deprecated @aws-sdk/protocol-http@3.374.0: This package has moved to @smithy/protocol-http npm warn deprecated google-p12-pem@4.0.1: Package is no longer maintained npm warn deprecated gauge@4.0.4: This package is no longer supported. npm warn deprecated gm@1.25.1: The gm module has been sunset. Please migrate to an alternative. https://github.com/aheckmann/gm?tab=readme-ov-file#2025-02-24-this-project-is-not-maintained npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead npm warn deprecated infisical-node@1.3.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. added 1684 packages in 4m 210 packages are looking for funding run `npm fund` for details root@n8n:~# ``` it doesn't run show ** ![Image](https://github.com/user-attachments/assets/54bb665c-1f9e-4562-a2de-9d7eb485ba6d) **
saavagebueno commented 2025-11-20 05:07:27 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jun 16, 2025):

Did you start it?

@tremor021 commented on GitHub (Jun 16, 2025): Did you start it?
saavagebueno commented 2025-11-20 05:07:28 -05:00
Author
Owner
Copy Link

@jaainil commented on GitHub (Jun 16, 2025):

@tremor021 yes

@jaainil commented on GitHub (Jun 16, 2025): @tremor021 yes
saavagebueno commented 2025-11-20 05:07:28 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jun 16, 2025):

what command you used?

@tremor021 commented on GitHub (Jun 16, 2025): what command you used?
saavagebueno commented 2025-11-20 05:07:28 -05:00
Author
Owner
Copy Link

@jaainil commented on GitHub (Jun 16, 2025):

@tremor021 restarted container and it started automatically :/

@jaainil commented on GitHub (Jun 16, 2025): @tremor021 restarted container and it started automatically :/
saavagebueno commented 2025-11-20 05:07:28 -05:00
Author
Owner
Copy Link

@spijkey87 commented on GitHub (Jun 16, 2025):

No also when you install for the first time.

@spijkey87 commented on GitHub (Jun 16, 2025): No also when you install for the first time.
saavagebueno commented 2025-11-20 05:07:28 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jun 17, 2025):

just do basic diagnostisc after LXC restarts:

journalctl --unit n8n.service
and
ss -tulpn to check if its running

@tremor021 commented on GitHub (Jun 17, 2025): just do basic diagnostisc after LXC restarts: `journalctl --unit n8n.service` and `ss -tulpn` to check if its running
saavagebueno commented 2025-11-20 05:07:28 -05:00
Author
Owner
Copy Link

@jaainil commented on GitHub (Jun 17, 2025):

@tremor021 its running

root@n8n:~# journalctl --unit n8n.service
Jun 17 13:37:19 n8n systemd[1]: Started n8n.service - n8n.
Jun 17 13:37:22 n8n n8n[100]: Permissions 0644 for n8n settings file /.n8n/config are too wide. This is ignored for now, but in the future n8n will att>
Jun 17 13:37:22 n8n n8n[100]: User settings loaded from: /.n8n/config
Jun 17 13:37:25 n8n n8n[100]: Initializing n8n process
Jun 17 13:37:26 n8n n8n[100]: n8n ready on ::, port 5678
Jun 17 13:37:26 n8n n8n[100]: There is a deprecation related to your environment variables. Please take the recommended actions to update your configur>
Jun 17 13:37:26 n8n n8n[100]:  - N8N_RUNNERS_ENABLED -> Running n8n without task runners is deprecated. Task runners will be turned on by default in a >
Jun 17 13:37:26 n8n n8n[100]: [license SDK] Skipping renewal on init because renewal is not due yet or cert is not initialized
Jun 17 13:37:28 n8n n8n[100]: Version: 1.98.1
Jun 17 13:37:28 n8n n8n[100]: Start Active Workflows:
Jun 17 13:37:30 n8n n8n[100]: Activated workflow "Ai Artical" (ID: DfnHtnjc7GCQJ7be)
Jun 17 13:37:30 n8n n8n[100]: Activated workflow "Ai Videos" (ID: WLyhZNY9rk7e4YVu)
Jun 17 13:37:32 n8n n8n[100]: Activated workflow "My workflow 4" (ID: T4S2Yr6akb8fXDp8)
Jun 17 13:37:32 n8n n8n[100]: Editor is now accessible via:
Jun 17 13:37:32 n8n n8n
@jaainil commented on GitHub (Jun 17, 2025): @tremor021 its running ``` root@n8n:~# journalctl --unit n8n.service Jun 17 13:37:19 n8n systemd[1]: Started n8n.service - n8n. Jun 17 13:37:22 n8n n8n[100]: Permissions 0644 for n8n settings file /.n8n/config are too wide. This is ignored for now, but in the future n8n will att> Jun 17 13:37:22 n8n n8n[100]: User settings loaded from: /.n8n/config Jun 17 13:37:25 n8n n8n[100]: Initializing n8n process Jun 17 13:37:26 n8n n8n[100]: n8n ready on ::, port 5678 Jun 17 13:37:26 n8n n8n[100]: There is a deprecation related to your environment variables. Please take the recommended actions to update your configur> Jun 17 13:37:26 n8n n8n[100]: - N8N_RUNNERS_ENABLED -> Running n8n without task runners is deprecated. Task runners will be turned on by default in a > Jun 17 13:37:26 n8n n8n[100]: [license SDK] Skipping renewal on init because renewal is not due yet or cert is not initialized Jun 17 13:37:28 n8n n8n[100]: Version: 1.98.1 Jun 17 13:37:28 n8n n8n[100]: Start Active Workflows: Jun 17 13:37:30 n8n n8n[100]: Activated workflow "Ai Artical" (ID: DfnHtnjc7GCQJ7be) Jun 17 13:37:30 n8n n8n[100]: Activated workflow "Ai Videos" (ID: WLyhZNY9rk7e4YVu) Jun 17 13:37:32 n8n n8n[100]: Activated workflow "My workflow 4" (ID: T4S2Yr6akb8fXDp8) Jun 17 13:37:32 n8n n8n[100]: Editor is now accessible via: Jun 17 13:37:32 n8n n8n ```
saavagebueno commented 2025-11-20 05:07:29 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 17, 2025):

Looks ok? You cannot reach the IP with Port?

@MickLesk commented on GitHub (Jun 17, 2025): Looks ok? You cannot reach the IP with Port?
saavagebueno commented 2025-11-20 05:07:29 -05:00
Author
Owner
Copy Link

@jaainil commented on GitHub (Jun 23, 2025):

Yes

@jaainil commented on GitHub (Jun 23, 2025): Yes
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1276
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?