SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Kavita upgrade script missing chmod +x step #2179

New Issue
Closed
opened 2025-11-20 05:24:45 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:24:45 -05:00
Owner
Copy Link

Originally created by @ponchohoncho on GitHub (Oct 23, 2025).

Originally assigned to: @tremor021 on GitHub.

✅ Have you read and understood the above guidelines?

yes

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

Kavita

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

8.4

📝 Provide a clear and concise description of the issue.

When I upgraded my Kavita instance to 0.8.8 it wouldn't start back up and the service talked about its permission being denied. The Kavita upgrade script seems to be missing a chmod+x step to make the Kavita binary executable after unzipping and moving it into place.

it would happen in this block around line 34

    rm -rf Kavita/config
    cp -r Kavita/* /opt/Kavita
    rm -rf Kavita

you'd add a line like
chmod +x /opt/Kavita/Kavita

The native install docs for Linux refer to that step: https://wiki.kavitareader.com/installation/native/
And the community-scripts installer has a chmod +x step also (though it seems excessive to +x the whole dir?)

🔄 Steps to reproduce the issue.

  • Have an outdated Kavita install
  • Run the upgrade script from the shell
  • Have Kavita not start back up

❌ Paste the full error output (if available).

I'm sorry, I fixed it and didn't preserve the original error message

🖼️ Additional context (optional).

No response

Originally created by @ponchohoncho on GitHub (Oct 23, 2025). Originally assigned to: @tremor021 on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Kavita ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/kavita.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 8.4 ### 📝 Provide a clear and concise description of the issue. When I upgraded my Kavita instance to 0.8.8 it wouldn't start back up and the service talked about its permission being denied. The Kavita upgrade script seems to be missing a chmod+x step to make the Kavita binary executable after unzipping and moving it into place. it would happen in this block around line 34 ``` rm -rf Kavita/config cp -r Kavita/* /opt/Kavita rm -rf Kavita ``` you'd add a line like `chmod +x /opt/Kavita/Kavita` The native install docs for Linux refer to that step: https://wiki.kavitareader.com/installation/native/ And the community-scripts installer has a chmod +x step also (though it seems excessive to +x the whole dir?) ### 🔄 Steps to reproduce the issue. - Have an outdated Kavita install - Run the upgrade script from the shell - Have Kavita not start back up ### ❌ Paste the full error output (if available). I'm sorry, I fixed it and didn't preserve the original error message ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:24:45 -05:00
saavagebueno commented 2025-11-20 05:24:45 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 23, 2025):

This script will get a refactor probably today. So after PR merges, it will be fixed

@tremor021 commented on GitHub (Oct 23, 2025): This script will get a refactor probably today. So after PR merges, it will be fixed
saavagebueno commented 2025-11-20 05:24:46 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 23, 2025):

im always done @tremor021

@MickLesk commented on GitHub (Oct 23, 2025): im always done @tremor021
saavagebueno commented 2025-11-20 05:24:46 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 23, 2025):

done

@MickLesk commented on GitHub (Oct 23, 2025): done
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#2179
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?