[GH-ISSUE #9988] Uptime-Kuma installation is 2.0.1 although it should be 2.0.2 #2172

Closed
opened 2026-02-26 12:51:33 +03:00 by kerem · 1 comment
Owner

Originally created by @BlaShDD on GitHub (Dec 15, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9988

Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 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?

9.1.1

📝 Provide a clear and concise description of the issue.

Uptime-Kuma version 2.0.1 is installed, although the website and the scipt say that 2.0.2 is installed. An update trigger also says that UK is up to date with 2.0.2.
The UK webfrontend displays an available update.

verbose output during installation:

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

🔄 Steps to reproduce the issue.

simple installation

Paste the full error output (if available).

run npm fund for details
✔️ Update Node.js 22
✔️ No update available: uptime-kuma (2.0.2)

🖼️ Additional context (optional).

No response

Originally created by @BlaShDD on GitHub (Dec 15, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9988 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 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? 9.1.1 ### 📝 Provide a clear and concise description of the issue. Uptime-Kuma version 2.0.1 is installed, although the website and the scipt say that 2.0.2 is installed. An update trigger also says that UK is up to date with 2.0.2. The UK webfrontend displays an available update. verbose output during installation: >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 ### 🔄 Steps to reproduce the issue. simple installation ### ❌ Paste the full error output (if available). > run `npm fund` for details > ✔️ Update Node.js 22 > ✔️ No update available: uptime-kuma (2.0.2) ### 🖼️ Additional context (optional). _No response_
Author
Owner
<!-- gh-comment-id:3655792014 --> @MickLesk commented on GitHub (Dec 15, 2025): https://github.com/community-scripts/ProxmoxVE/discussions/3454 https://github.com/community-scripts/ProxmoxVE/issues/9025 https://github.com/community-scripts/ProxmoxVE/issues/8616 https://github.com/community-scripts/ProxmoxVE/issues/8462
Sign in to join this conversation.
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#2172
No description provided.