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 13 Packages Projects Releases 10 Wiki Activity

n8n db location wrong #1707

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

Originally created by @sharkoz on GitHub (Oct 1, 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?

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

📈 Which Proxmox version are you on?

pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve)

📝 Provide a clear and concise description of the issue.

N8n uses the wrong path for its root folder
It uses /.n8n/ instead of /root/.n8n

This makes it impossible to use the CLI to import settings for example, as the cli imports to /root/.n8n/database.sqlite and the exec uses /.n8n/database.sqlite

🔄 Steps to reproduce the issue.

Launch with default settings

Try :
lsof | grep database.sqlite

❌ Paste the full error output (if available).

root@n8n:~# lsof | grep database.sqlite node 14762 root 21u REG 0,143 524288 216175 /.n8n/database.sqlite

🖼️ Additional context (optional).

I temporarily fixed it by deleting /.n8n and creating a symlink to /root/.n8n

Originally created by @sharkoz on GitHub (Oct 1, 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? 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 ### 📈 Which Proxmox version are you on? pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve) ### 📝 Provide a clear and concise description of the issue. N8n uses the wrong path for its root folder It uses `/.n8n/` instead of `/root/.n8n` This makes it impossible to use the CLI to import settings for example, as the cli imports to` /root/.n8n/database.sqlite` and the exec uses `/.n8n/database.sqlite ` ### 🔄 Steps to reproduce the issue. Launch with default settings Try : `lsof | grep database.sqlite` ### ❌ Paste the full error output (if available). `root@n8n:~# lsof | grep database.sqlite node 14762 root 21u REG 0,143 524288 216175 /.n8n/database.sqlite` ### 🖼️ Additional context (optional). I temporarily fixed it by deleting `/.n8n` and creating a symlink to `/root/.n8n`
OVERLORD added the not a script issue label 2026-02-05 02:02:06 +03:00
OVERLORD commented 2026-02-05 02:02:11 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 2, 2025):

$STD npm install --global patch-package
$STD npm install --global n8n

Its the only what we do. n8n create his own directorys. Report it there, if you not confirm with this

@MickLesk commented on GitHub (Oct 2, 2025): $STD npm install --global patch-package $STD npm install --global n8n Its the only what we do. n8n create his own directorys. Report it there, if you not confirm with this
OVERLORD commented 2026-02-05 02:02:19 +03:00
Author
Owner
Copy Link

@sharkoz commented on GitHub (Oct 2, 2025):

I believe that n8n installs this folder in the user /home , and here during installation and run it thinks that /home is just / , and when I get an interactive session it thinks that its home is /root .

I'll run some more tests

@sharkoz commented on GitHub (Oct 2, 2025): I believe that n8n installs this folder in the user /home , and here during installation and run it thinks that /home is just `/` , and when I get an interactive session it thinks that its home is `/root` . I'll run some more tests
OVERLORD commented 2026-02-05 02:02:21 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 2, 2025):

if you think something is wrong, feel free to create an PR and we can check it. Ive checked there docs and is the same what we do

@MickLesk commented on GitHub (Oct 2, 2025): if you think something is wrong, feel free to create an PR and we can check it. Ive checked there docs and is the same what we do
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 not a script issue
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#1707
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?