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

Stuck at 2.0.1 #2288

New Issue
Closed
opened 2025-11-20 05:26:50 -05:00 by saavagebueno · 8 comments
saavagebueno commented 2025-11-20 05:26:50 -05:00
Owner
Copy Link

Originally created by @vascozorrinho on GitHub (Nov 10, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Uptime Kuma

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

8.4.14

📝 Provide a clear and concise description of the issue.

I've installed this LCX container and the installed Uptime Kuma was 2.0.1.

I've tried to update to 2.0.2 running the update command or running the bash command again. In both cases i go Yes silent option. At the end of the execution is says the update to 2.0.2 is a success.

Even after rebooting the container the interface keeps showing I'm in the 2.0.1 version

🔄 Steps to reproduce the issue.

update

❌ Paste the full error output (if available).

No error is displayed

🖼️ Additional context (optional).

No response

Originally created by @vascozorrinho on GitHub (Nov 10, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Uptime Kuma ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/uptimekuma.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 8.4.14 ### 📝 Provide a clear and concise description of the issue. I've installed this LCX container and the installed Uptime Kuma was 2.0.1. I've tried to update to 2.0.2 running the update command or running the bash command again. In both cases i go Yes silent option. At the end of the execution is says the update to 2.0.2 is a success. Even after rebooting the container the interface keeps showing I'm in the 2.0.1 version ### 🔄 Steps to reproduce the issue. update ### ❌ Paste the full error output (if available). No error is displayed ### 🖼️ Additional context (optional). _No response_
saavagebueno added the not a script issuebug labels 2025-11-20 05:26:50 -05:00
saavagebueno commented 2025-11-20 05:26:51 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 10, 2025):

its an upstream error, they dont have updated the version file. the tool do what it do. Its not an script issue.

If you really want to force it again, go to /root/.uptime-kuma and edit the file, then run update.

@MickLesk commented on GitHub (Nov 10, 2025): its an upstream error, they dont have updated the version file. the tool do what it do. Its not an script issue. If you really want to force it again, go to /root/.uptime-kuma and edit the file, then run update.
saavagebueno commented 2025-11-20 05:26:51 -05:00
Author
Owner
Copy Link

@vascozorrinho commented on GitHub (Nov 10, 2025):

that file already says 2.0.2. what am i missing?

EDIT: changed it to 2.0.1 and run the update again. the update went through but GUI still says 2.0.1

@vascozorrinho commented on GitHub (Nov 10, 2025): that file already says 2.0.2. what am i missing? EDIT: changed it to 2.0.1 and run the update again. the update went through but GUI still says 2.0.1
saavagebueno commented 2025-11-20 05:26:52 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Nov 10, 2025):

As Mick mentioned, they did not update the File where the WebGui gets the Version from. What are we supposed to then?

@michelroegl-brunner commented on GitHub (Nov 10, 2025): As Mick mentioned, they did not update the File where the WebGui gets the Version from. What are we supposed to then?
saavagebueno commented 2025-11-20 05:26:52 -05:00
Author
Owner
Copy Link

@vascozorrinho commented on GitHub (Nov 10, 2025):

Is that a question for me? IDK.. probably not much, but i thought there was a solution

"If you really want to force it again, go to /root/.uptime-kuma and edit the file, then run update."

Also, why does the script says it did the update?

@vascozorrinho commented on GitHub (Nov 10, 2025): Is that a question for me? IDK.. probably not much, but i thought there was a solution "If you really want to force it again, go to /root/.uptime-kuma and edit the file, then run update." Also, why does the script says it did the update?
saavagebueno commented 2025-11-20 05:26:52 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 10, 2025):

..... What don't you understand about it being an upstream issue? That was just to force it so you could see that it's not the update's fault.

@MickLesk commented on GitHub (Nov 10, 2025): ..... What don't you understand about it being an upstream issue? That was just to force it so you could see that it's not the update's fault.
saavagebueno commented 2025-11-20 05:26:52 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Nov 10, 2025):

Is that a question for me? IDK.. probably not much, but i thought there was a solution

"If you really want to force it again, go to /root/.uptime-kuma and edit the file, then run update."

Also, why does the script says it did the update?

It sayes it updated becouse it dose. It is a File wich gets provide by uptime-kuma wich has the version in it. Adn this file simply has the wrong version written to it. that is why you see the old version. That is why we are telling you we can not do anything here.

@michelroegl-brunner commented on GitHub (Nov 10, 2025): > Is that a question for me? IDK.. probably not much, but i thought there was a solution > > "If you really want to force it again, go to /root/.uptime-kuma and edit the file, then run update." > > Also, why does the script says it did the update? It sayes it updated becouse it dose. It is a File wich gets provide by uptime-kuma wich has the version in it. Adn this file simply has the wrong version written to it. that is why you see the old version. That is why we are telling you we can not do anything here.
saavagebueno commented 2025-11-20 05:26:52 -05:00
Author
Owner
Copy Link

@vascozorrinho commented on GitHub (Nov 10, 2025):

@MickLesk i just understood you were providing me a workaround.. no need to be salty about that

@vascozorrinho commented on GitHub (Nov 10, 2025): @MickLesk i just understood you were providing me a workaround.. no need to be salty about that
saavagebueno commented 2025-11-20 05:26:52 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 10, 2025):

New Install
=>

Image

they dont have updated their file

@MickLesk commented on GitHub (Nov 10, 2025): New Install => <img width="399" height="246" alt="Image" src="https://github.com/user-attachments/assets/ecf6248d-8086-44f8-a532-60518443150e" /> they dont have updated their file
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 not a script issue
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#2288
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?