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 13 Packages Projects Releases 10 Wiki Activity

Kuma Update Error #1830

New Issue
Closed
opened 2026-02-05 02:22:48 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-05 02:22:48 +03:00
Owner
Copy Link

Originally created by @Zobber on GitHub (Oct 18, 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 12

📈 Which Proxmox version are you on?

8.4.14

📝 Provide a clear and concise description of the issue.

Hi,

I was trying to update my kuma uptime container, but when I ran the update. I currently have Kuma down and haven't been able to fix it.

🔄 Steps to reproduce the issue.

Run update into lxc container

❌ Paste the full error output (if available).

✓ Stopped Uptime Kuma

🖼️ Additional context (optional).

"name": "uptime-kuma",
"version": "1.23.16",
Originally created by @Zobber on GitHub (Oct 18, 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? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 8.4.14 ### 📝 Provide a clear and concise description of the issue. Hi, I was trying to update my **kuma uptime** container, but when I ran the **update**. I currently have Kuma down and haven't been able to fix it. ### 🔄 Steps to reproduce the issue. Run update into lxc container ### ❌ Paste the full error output (if available). ✓ Stopped Uptime Kuma - Pulling Uptime Kuma https://api.github.com/repos/louislam/uptime-kuma/releases/191803854 [ERROR] in line 75: exit code 0: while executing command git checkout $LATEST --force &> /dev/null ### 🖼️ Additional context (optional). "name": "uptime-kuma", "version": "1.23.16",
OVERLORD added the bug label 2026-02-05 02:22:48 +03:00
OVERLORD commented 2026-02-05 02:23:01 +03:00
Author
Owner
Copy Link

@Zobber commented on GitHub (Oct 18, 2025):

Update

I tried restarting and ran the “update” command again, and the message did not reappear, which means that sometimes it does generate an error. I started the service manually with systemctl, and the service is working correctly.

@Zobber commented on GitHub (Oct 18, 2025): *Update* I tried restarting and ran the “**update**” command again, and the message did not reappear, which means that sometimes it does generate an error. I started the service manually with systemctl, and the service is working correctly.
OVERLORD commented 2026-02-05 02:23:04 +03:00
Author
Owner
Copy Link

@chrsgrhm commented on GitHub (Nov 12, 2025):

I had the same issue, and I rebooted and reran "update" and it did not work. My web page never returned to let me know it was migrating, but I saw the CPU % go up significantly. I let it run over night, and it was still not working this morning. Systemctl shows it is just looping.

So, I attempted to follow these instructions: https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2#migration-steps-non-docker. It worked well, but I'm not sure if it breaks any part of the Community Scripts workflow. When following those steps, I was able to view the migration status by going to http://0.0.0.0:3001/migrate-status.
Note: the Community Scripts install does not use pm2, so use systemctl to stop and start the process.

@tremor021 So, I'd say the update feature is still not working with this, as you have to migrate or reinstall a new version.

@chrsgrhm commented on GitHub (Nov 12, 2025): I had the same issue, and I rebooted and reran "update" and it did not work. My web page never returned to let me know it was migrating, but I saw the CPU % go up significantly. I let it run over night, and it was still not working this morning. Systemctl shows it is just looping. So, I attempted to follow these instructions: https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2#migration-steps-non-docker. It worked well, but I'm not sure if it breaks any part of the Community Scripts workflow. When following those steps, I was able to view the migration status by going to http://0.0.0.0:3001/migrate-status. Note: the Community Scripts install does not use pm2, so use systemctl to stop and start the process. @tremor021 So, I'd say the update feature is still not working with this, as you have to migrate or reinstall a new version.
OVERLORD commented 2026-02-05 02:23:06 +03:00
Author
Owner
Copy Link

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

... lol, git :-D and broken all

@MickLesk commented on GitHub (Nov 12, 2025): ... lol, git :-D and broken all
OVERLORD commented 2026-02-05 02:23:08 +03:00
Author
Owner
Copy Link

@chrsgrhm commented on GitHub (Nov 12, 2025):

... lol, git :-D and broken all

Should I open a new issue or do you think we should reopen this one?
FYI, I have the same setup and exact same issues as OP.

@chrsgrhm commented on GitHub (Nov 12, 2025): > ... lol, git :-D and broken all Should I open a new issue or do you think we should reopen this one? FYI, I have the same setup and exact same issues as OP.
OVERLORD commented 2026-02-05 02:23:10 +03:00
Author
Owner
Copy Link

@dynamicpete commented on GitHub (Dec 7, 2025):

I have exactly the same problem. Still waiting for any solution :(
I'm not allowed to reopens this issue, so probably we should create a new one...

@dynamicpete commented on GitHub (Dec 7, 2025): I have exactly the same problem. Still waiting for any solution :( I'm not allowed to reopens this issue, so probably we should create a new one...
OVERLORD commented 2026-02-05 02:23:12 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 7, 2025):

Why? Its Not an issue from us.. damn Ive already explained several times that the upstream is pulling the wrong file. This is also known there and has already been fixed for the next version.

@MickLesk commented on GitHub (Dec 7, 2025): Why? Its Not an issue from us.. damn Ive already explained several times that the upstream is pulling the wrong file. This is also known there and has already been fixed for the next version.
OVERLORD commented 2026-02-05 02:23:15 +03:00
Author
Owner
Copy Link

@chrsgrhm commented on GitHub (Dec 8, 2025):

Why? Its Not an issue from us.. damn Ive already explained several times that the upstream is pulling the wrong file. This is also known there and has already been fixed for the next version.

You have explained nothing on this case.

@chrsgrhm commented on GitHub (Dec 8, 2025): > Why? Its Not an issue from us.. damn Ive already explained several times that the upstream is pulling the wrong file. This is also known there and has already been fixed for the next version. You have explained nothing on this case.
OVERLORD commented 2026-02-05 02:23:20 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 8, 2025):

Why? Its Not an issue from us.. damn Ive already explained several times that the upstream is pulling the wrong file. This is also known there and has already been fixed for the next version.

You have explained nothing on this case.

No, I'm writing this for fun, because I would never explain anything.
https://github.com/community-scripts/ProxmoxVE/issues/9025
https://github.com/community-scripts/ProxmoxVE/issues/8616

=> https://github.com/community-scripts/ProxmoxVE/issues/9025#issuecomment-3566690108

@MickLesk commented on GitHub (Dec 8, 2025): > > Why? Its Not an issue from us.. damn Ive already explained several times that the upstream is pulling the wrong file. This is also known there and has already been fixed for the next version. > > You have explained nothing on this case. No, I'm writing this for fun, because I would never explain anything. https://github.com/community-scripts/ProxmoxVE/issues/9025 https://github.com/community-scripts/ProxmoxVE/issues/8616 => https://github.com/community-scripts/ProxmoxVE/issues/9025#issuecomment-3566690108
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
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#1830
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?