ProxmoxVE: Trilium LXC does not update correctly

โœ… 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

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 42 (20 by maintainers)

Most upvoted comments

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)"

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.

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

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) }')

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!

no its marked as breaking change since weeks

touch /opt/TrilliumNext_version.txt

Create an empty File with Touch there

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

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.

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

Image

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.