starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 17:26:03 +03:00

[GH-ISSUE #12279] Uptime Kuma upgrade does not work. #2557

New issue

Closed

opened 2026-02-26 12:52:50 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 12:52:50 +03:00

Owner

Originally created by @phellarv on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/12279

✅ 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 12

📈 Which Proxmox version are you on?

pve-manager/8.4.16/368e3c45c15b895c (running kernel: 6.8.12-18-pve)

📝 Provide a clear and concise description of the issue.

I tried to upgrade a Uptime Kuma LXC

🔄 Steps to reproduce the issue.

Run update-script in the LXC

❌ Paste the full error output (if available).

/ / / /___ / /()___ ___ ___ / /// ______ ___ ____ _
/ / / / __ / / / __ __ \/ _ \ / ,< / / / / __ / __ `/
/ // / // / // / / / / / / __/ / /| / // / / / / / / // /
_/ ./_/// // //___/ // |_,// // //_,/
//

Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu jammy-security InRelease
Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

removed 66 packages, and changed 105 packages in 3s

14 packages are looking for funding
run npm fund for details
✔️ Update Node.js 22
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package chromium is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
chromium-bsu

E: Package 'chromium' has no installation candidate
✖️ Failed to install dependencies: chromium
✖️ in line 33: exit code 1 (General error / Operation not permitted): while executing command return 1

--- Last 20 lines of log ---
[2026-02-24 13:51:41] [INFO] Update Node.js 22
[2026-02-24 13:51:47] [OK] Update Node.js 22
[2026-02-24 13:51:48] [ERROR] Failed to install dependencies: chromium
[2026-02-24 13:51:48] [ERROR] in line 33: exit code 1 (General error / Operation not permitted): while executing command return 1

📋 Full log: /tmp/create-lxc-91677caa.log
root@uptimekuma:~# cat /tmp/create-lxc-91677caa.log
[2026-02-24 13:51:41] [INFO] Update Node.js 22
[2026-02-24 13:51:47] [OK] Update Node.js 22
[2026-02-24 13:51:48] [ERROR] Failed to install dependencies: chromium
[2026-02-24 13:51:48] [ERROR] in line 33: exit code 1 (General error / Operation not permitted): while executing command return 1
[2026-02-24 13:51:48] Full log: /tmp/create-lxc-91677caa.log

🖼️ Additional context (optional).

No response

Originally created by @phellarv on GitHub (Feb 24, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/12279 ### ✅ 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? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/8.4.16/368e3c45c15b895c (running kernel: 6.8.12-18-pve) ### 📝 Provide a clear and concise description of the issue. I tried to upgrade a Uptime Kuma LXC ### 🔄 Steps to reproduce the issue. Run update-script in the LXC ### ❌ Paste the full error output (if available). __ __ __ _ __ __ / / / /___ / /_(_)___ ___ ___ / //_/_ ______ ___ ____ _ / / / / __ \/ __/ / __ `__ \/ _ \ / ,< / / / / __ `__ \/ __ `/ / /_/ / /_/ / /_/ / / / / / / __/ / /| / /_/ / / / / / / /_/ / \____/ .___/\__/_/_/ /_/ /_/\___/ /_/ |_\__,_/_/ /_/ /_/\__,_/ /_/ Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy-security InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. removed 66 packages, and changed 105 packages in 3s 14 packages are looking for funding run `npm fund` for details ✔️ Update Node.js 22 Reading package lists... Done Building dependency tree... Done Reading state information... Done Package chromium is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: chromium-bsu E: Package 'chromium' has no installation candidate ✖️ Failed to install dependencies: chromium ✖️ in line 33: exit code 1 (General error / Operation not permitted): while executing command return 1 --- Last 20 lines of log --- [2026-02-24 13:51:41] [INFO] Update Node.js 22 [2026-02-24 13:51:47] [OK] Update Node.js 22 [2026-02-24 13:51:48] [ERROR] Failed to install dependencies: chromium [2026-02-24 13:51:48] [ERROR] in line 33: exit code 1 (General error / Operation not permitted): while executing command return 1 ----------------------------------- 📋 Full log: /tmp/create-lxc-91677caa.log root@uptimekuma:~# cat /tmp/create-lxc-91677caa.log [2026-02-24 13:51:41] [INFO] Update Node.js 22 [2026-02-24 13:51:47] [OK] Update Node.js 22 [2026-02-24 13:51:48] [ERROR] Failed to install dependencies: chromium [2026-02-24 13:51:48] [ERROR] in line 33: exit code 1 (General error / Operation not permitted): while executing command return 1 [2026-02-24 13:51:48] Full log: /tmp/create-lxc-91677caa.log ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:52:50 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:52:50 +03:00

Author

Owner

@MickLesk commented on GitHub (Feb 24, 2026):

ubuntu jammy?
we running uptime kuma with debian trixie. How old is this?

to be honest, you should recreate the container or you try the dirty way:

Upgrade Your OS to Ubuntu 24.04
apt install -y chromium
ln -s /usr/bin/chromium /opt/uptime-kuma/chromium
run update again

@MickLesk commented on GitHub (Feb 24, 2026): ubuntu jammy? we running uptime kuma with debian trixie. How old is this? to be honest, you should recreate the container or you try the dirty way: - Upgrade Your OS to Ubuntu 24.04 - apt install -y chromium - ln -s /usr/bin/chromium /opt/uptime-kuma/chromium - run update again

kerem commented

2026-02-26 12:52:50 +03:00

Author

Owner

@phellarv commented on GitHub (Feb 24, 2026):

I went the recreate path.
backed up /opt/uptime-kuma/data
Created a new LXC
restored /opt/uptime-kuma/data
Voila.

@phellarv commented on GitHub (Feb 24, 2026): I went the recreate path. backed up /opt/uptime-kuma/data Created a new LXC restored /opt/uptime-kuma/data Voila.

kerem referenced this issue

2026-02-26 14:34:42 +03:00

[PR #5575] [MERGED] [core]: add ipv6 configuration support #5613

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#2557

No description provided.

Rows
Columns