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

Trilium LXC does not update correctly #419

New Issue
Closed
opened 2026-02-04 18:40:18 +03:00 by OVERLORD · 42 comments
OVERLORD commented 2026-02-04 18:40:18 +03:00
Owner
Copy Link

Originally created by @photodrum on GitHub (Jan 31, 2025).

✅ 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

Originally created by @photodrum on GitHub (Jan 31, 2025). ### ✅ 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? - [x] 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_
OVERLORD added the question label 2026-02-04 18:40:18 +03:00
OVERLORD commented 2026-02-04 18:40:32 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jan 31, 2025):

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/

@tremor021 commented on GitHub (Jan 31, 2025): 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/`
OVERLORD commented 2026-02-04 18:40:40 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 31, 2025):

Or systemctl status...

@MickLesk commented on GitHub (Jan 31, 2025): Or systemctl status...
OVERLORD commented 2026-02-04 18:40:49 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 1, 2025):

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.

@tremor021 commented on GitHub (Feb 1, 2025): 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.
OVERLORD commented 2026-02-04 18:40:55 +03:00
Author
Owner
Copy Link

@pziemniak commented on GitHub (Feb 1, 2025):

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
@pziemniak commented on GitHub (Feb 1, 2025): 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 ```
OVERLORD commented 2026-02-04 18:41:03 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 1, 2025):

Can you try to Upgrade NodeJs to 22?

@MickLesk commented on GitHub (Feb 1, 2025): Can you try to Upgrade NodeJs to 22?
OVERLORD commented 2026-02-04 18:41:35 +03:00
Author
Owner
Copy Link

@pziemniak commented on GitHub (Feb 1, 2025):

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.

@pziemniak commented on GitHub (Feb 1, 2025): 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.
OVERLORD commented 2026-02-04 18:41:39 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 1, 2025):

Maybe an trillium bug with the package? Dockerfile use node22

@MickLesk commented on GitHub (Feb 1, 2025): Maybe an trillium bug with the package? Dockerfile use node22
OVERLORD commented 2026-02-04 18:41:51 +03:00
Author
Owner
Copy Link

@pziemniak commented on GitHub (Feb 1, 2025):

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.

@pziemniak commented on GitHub (Feb 1, 2025): 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.
OVERLORD commented 2026-02-04 18:41:58 +03:00
Author
Owner
Copy Link

@photodrum commented on GitHub (Feb 1, 2025):

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

@photodrum commented on GitHub (Feb 1, 2025): > 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
OVERLORD commented 2026-02-04 18:42:07 +03:00
Author
Owner
Copy Link

@Noxious-Stimuli commented on GitHub (Feb 1, 2025):

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.

@Noxious-Stimuli commented on GitHub (Feb 1, 2025): 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.
OVERLORD commented 2026-02-04 18:42:20 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 1, 2025):

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

@MickLesk commented on GitHub (Feb 1, 2025): Okay, i can check it at monday, fine for you all?
OVERLORD commented 2026-02-04 18:42:23 +03:00
Author
Owner
Copy Link

@cbbossi commented on GitHub (Feb 2, 2025):

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.

@cbbossi commented on GitHub (Feb 2, 2025): 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.
OVERLORD commented 2026-02-04 18:42:29 +03:00
Author
Owner
Copy Link

@ehcorn commented on GitHub (Feb 3, 2025):

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.
@ehcorn commented on GitHub (Feb 3, 2025): 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. ```
OVERLORD commented 2026-02-04 18:42:32 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 3, 2025):

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

Image

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

whats the output?

@MickLesk commented on GitHub (Feb 3, 2025): I try my luck, but for me it worked. ive installed latest release ([v0.90.12](https://github.com/TriliumNext/Notes/releases/tag/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](https://github.com/TriliumNext/Notes/releases/tag/v0.91.5) ![Image](https://github.com/user-attachments/assets/b0e58b54-6667-4bf7-ac65-dac7807cd3a0) ______ Can a user with failure status do following: cd /opt/trilium ./trilium.sh whats the output?
OVERLORD commented 2026-02-04 18:42:43 +03:00
Author
Owner
Copy Link

@photodrum commented on GitHub (Feb 3, 2025):

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

whats the output?

Image

@photodrum commented on GitHub (Feb 3, 2025): > Can a user with failure status do following: cd /opt/trilium ./trilium.sh > > whats the output? ![Image](https://github.com/user-attachments/assets/8cca5f00-f259-401f-b609-d26cb91e4052)
OVERLORD commented 2026-02-04 18:42:50 +03:00
Author
Owner
Copy Link

@cbbossi commented on GitHub (Feb 3, 2025):

Follow your request...

Image

@cbbossi commented on GitHub (Feb 3, 2025): Follow your request... ![Image](https://github.com/user-attachments/assets/720a493d-9c70-406e-93dc-01e78df94538)
OVERLORD commented 2026-02-04 18:42:55 +03:00
Author
Owner
Copy Link

@cbbossi commented on GitHub (Feb 6, 2025):

hello, I tested the new version but the issue still there,,

Image

@cbbossi commented on GitHub (Feb 6, 2025): hello, I tested the new version but the issue still there,, ![Image](https://github.com/user-attachments/assets/86b66276-193f-4d4a-898c-2fdd6578b11f)
OVERLORD commented 2026-02-04 18:43:04 +03:00
Author
Owner
Copy Link

@cbbossi commented on GitHub (Feb 6, 2025):

Follow the other diagnostics I did based on the request from MickLesk

I hope this can provide enough info on the matter.

Image

@cbbossi commented on GitHub (Feb 6, 2025): Follow the other diagnostics I did based on the request from MickLesk I hope this can provide enough info on the matter. ![Image](https://github.com/user-attachments/assets/a116ff24-1acf-492d-bc39-3181109ccfc7)
OVERLORD commented 2026-02-04 18:43:23 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Feb 6, 2025):

I also can not reproduce the issue.

@michelroegl-brunner commented on GitHub (Feb 6, 2025): I also can not reproduce the issue.
OVERLORD commented 2026-02-04 18:43:33 +03:00
Author
Owner
Copy Link

@beercity commented on GitHub (Feb 6, 2025):

I have been using Trilium for several years, initially the zadam edition and then it was upgraded to the TriliumNext edition using the script. Ever since the upgrade, I am experiencing the same issue as above.

I created a fresh LXC using the script and imported my backup, and it works without issue. The most stable and sustainable option may just be to take a backup and import into a new instance if the upgrade breaks Trilium.

@beercity commented on GitHub (Feb 6, 2025): I have been using Trilium for several years, initially the zadam edition and then it was upgraded to the TriliumNext edition using the script. Ever since the upgrade, I am experiencing the same issue as above. I created a fresh LXC using the script and imported my backup, and it works without issue. The most stable and sustainable option may just be to take a backup and import into a new instance if the upgrade breaks Trilium.
OVERLORD commented 2026-02-04 18:43:38 +03:00
Author
Owner
Copy Link

@cbbossi commented on GitHub (Feb 6, 2025):

Ya!
That is exactly the procedure I'm try no to do, since I'm little behind of my backups of trillium.

It is a little bit annoying every time u update this trillium at PROMOX container u have to refresh the dam thing all over again.

I really like this editor it is by far the best editor for my needs.

I was helpful some one will came out with some kind of solution for this update, sync GitHub communists always show up w/ some solution.

@cbbossi commented on GitHub (Feb 6, 2025): Ya! That is exactly the procedure I'm try no to do, since I'm little behind of my backups of trillium. It is a little bit annoying every time u update this trillium at PROMOX container u have to refresh the dam thing all over again. I really like this editor it is by far the best editor for my needs. I was helpful some one will came out with some kind of solution for this update, sync GitHub communists always show up w/ some solution.
OVERLORD commented 2026-02-04 18:43:45 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 6, 2025):

I havnt an solution yet, because for me it works from several versions...

@MickLesk commented on GitHub (Feb 6, 2025): I havnt an solution yet, because for me it works from several versions...
OVERLORD commented 2026-02-04 18:43:54 +03:00
Author
Owner
Copy Link

@Astrolight commented on GitHub (Feb 7, 2025):

I also had issues with the update. I just rm the stuff in the /opt/trilium folder and reran the 'update' command. All of my items are fine and trilium is back up.

Might be an issue with overwriting an old install and some items not being deleted like they normally would.

@Astrolight commented on GitHub (Feb 7, 2025): I also had issues with the update. I just rm the stuff in the /opt/trilium folder and reran the 'update' command. All of my items are fine and trilium is back up. Might be an issue with overwriting an old install and some items not being deleted like they normally would.
OVERLORD commented 2026-02-04 18:44:01 +03:00
Author
Owner
Copy Link

@photodrum commented on GitHub (Feb 7, 2025):

I also had issues with the update. I just rm the stuff in the /opt/trilium folder and reran the 'update' command. All of my items are fine and trilium is back up.

Might be an issue with overwriting an old install and some items not being deleted like they normally would.

Thanks brother, apparently you are right and your update method helped me.

@photodrum commented on GitHub (Feb 7, 2025): > I also had issues with the update. I just rm the stuff in the /opt/trilium folder and reran the 'update' command. All of my items are fine and trilium is back up. > > Might be an issue with overwriting an old install and some items not being deleted like they normally would. Thanks brother, apparently you are right and your update method helped me.
OVERLORD commented 2026-02-04 18:44:03 +03:00
Author
Owner
Copy Link

@cbbossi commented on GitHub (Feb 7, 2025):

Hello Astrolight

If I remove this path the database will not be erased to?

Image
@cbbossi commented on GitHub (Feb 7, 2025): Hello Astrolight If I remove this path the database will not be erased to? <img width="687" alt="Image" src="https://github.com/user-attachments/assets/f5260e21-de9a-4875-910b-4412d38e6b8c" />
OVERLORD commented 2026-02-04 18:44:05 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 7, 2025):

can anyone check the dev branch, if this works? Please backup your LXC before

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/develop/ct/trilium.sh)"
@MickLesk commented on GitHub (Feb 7, 2025): can anyone check the dev branch, if this works? Please backup your LXC before ``` bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/develop/ct/trilium.sh)" ```
OVERLORD commented 2026-02-04 18:44:13 +03:00
Author
Owner
Copy Link

@cbbossi commented on GitHub (Feb 7, 2025):

Hello
Ya worked!
I would like to express my gratitude to your disposition to fix the issue.

Keep the good work pls!

Image

@cbbossi commented on GitHub (Feb 7, 2025): Hello Ya worked! I would like to express my gratitude to your disposition to fix the issue. Keep the good work pls! ![Image](https://github.com/user-attachments/assets/c5ff8ece-95fa-4b12-bfdf-ccb041440de6)
OVERLORD commented 2026-02-04 18:44:18 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 7, 2025):

I try at evening to create an PR, Ive shutdown my pc 10min ago

@MickLesk commented on GitHub (Feb 7, 2025): I try at evening to create an PR, Ive shutdown my pc 10min ago
OVERLORD commented 2026-02-04 18:44:24 +03:00
Author
Owner
Copy Link

@Scorpoon commented on GitHub (Feb 7, 2025):

can anyone check the dev branch, if this works? Please backup your LXC before

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

Works for me too, thanks for the fix

@Scorpoon commented on GitHub (Feb 7, 2025): > can anyone check the dev branch, if this works? Please backup your LXC before > > ``` > bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/develop/ct/trilium.sh)" > ``` Works for me too, thanks for the fix
OVERLORD commented 2026-02-04 18:44:29 +03:00
Author
Owner
Copy Link

@johndoe0815 commented on GitHub (Feb 13, 2025):

While the update does now work with the dev branch for me, when using the normal script

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

I just get an error
environment: line 33: RELEASE: unbound variable

There seems to be an issue with this line, which is not in the dev branch:

    if [[ "${RELEASE}" != "$(cat /opt/${APP}_version.txt)" ]] || [[ ! -f /opt/${APP}_version.txt ]]; then
    RELEASE=$(curl -s https://api.github.com/repos/TriliumNext/Notes/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }')
@johndoe0815 commented on GitHub (Feb 13, 2025): While the update does now work with the dev branch for me, when using the normal script `bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/trilium.sh)"` I just get an error `environment: line 33: RELEASE: unbound variable` There seems to be an issue with this line, which is not in the dev branch: ``` if [[ "${RELEASE}" != "$(cat /opt/${APP}_version.txt)" ]] || [[ ! -f /opt/${APP}_version.txt ]]; then RELEASE=$(curl -s https://api.github.com/repos/TriliumNext/Notes/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }') ```
OVERLORD commented 2026-02-04 18:44:37 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 13, 2025):

Create an empty File with Touch there

@MickLesk commented on GitHub (Feb 13, 2025): Create an empty File with Touch there
OVERLORD commented 2026-02-04 18:44:48 +03:00
Author
Owner
Copy Link

@johndoe0815 commented on GitHub (Feb 13, 2025):

Create an empty file where and how?
Can‘t the script just made properly working without manual interventions?

@johndoe0815 commented on GitHub (Feb 13, 2025): Create an empty file where and how? Can‘t the script just made properly working without manual interventions?
OVERLORD commented 2026-02-04 18:45:20 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 13, 2025):

no its marked as breaking change since weeks

touch /opt/TrilliumNext_version.txt

@MickLesk commented on GitHub (Feb 13, 2025): no its marked as breaking change since weeks touch /opt/TrilliumNext_version.txt
OVERLORD commented 2026-02-04 18:45:34 +03:00
Author
Owner
Copy Link

@johndoe0815 commented on GitHub (Feb 13, 2025):

Where is that marked? I am already on Trilium Next, just with the latest update the script does not anymore work. And the dev branch does not seem to need any touch.

@johndoe0815 commented on GitHub (Feb 13, 2025): Where is that marked? I am already on Trilium Next, just with the latest update the script does not anymore work. And the dev branch does not seem to need any touch.
OVERLORD commented 2026-02-04 18:45:39 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 13, 2025):

Why do we always have to discuss? Be glad that we support the script at all. Instead of discussing it forever, you could have fixed it with this one-liner. We can't catch every variant of 10,000 installations!

@MickLesk commented on GitHub (Feb 13, 2025): Why do we always have to discuss? Be glad that we support the script at all. Instead of discussing it forever, you could have fixed it with this one-liner. We can't catch every variant of 10,000 installations!
OVERLORD commented 2026-02-04 18:45:43 +03:00
Author
Owner
Copy Link

@johndoe0815 commented on GitHub (Feb 13, 2025):

I am glad. Why are you directly feeling offended? I am just asking questions, not blaming anyone.

We are talking about installations that all use the same single line to install and update, so the variety is for sure not that high. It is fine if there is any intervention required, it would just be helpful to then either put it on the main page or at least explain if and why this cannot be fixed in the script (which seems to be possible in the dev branch). If you were willing to explain, I would ask less questions. I just want to stay „in standard“ and not bring the container with some additional commands into a stage that would cause further issues in the future. THAT would increase the variants.

@johndoe0815 commented on GitHub (Feb 13, 2025): I am glad. Why are you directly feeling offended? I am just asking questions, not blaming anyone. We are talking about installations that all use the same single line to install and update, so the variety is for sure not that high. It is fine if there is any intervention required, it would just be helpful to then either put it on the main page or at least explain if and why this cannot be fixed in the script (which seems to be possible in the dev branch). If you were willing to explain, I would ask less questions. I just want to stay „in standard“ and not bring the container with some additional commands into a stage that would cause further issues in the future. THAT would increase the variants.
OVERLORD commented 2026-02-04 18:45:46 +03:00
Author
Owner
Copy Link

@Noxious-Stimuli commented on GitHub (Feb 13, 2025):

Why do we always have to discuss?

Because the fix you suggested didn't work.

environment: line 32: RELEASE: unbound variable

@Noxious-Stimuli commented on GitHub (Feb 13, 2025): > Why do we always have to discuss? Because the fix you suggested didn't work. ` environment: line 32: RELEASE: unbound variable`
OVERLORD commented 2026-02-04 18:45:52 +03:00
Author
Owner
Copy Link

@Scorpoon commented on GitHub (Feb 13, 2025):

no its marked as breaking change since weeks

touch /opt/TrilliumNext_version.txt

Created the file ("Trilium_version.txt" instead of "TriliumNext_version.txt" because $APP = Trilium) but it seems that there is still something wrong.
environment: line 32: RELEASE: unbound variable

Maybe I'm wrong but in the /ct/trilium.sh script the RELEASE variable is accessed before it's set and thats why the error pops up: also the line number 32 would match the follwing first line

if [[ "${RELEASE}" != "$(cat /opt/${APP}_version.txt)" ]] || [[ ! -f /opt/${APP}_version.txt ]]; then
RELEASE=$(curl -s https://api.github.com/repos/TriliumNext/Notes/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }')
@Scorpoon commented on GitHub (Feb 13, 2025): > no its marked as breaking change since weeks > > touch /opt/TrilliumNext_version.txt Created the file ("Trilium_version.txt" instead of "TriliumNext_version.txt" because $APP = Trilium) but it seems that there is still something wrong. `environment: line 32: RELEASE: unbound variable` Maybe I'm wrong but in the /ct/trilium.sh script the RELEASE variable is accessed before it's set and thats why the error pops up: also the line number 32 would match the follwing first line if [[ "${RELEASE}" != "$(cat /opt/${APP}_version.txt)" ]] || [[ ! -f /opt/${APP}_version.txt ]]; then RELEASE=$(curl -s https://api.github.com/repos/TriliumNext/Notes/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }')
OVERLORD commented 2026-02-04 18:45:57 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 13, 2025):

no its marked as breaking change since weeks
touch /opt/TrilliumNext_version.txt

Created the file ("Trilium_version.txt" instead of "TriliumNext_version.txt" because $APP = Trilium) but it seems that there is still something wrong. environment: line 32: RELEASE: unbound variable

Maybe I'm wrong but in the /ct/trilium.sh script the RELEASE variable is accessed before it's set and thats why the error pops up: also the line number 32 would match the follwing first line

if [[ "${RELEASE}" != "$(cat /opt/${APP}_version.txt)" ]] || [[ ! -f /opt/${APP}_version.txt ]]; then
RELEASE=$(curl -s https://api.github.com/repos/TriliumNext/Notes/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }')

easy, thats fixed.

@MickLesk commented on GitHub (Feb 13, 2025): > > no its marked as breaking change since weeks > > touch /opt/TrilliumNext_version.txt > > Created the file ("Trilium_version.txt" instead of "TriliumNext_version.txt" because $APP = Trilium) but it seems that there is still something wrong. `environment: line 32: RELEASE: unbound variable` > > Maybe I'm wrong but in the /ct/trilium.sh script the RELEASE variable is accessed before it's set and thats why the error pops up: also the line number 32 would match the follwing first line > > ``` > if [[ "${RELEASE}" != "$(cat /opt/${APP}_version.txt)" ]] || [[ ! -f /opt/${APP}_version.txt ]]; then > RELEASE=$(curl -s https://api.github.com/repos/TriliumNext/Notes/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }') > ``` easy, thats fixed.
OVERLORD commented 2026-02-04 18:46:05 +03:00
Author
Owner
Copy Link

@Scorpoon commented on GitHub (Feb 13, 2025):

no its marked as breaking change since weeks
touch /opt/TrilliumNext_version.txt

Created the file ("Trilium_version.txt" instead of "TriliumNext_version.txt" because $APP = Trilium) but it seems that there is still something wrong. environment: line 32: RELEASE: unbound variable
Maybe I'm wrong but in the /ct/trilium.sh script the RELEASE variable is accessed before it's set and thats why the error pops up: also the line number 32 would match the follwing first line

if [[ "${RELEASE}" != "$(cat /opt/${APP}_version.txt)" ]] || [[ ! -f /opt/${APP}_version.txt ]]; then
RELEASE=$(curl -s https://api.github.com/repos/TriliumNext/Notes/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }')

easy, thats fixed.

Ah great, I just wanted to push my PR :D
Thanks ;)

@Scorpoon commented on GitHub (Feb 13, 2025): > > > no its marked as breaking change since weeks > > > touch /opt/TrilliumNext_version.txt > > > > > > Created the file ("Trilium_version.txt" instead of "TriliumNext_version.txt" because $APP = Trilium) but it seems that there is still something wrong. `environment: line 32: RELEASE: unbound variable` > > Maybe I'm wrong but in the /ct/trilium.sh script the RELEASE variable is accessed before it's set and thats why the error pops up: also the line number 32 would match the follwing first line > > ``` > > if [[ "${RELEASE}" != "$(cat /opt/${APP}_version.txt)" ]] || [[ ! -f /opt/${APP}_version.txt ]]; then > > RELEASE=$(curl -s https://api.github.com/repos/TriliumNext/Notes/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }') > > ``` > > easy, thats fixed. Ah great, I just wanted to push my PR :D Thanks ;)
OVERLORD commented 2026-02-04 18:46:19 +03:00
Author
Owner
Copy Link

@Scorpoon commented on GitHub (Feb 13, 2025):

no its marked as breaking change since weeks
touch /opt/TrilliumNext_version.txt

Created the file ("Trilium_version.txt" instead of "TriliumNext_version.txt" because $APP = Trilium) but it seems that there is still something wrong. environment: line 32: RELEASE: unbound variable
Maybe I'm wrong but in the /ct/trilium.sh script the RELEASE variable is accessed before it's set and thats why the error pops up: also the line number 32 would match the follwing first line

if [[ "${RELEASE}" != "$(cat /opt/${APP}_version.txt)" ]] || [[ ! -f /opt/${APP}_version.txt ]]; then
RELEASE=$(curl -s https://api.github.com/repos/TriliumNext/Notes/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }')

easy, thats fixed.

Added another PR for a missing ";" after your change...

@Scorpoon commented on GitHub (Feb 13, 2025): > > > no its marked as breaking change since weeks > > > touch /opt/TrilliumNext_version.txt > > > > > > Created the file ("Trilium_version.txt" instead of "TriliumNext_version.txt" because $APP = Trilium) but it seems that there is still something wrong. `environment: line 32: RELEASE: unbound variable` > > Maybe I'm wrong but in the /ct/trilium.sh script the RELEASE variable is accessed before it's set and thats why the error pops up: also the line number 32 would match the follwing first line > > ``` > > if [[ "${RELEASE}" != "$(cat /opt/${APP}_version.txt)" ]] || [[ ! -f /opt/${APP}_version.txt ]]; then > > RELEASE=$(curl -s https://api.github.com/repos/TriliumNext/Notes/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }') > > ``` > > easy, thats fixed. Added another PR for a missing ";" after your change...
OVERLORD commented 2026-02-04 18:46:26 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 13, 2025):

done and closed

@MickLesk commented on GitHub (Feb 13, 2025): done and closed
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 question
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#419
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?