Linkwarden LXC update failed #977

Closed
opened 2026-02-04 22:23:23 +03:00 by OVERLORD · 5 comments
Owner

Originally created by @jrycp23nkt on GitHub (May 18, 2025).

Have you read and understood the above guidelines?

yes

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

Linkwarden

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📝 Provide a clear and concise description of the issue.

Hello everyone,

I wanted to update Linkwarden using the “update” command. The process took several hours (I don't know if this is normal) and finally crashed.

Is it possible to do a rollback or just recover the application before crashing (I forgot to make a backup 😅)?

Thanks in advance.

Image
Originally created by @jrycp23nkt on GitHub (May 18, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Linkwarden ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/linkwarden.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. Hello everyone, I wanted to update Linkwarden using the “update” command. The process took several hours (I don't know if this is normal) and finally crashed. Is it possible to do a rollback or just recover the application before crashing (I forgot to make a backup 😅)? Thanks in advance. <img width="655" alt="Image" src="https://github.com/user-attachments/assets/78db740f-7e81-49f0-ab0c-9d0bca384481" />
OVERLORD added the bug label 2026-02-04 22:23:23 +03:00
Author
Owner

@michelroegl-brunner commented on GitHub (May 18, 2025):

No way to roll back from our side. Always backup befor a update

@michelroegl-brunner commented on GitHub (May 18, 2025): No way to roll back from our side. Always backup befor a update
Author
Owner

@jrycp23nkt commented on GitHub (May 18, 2025):

Well, I ran the update command one last time and it finally finished without an error message.

I manage to access Linkwarden but new problem, all images, screenshots, etc ... have disappeared 😅

@jrycp23nkt commented on GitHub (May 18, 2025): Well, I ran the update command one last time and it finally finished without an error message. I manage to access Linkwarden but new problem, all images, screenshots, etc ... have disappeared 😅
Author
Owner

@pmontgo33 commented on GitHub (May 20, 2025):

I am having the same issue. When I run the update script, it fails with the same error, and Linkwarden is stopped. I had to restore from a backup.

@pmontgo33 commented on GitHub (May 20, 2025): I am having the same issue. When I run the update script, it fails with the same error, and Linkwarden is stopped. I had to restore from a backup.
Author
Owner

@pmontgo33 commented on GitHub (May 25, 2025):

Just wondering why this was closed. Was this fixed? I can try updating again to confirm the issue persists if that's helpful

@pmontgo33 commented on GitHub (May 25, 2025): Just wondering why this was closed. Was this fixed? I can try updating again to confirm the issue persists if that's helpful
Author
Owner

@MickLesk commented on GitHub (May 25, 2025):

The General issue is closed. Yours is another. Without Logs / current Version etc. Nobody can Help you.

@MickLesk commented on GitHub (May 25, 2025): The General issue is closed. Yours is another. Without Logs / current Version etc. Nobody can Help you.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#977