Trilium LXC does not update correctly

[photodrum]

✅ Have you read and understood the above guidelines?

yes

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

Trilium LXC

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/trilium.sh)"

📝 Provide a clear and concise description of the issue.

After the update, access (502) to Trilium is lost

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

No response

🔄 Steps to reproduce the issue.

Run: bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/trilium.sh)"

---

/_ __/() () ______ ___
/ / / / / / / / / / __ `
/ / / / / / / / // / / / / / /
// // ////_,// // /_/

✔️ Stopped Trilium
✔️ Updated to v0.91.5
✔️ Cleaned
✔️ Started Trilium
✔️ Updated Successfully

❌ Paste the full error output (if available).

502 Bad Gateway

🖼️ Additional context (optional).

No response

[tremor021]

there is really nothing that update scripts does to break installed application, since configuration and data files are not in the application folder
update function basicaly just gets the latest release archive and extracts it to the same folder where trillium is already installed

can you give output of:
curl http://container-ip:8080/

[MickLesk]

Or systemctl status...

[tremor021]

Also, i just tried on mine:

 ______     _ ___               
 /_  __/____(_) (_)_  ______ ___ 
  / / / ___/ / / / / / / __ `__ \
 / / / /  / / / / /_/ / / / / / /
/_/ /_/  /_/_/_/\__,_/_/ /_/ /_/ 
                                 

  ✔️  Stopped Trilium
  ✔️  Updated to v0.91.5
  ✔️  Cleaned
  ✔️  Started Trilium
  ✔️  Updated Successfully
root@trilium:~/# systemctl status trilium.service 
● trilium.service - Trilium Daemon
     Loaded: loaded (/etc/systemd/system/trilium.service; enabled; preset: enabled)
     Active: active (running) since Fri 2025-01-31 22:03:04 CET; 15s ago
   Main PID: 5495 (trilium.sh)
      Tasks: 12 (limit: 77006)
     Memory: 109.9M
        CPU: 3.103s
     CGroup: /system.slice/trilium.service
             ├─5495 /bin/sh /opt/trilium/trilium.sh
             └─5496 ./node/bin/node src/main

Jan 31 22:03:07 trilium trilium.sh[5496]:   "utcDateTime": "2025-01-31T21:03:05.658Z"
Jan 31 22:03:07 trilium trilium.sh[5496]: }
Jan 31 22:03:07 trilium trilium.sh[5496]: CPU model: unknown, logical cores: 1, freq: 1799 Mhz
Jan 31 22:03:07 trilium trilium.sh[5496]: Trusted reverse proxy: false
Jan 31 22:03:07 trilium trilium.sh[5496]: App HTTP server starting up at port 8080
Jan 31 22:03:07 trilium trilium.sh[5496]: Listening on port 8080
Jan 31 22:03:08 trilium trilium.sh[5496]: websocket client connected
Jan 31 22:03:11 trilium trilium.sh[5496]: Table counts: notes: 220, revisions: 0, attachments: 18, branches: 234, attributes: 350, etapi_tokens: 0, blobs: 129
Jan 31 22:03:11 trilium trilium.sh[5496]: Slow query took 30ms: SELECT id, entityId FROM entity_changes LEFT JOIN notes ON entityId = notes.noteId WHERE entity_changes.isErased = 0 AND entity_changes.entit>
Jan 31 22:03:11 trilium trilium.sh[5496]: All consistency checks passed with no errors detected (took 96ms)

It works just fine.

[pziemniak]

Does not work for me, installed about a week ago, updated today and it immediately stopped working. Found the following in the logs:

trilium.sh[852]: (node:852) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
trilium.sh[852]: (Use `node --trace-warnings ...` to show where the warning was created)
trilium.sh[852]: file:///opt/trilium/node_modules/image-type/index.js:1
trilium.sh[852]: import {fileTypeFromBuffer} from 'file-type';
trilium.sh[852]:         ^^^^^^^^^^^^^^^^^^
trilium.sh[852]: SyntaxError: Named export 'fileTypeFromBuffer' not found. The requested module 'file-type' is a CommonJS module, which may not support all module.exports as named exports.
trilium.sh[852]: CommonJS modules can always be imported via the default export, for example using:
trilium.sh[852]: import pkg from 'file-type';
trilium.sh[852]: const {fileTypeFromBuffer} = pkg;
trilium.sh[852]:     at ModuleJob._instantiate (node:internal/modules/esm/module_job:134:21)
trilium.sh[852]:     at async ModuleJob.run (node:internal/modules/esm/module_job:217:5)
trilium.sh[852]:     at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
trilium.sh[852]:     at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:123:5)
trilium.sh[852]: Node.js v20.15.1

[MickLesk]

Can you try to Upgrade NodeJs to 22?

[pziemniak]

NodeJs seems to be bundled together with Trilium package and it does not have npm to make an upgrade. I installed version 22 using nvm and used that version to launch Trillum, but the result is the same.

EDIT
updated modules using npm 22 and it worked all fine.

[MickLesk]

Maybe an trillium bug with the package? Dockerfile use node22

[pziemniak]

Appears something was either with the package or with the upgrade. When re-did the upgrade it starts now fine with the built-in NodeJs 20.

[photodrum]

there is really nothing that update scripts does to break installed application, since configuration and data files are not in the application folder update function basicaly just gets the latest release archive and extracts it to the same folder where trillium is already installed

can you give output of: curl http://container-ip:8080/

curl: (7) Failed to connect to 192.168.50.28 port 8080 after 0 ms: Couldn't connect to server

[Noxious-Stimuli]

Same issue here.

  ______     _ ___               
 /_  __/____(_) (_)_  ______ ___ 
  / / / ___/ / / / / / / __ `__ \
 / / / /  / / / / /_/ / / / / / /
/_/ /_/  /_/_/_/\__,_/_/ /_/ /_/ 
                                 

  ✔️  Stopped Trilium
  ✔️  Updated to v0.91.5
  ✔️  Cleaned
  ✔️  Started Trilium
  ✔️  Updated Successfully
root@trilium:~# systemctl status trilium.service
× trilium.service - Trilium Daemon
     Loaded: loaded (/etc/systemd/system/trilium.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Sat 2025-02-01 17:11:06 GMT; 6s ago
   Duration: 286ms
    Process: 2069 ExecStart=/opt/trilium/trilium.sh (code=exited, status=1/FAILURE)
   Main PID: 2069 (code=exited, status=1/FAILURE)
        CPU: 339ms

Feb 01 17:11:06 trilium systemd[1]: trilium.service: Scheduled restart job, restart counter is at 5.
Feb 01 17:11:06 trilium systemd[1]: Stopped trilium.service - Trilium Daemon.
Feb 01 17:11:06 trilium systemd[1]: trilium.service: Start request repeated too quickly.
Feb 01 17:11:06 trilium systemd[1]: trilium.service: Failed with result 'exit-code'.
Feb 01 17:11:06 trilium systemd[1]: Failed to start trilium.service - Trilium Daemon.
root@trilium:~# curl http://192.168.0.243:8080
curl: (7) Failed to connect to 192.168.0.243 port 8080 after 0 ms: Couldn't connect to server

Rerunning "update" in the console causes the script to trigger as if there was an update, but it results in the above errors and failure to start.

[MickLesk]

Okay, i can check it at monday, fine for you all?

[cbbossi]

Hello there.

Yap apparently others are having the same issue I just had a few minutes ago.

Thanks in advance for any clue to fix that.

[ehcorn]

joining the fray but I get a different error. I installed using the script from the old github: https://raw.githubusercontent.com/tteck/Proxmox/main/ct/trilium.sh

tried running plain "update" and get: [ERROR] in line 66: exit code 0: while executing command wget -q https://github.com/TriliumNext/Notes/releases/download/${RELEASE}/TriliumNextNotes-${RELEASE}-server-linux-x64.tar.xz

so I tried running the new update script inside the shell, seems to update and says trilium stopped, updated, etc. as expected then when I run systemctl status trilium I get:

× trilium.service - Trilium Daemon
     Loaded: loaded (/etc/systemd/system/trilium.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Sun 2025-02-02 16:22:21 PST; 6min ago
   Duration: 336ms
    Process: 755 ExecStart=/opt/trilium/trilium.sh (code=exited, status=1/FAILURE)
   Main PID: 755 (code=exited, status=1/FAILURE)
        CPU: 322ms

Feb 02 16:22:21 trilium systemd[1]: trilium.service: Scheduled restart job, restart counter is at 5.
Feb 02 16:22:21 trilium systemd[1]: Stopped trilium.service - Trilium Daemon.
Feb 02 16:22:21 trilium systemd[1]: trilium.service: Start request repeated too quickly.
Feb 02 16:22:21 trilium systemd[1]: trilium.service: Failed with result 'exit-code'.
Feb 02 16:22:21 trilium systemd[1]: Failed to start trilium.service - Trilium Daemon.

[MickLesk]

I try my luck, but for me it worked. ive installed latest release (v0.90.12) and setup the installation with password and co. created some testnotes and then enter "update" in the lxc shell. Now its version: v0.91.5

---

Can a user with failure status do following:
cd /opt/trilium
./trilium.sh

whats the output?