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

Trilium fails to start after install #1974

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

Originally created by @meszolym on GitHub (Nov 11, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Trilium

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/trilium.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-16-pve)

📝 Provide a clear and concise description of the issue.

Trilium can't start after install. It seems like there's some missing node.js modules that are not installed by the script.

🔄 Steps to reproduce the issue.

Step 1: Run the install script
Step 2: Check systemctl status trilium

❌ Paste the full error output (if available).

root@trilium-server-mecseki-net:~# journalctl -u trilium.service -n 50 --no-pager
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: was compiled against a different Node.js version using
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: NODE_MODULE_VERSION 137. This version of Node.js requires
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: NODE_MODULE_VERSION 127. Please try re-compiling or re-installing
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: the module (for instance, using npm rebuild or npm install).
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at Object..node (node:internal/modules/cjs/loader:1921:18)
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at Module.load (node:internal/modules/cjs/loader:1465:32)
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at Function._load (node:internal/modules/cjs/loader:1282:12)
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at TracingChannel.traceSync (node:diagnostics_channel:322:14)
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at Module.require (node:internal/modules/cjs/loader:1487:12)
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at require (node:internal/modules/helpers:135:16)
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at bindings (/opt/trilium/node_modules/bindings/bindings.js:112:48)
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at new Database (/opt/trilium/node_modules/better-sqlite3/lib/database.js:48:64)
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at nOi (/opt/trilium/main.cjs:950:14657) {
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: code: 'ERR_DLOPEN_FAILED'
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: }
Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: Node.js v22.16.0
Nov 10 21:41:40 trilium-server-mecseki-net systemd[1]: trilium.service: Main process exited, code=exited, status=1/FAILURE
Nov 10 21:41:40 trilium-server-mecseki-net systemd[1]: trilium.service: Failed with result 'exit-code'.
Nov 10 21:41:40 trilium-server-mecseki-net systemd[1]: trilium.service: Consumed 663ms CPU time, 96.1M memory peak.

🖼️ Additional context (optional).

No response

Originally created by @meszolym on GitHub (Nov 11, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Trilium ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/trilium.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-16-pve) ### 📝 Provide a clear and concise description of the issue. Trilium can't start after install. It seems like there's some missing node.js modules that are not installed by the script. ### 🔄 Steps to reproduce the issue. Step 1: Run the install script Step 2: Check systemctl status trilium ### ❌ Paste the full error output (if available). root@trilium-server-mecseki-net:~# journalctl -u trilium.service -n 50 --no-pager Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: was compiled against a different Node.js version using Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: NODE_MODULE_VERSION 137. This version of Node.js requires Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: NODE_MODULE_VERSION 127. Please try re-compiling or re-installing Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: the module (for instance, using `npm rebuild` or `npm install`). Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at Object..node (node:internal/modules/cjs/loader:1921:18) Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at Module.load (node:internal/modules/cjs/loader:1465:32) Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at Function._load (node:internal/modules/cjs/loader:1282:12) Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at TracingChannel.traceSync (node:diagnostics_channel:322:14) Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at wrapModuleLoad (node:internal/modules/cjs/loader:235:24) Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at Module.require (node:internal/modules/cjs/loader:1487:12) Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at require (node:internal/modules/helpers:135:16) Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at bindings (/opt/trilium/node_modules/bindings/bindings.js:112:48) Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at new Database (/opt/trilium/node_modules/better-sqlite3/lib/database.js:48:64) Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: at nOi (/opt/trilium/main.cjs:950:14657) { Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: code: 'ERR_DLOPEN_FAILED' Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: } Nov 10 21:41:40 trilium-server-mecseki-net trilium.sh[1338]: Node.js v22.16.0 Nov 10 21:41:40 trilium-server-mecseki-net systemd[1]: trilium.service: Main process exited, code=exited, status=1/FAILURE Nov 10 21:41:40 trilium-server-mecseki-net systemd[1]: trilium.service: Failed with result 'exit-code'. Nov 10 21:41:40 trilium-server-mecseki-net systemd[1]: trilium.service: Consumed 663ms CPU time, 96.1M memory peak. ### 🖼️ Additional context (optional). _No response_
OVERLORD added the not a script issueexternaldependencies labels 2026-02-05 03:08:28 +03:00
OVERLORD commented 2026-02-05 03:08:35 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Nov 11, 2025):

https://github.com/TriliumNext/Trilium/issues/7674

@tremor021 commented on GitHub (Nov 11, 2025): https://github.com/TriliumNext/Trilium/issues/7674
OVERLORD commented 2026-02-05 03:08:40 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 11, 2025):

Our Script doesnt Install anything. Its an prebuild Archive

@MickLesk commented on GitHub (Nov 11, 2025): Our Script doesnt Install anything. Its an prebuild Archive
OVERLORD commented 2026-02-05 03:08:49 +03:00
Author
Owner
Copy Link

@meszolym commented on GitHub (Nov 11, 2025):

Thank you for the replies, I'll look into it.

@meszolym commented on GitHub (Nov 11, 2025): Thank you for the replies, I'll look into it.
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 dependencies external 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#1974
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?