starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 09:15:59 +03:00

[GH-ISSUE #958] Navidrome update fails #207

New issue

Closed

opened 2026-02-26 12:44:44 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 12:44:44 +03:00

Owner

Originally created by @symphonyalpha on GitHub (Dec 21, 2024).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/958

✅ Have you read and understood the above guidelines?

yes

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

Navidrome

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

update

📝 Provide a clear and concise description of the issue.

When updating an existing Navidrome container, the script does not perform a chmod +x on the new binary which prevents the Navidrome service from starting up.

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Run update in an already created container.

❌ Paste the full error output (if available).

Nil

🖼️ Additional context (optional).

github.com/community-scripts/ProxmoxVE@67a0c06b80/ct/navidrome.sh (L41-L42)

I've tested running the above commands from the script manually but the new binary still does not have the executable flag set which prevents the Navidrome service from starting.

Relevant screenshot:

Originally created by @symphonyalpha on GitHub (Dec 21, 2024). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/958 ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Navidrome ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. When updating an existing Navidrome container, the script does not perform a `chmod +x` on the new binary which prevents the Navidrome service from starting up. ### ⚙️ What settings are you using? - [ ] Default Settings - [X] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Run `update` in an already created container. ### ❌ Paste the full error output (if available). Nil ### 🖼️ Additional context (optional). https://github.com/community-scripts/ProxmoxVE/blob/67a0c06b806aff58688d1bf9dd6c9ff5564a771e/ct/navidrome.sh#L41-L42 I've tested running the above commands from the script manually but the new binary still does not have the executable flag set which prevents the Navidrome service from starting. Relevant screenshot: ![image](https://github.com/user-attachments/assets/4b939770-78bc-4405-9404-048f77bf39a3)

kerem

2026-02-26 12:44:44 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:44:44 +03:00

Author

Owner

@ehcloninger commented on GitHub (Dec 21, 2024):

I tried to create a new LXC from navidrome today and this may be the same problem. The container was created, but there was no navidrome.service created from the contents of /opt/navidrome. I had previously created containers from the scripts for calibre-web and audiobookshelf from the scripts in the last 2 days, so this may be unique to the navidrome script.

@ehcloninger commented on GitHub (Dec 21, 2024): I tried to create a new LXC from navidrome today and this may be the same problem. The container was created, but there was no navidrome.service created from the contents of /opt/navidrome. I had previously created containers from the scripts for calibre-web and audiobookshelf from the scripts in the last 2 days, so this may be unique to the navidrome script.

kerem commented

2026-02-26 12:44:44 +03:00

Author

Owner

@MickLesk commented on GitHub (Dec 22, 2024):

Can you test the dev branch?

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

@MickLesk commented on GitHub (Dec 22, 2024): Can you test the dev branch? ```bash bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/develop/ct/navidrome.sh)" ```

kerem commented

2026-02-26 12:44:44 +03:00

Author

Owner

@symphonyalpha commented on GitHub (Dec 22, 2024):

Just tried it and Navidrome was able to start up fine after the update!

@symphonyalpha commented on GitHub (Dec 22, 2024): Just tried it and Navidrome was able to start up fine after the update! ![image](https://github.com/user-attachments/assets/81a175d1-cb6c-46b9-ba84-080bfc108e9a)

kerem commented

2026-02-26 12:44:44 +03:00

Author

Owner

@MickLesk commented on GitHub (Dec 22, 2024):

Okay fine, im not on PC today, i prepare the PR tomorrow

@MickLesk commented on GitHub (Dec 22, 2024): Okay fine, im not on PC today, i prepare the PR tomorrow

kerem commented

2026-02-26 12:44:44 +03:00

Author

Owner

@ehcloninger commented on GitHub (Dec 22, 2024):

@MickLesk I can also confirm that it worked on a new install where yesterday the script in main did not. Thanks!

@ehcloninger commented on GitHub (Dec 22, 2024): @MickLesk I can also confirm that it worked on a new install where yesterday the script in `main` did not. Thanks!

kerem commented

2026-02-26 12:44:44 +03:00

Author

Owner

@arnob216 commented on GitHub (Dec 23, 2024):

Yap, main script is not working, update or fresh.

@arnob216 commented on GitHub (Dec 23, 2024): Yap, main script is not working, update or fresh.

kerem referenced this issue

2026-02-26 13:31:19 +03:00

[PR #546] [MERGED] Fix Z-Wave JS UI script #2774

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#207

No description provided.

Rows
Columns