starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Stuck at 2.0.1 #1972

New Issue
Closed
opened 2026-02-05 03:07:45 +03:00 by OVERLORD · 11 comments
OVERLORD commented 2026-02-05 03:07:45 +03: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_
OVERLORD added the not a script issuebug labels 2026-02-05 03:07:45 +03:00
OVERLORD commented 2026-02-05 03:07:51 +03: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.
OVERLORD commented 2026-02-05 03:07:53 +03: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
OVERLORD commented 2026-02-05 03:07:55 +03: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?
OVERLORD commented 2026-02-05 03:07:58 +03: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?
OVERLORD commented 2026-02-05 03:08:02 +03: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.
OVERLORD commented 2026-02-05 03:08:05 +03: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.
OVERLORD commented 2026-02-05 03:08:08 +03: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
OVERLORD commented 2026-02-05 03:08:12 +03: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
OVERLORD commented 2026-02-05 03:08:15 +03:00
Author
Owner
Copy Link

@7adityaraj commented on GitHub (Nov 22, 2025):

Hello @MickLesk @vascozorrinho @michelroegl-brunner,

I was trying to troubleshoot the update cmd in verbose mode, and found that the script located at /opt/uptime-kuma/extra/download-dist.js is trying to download version from file package.json["version"] .

As we can find below, while its trying to install 2.0.2, the dist cmd pulls 2.0.1 version

25 packages are looking for funding
  run `npm fund` for details
  ✔️   Update Node.js 22
  ✔️   Update available: uptime-kuma not installed → 2.0.2
  ✔️   Stopped Service
  ✔️   Deployed: uptime-kuma (2.0.2)

up to date, audited 692 packages in 2s

104 packages are looking for funding
  run `npm fund` for details

3 vulnerabilities (1 moderate, 2 high)

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

> uptime-kuma@2.0.1 download-dist
> node extra/download-dist.js

Downloading dist

https://github.com/louislam/uptime-kuma/releases/download/2.0.1/dist.tar.gz
                                                           ^^^
.....

Extracting dist...
Done
  ✔️   Updated Uptime Kuma
  ✔️   Started Service
  ✔️   Updated successfully!


####

root@uptimekuma:~# cat /opt/uptime-kuma/extra/download-dist.js

console.log("Downloading dist");
const https = require("https");
const tar = require("tar");

const packageJSON = require("../package.json");
const fs = require("fs");
const version = packageJSON.version;

const filename = "dist.tar.gz";

const url = `https://github.com/louislam/uptime-kuma/releases/download/${version}/${filename}`;
download(url);

/**
 * Downloads the latest version of the dist from a GitHub release.
 * @param {string} url The URL to download from.
 * @returns {void}
 *
 * Generated by Trelent
 */
function download(url) {
    console.log(url);

    https.get(url, (response) => {
        if (response.statusCode === 200) {
            console.log("Extracting dist...");

            ........redacted...
    });
}

I am not sure what could the order to update the package.json, but there is something that we can look into, either pull the latest version from github release as mentioned in the script instead of local package.json file or update the package json file before running the dist script. Not sure what the best way but if someone could advise on this.

Btw, udpating the .uptime-kuma file in root dir doesn't have any affect, i tried even adding higer version or lower version and even deleting the file, no affect

And yes, in the uptime repo https://github.com/louislam/uptime-kuma/blob/2.0.2/package.json still points to 2.0.1

@7adityaraj commented on GitHub (Nov 22, 2025): Hello @MickLesk @vascozorrinho @michelroegl-brunner, I was trying to troubleshoot the update cmd in verbose mode, and found that the script located at `/opt/uptime-kuma/extra/download-dist.js` is trying to download version from file `package.json["version"]` . As we can find below, while its trying to install `2.0.2`, the dist cmd pulls `2.0.1` version ``` 25 packages are looking for funding run `npm fund` for details ✔️ Update Node.js 22 ✔️ Update available: uptime-kuma not installed → 2.0.2 ✔️ Stopped Service ✔️ Deployed: uptime-kuma (2.0.2) up to date, audited 692 packages in 2s 104 packages are looking for funding run `npm fund` for details 3 vulnerabilities (1 moderate, 2 high) To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. > uptime-kuma@2.0.1 download-dist > node extra/download-dist.js Downloading dist https://github.com/louislam/uptime-kuma/releases/download/2.0.1/dist.tar.gz ^^^ ..... Extracting dist... Done ✔️ Updated Uptime Kuma ✔️ Started Service ✔️ Updated successfully! #### root@uptimekuma:~# cat /opt/uptime-kuma/extra/download-dist.js console.log("Downloading dist"); const https = require("https"); const tar = require("tar"); const packageJSON = require("../package.json"); const fs = require("fs"); const version = packageJSON.version; const filename = "dist.tar.gz"; const url = `https://github.com/louislam/uptime-kuma/releases/download/${version}/${filename}`; download(url); /** * Downloads the latest version of the dist from a GitHub release. * @param {string} url The URL to download from. * @returns {void} * * Generated by Trelent */ function download(url) { console.log(url); https.get(url, (response) => { if (response.statusCode === 200) { console.log("Extracting dist..."); ........redacted... }); } ``` I am not sure what could the order to update the package.json, but there is something that we can look into, either pull the latest version from github release as mentioned in the script instead of local package.json file or update the package json file before running the dist script. Not sure what the best way but if someone could advise on this. Btw, udpating the .uptime-kuma file in root dir doesn't have any affect, i tried even adding higer version or lower version and even deleting the file, no affect And yes, in the uptime repo https://github.com/louislam/uptime-kuma/blob/2.0.2/package.json still points to 2.0.1
OVERLORD commented 2026-02-05 03:08:19 +03:00
Author
Owner
Copy Link

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

Uptime Kuma’s upstream 2.0.2 release still ships a package.json with version 2.0.1.
The download-dist.js script always pulls the version defined in package.json, not the GitHub tag.
Our installer always fetches the latest tarball correctly, but the dist step inside Kuma pulls the wrong file because upstream didn’t update their version field.

We will not patch or fake upstream files.
This needs to be corrected in the Uptime Kuma repository itself — there is nothing the script can safely “fix”, because it would mean modifying upstream source code.

So yes:
=> Update works
=> Latest tarball is deployed
=> Version mismatch is upstream and must be reported there

Once they release a correct package.json, everything will update cleanly again.

package.json

@MickLesk commented on GitHub (Nov 22, 2025): Uptime Kuma’s upstream 2.0.2 release still ships a package.json with version 2.0.1. The download-dist.js script always pulls the version defined in package.json, not the GitHub tag. Our installer always fetches the latest tarball correctly, but the dist step inside Kuma pulls the wrong file because upstream didn’t update their version field. We will not patch or fake upstream files. This needs to be corrected in the Uptime Kuma repository itself — there is nothing the script can safely “fix”, because it would mean modifying upstream source code. So yes: => Update works => Latest tarball is deployed => Version mismatch is upstream and must be reported there Once they release a correct package.json, everything will update cleanly again. [package.json](https://github.com/user-attachments/files/23689193/package.json)
OVERLORD commented 2026-02-05 03:08:25 +03:00
Author
Owner
Copy Link

@7adityaraj commented on GitHub (Nov 22, 2025):

yes @MickLesk i update that in my post as well,

And yes, in the uptime repo https://github.com/louislam/uptime-kuma/blob/2.0.2/package.json still points to 2.0.1

Thanks for explaining this, and is there workaround untill they fix it, I am going to add this issue in their issue as well

update: issue is already there:

https://github.com/louislam/uptime-kuma/issues/6383

https://github.com/louislam/uptime-kuma/issues/6255

@7adityaraj commented on GitHub (Nov 22, 2025): yes @MickLesk i update that in my post as well, > And yes, in the uptime repo https://github.com/louislam/uptime-kuma/blob/2.0.2/package.json still points to 2.0.1 Thanks for explaining this, and is there workaround untill they fix it, I am going to add this issue in their issue as well update: issue is already there: https://github.com/louislam/uptime-kuma/issues/6383 https://github.com/louislam/uptime-kuma/issues/6255
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label bug not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1972
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?