starred/ProxmoxVE

Fork 0

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

[GH-ISSUE #8253] Uptimekuma fails to create LXC #1766

New issue

Closed

opened 2026-02-26 12:50:09 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @briodan on GitHub (Oct 10, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/8253

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

default

📈 Which Proxmox version are you on?

pve-manager/8.2.6/414ce79a1d42d6bc (running kernel: 6.8.12-1-pve)

📝 Provide a clear and concise description of the issue.

LXC creation fails in both default and advanced mode

🔄 Steps to reproduce the issue.

run script in default mode:

advanced mode:

set disk to 10G
set vlan
everything else default

❌ Paste the full error output (if available).

🖥️ Operating System: debian
🌟 Version: 13
📦 Container Type: Unprivileged
🔐 Root Password: ********
🆔 Container ID: 113
🏠 Hostname: uptimekuma
💾 Disk Size: 10 GB
🧠 CPU Cores: 1
🛠️ RAM Size: 1024 MiB
🌉 Bridge: vmbr0
📡 IPv4: DHCP
📡 IPv6: SLAAC/AUTO
📡 APT-Cacher IP Address: Default
⚙️ Interface MTU Size: Default
🔍 DNS Search Domain: Host
📡 DNS Server IP Address: Host
🏷️ Vlan: 10
📡 Tags: community-script;analytics;monitoring
🔑 Root SSH Access: yes
🗂️ Enable FUSE Support: no
🔍 Verbose Mode: yes
🚀 Creating a Uptime Kuma LXC using the above advanced settings
💡 Writing configuration to /opt/community-scripts/uptimekuma.conf
✔️ Storage NAS-Data (Free: 53.2GB Used: 40.7GB) [Template]
✔️ Storage vm-disks (Free: 454.6GB Used: 411.6GB) [Container]
✔️ Cluster is quorate
✔️ Template debian-13-standard_13.1-2_amd64.tar.zst [local]
✖️ Container creation failed. Checking if template is corrupted or incomplete.
✖️ Template is valid, but container creation still failed.

[ERROR] in line 1152: exit code 0: while executing command bash -c "(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" ?

🖼️ Additional context (optional).

No response

Originally created by @briodan on GitHub (Oct 10, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/8253 ### ✅ 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? default ### 📈 Which Proxmox version are you on? pve-manager/8.2.6/414ce79a1d42d6bc (running kernel: 6.8.12-1-pve) ### 📝 Provide a clear and concise description of the issue. LXC creation fails in both default and advanced mode ### 🔄 Steps to reproduce the issue. run script in default mode: advanced mode: - set disk to 10G - set vlan - everything else default ### ❌ Paste the full error output (if available). 🖥️ Operating System: debian 🌟 Version: 13 📦 Container Type: Unprivileged 🔐 Root Password: ******** 🆔 Container ID: 113 🏠 Hostname: uptimekuma 💾 Disk Size: 10 GB 🧠 CPU Cores: 1 🛠️ RAM Size: 1024 MiB 🌉 Bridge: vmbr0 📡 IPv4: DHCP 📡 IPv6: SLAAC/AUTO 📡 APT-Cacher IP Address: Default ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: 10 📡 Tags: community-script;analytics;monitoring 🔑 Root SSH Access: yes 🗂️ Enable FUSE Support: no 🔍 Verbose Mode: yes 🚀 Creating a Uptime Kuma LXC using the above advanced settings 💡 Writing configuration to /opt/community-scripts/uptimekuma.conf ✔️ Storage NAS-Data (Free: 53.2GB Used: 40.7GB) [Template] ✔️ Storage vm-disks (Free: 454.6GB Used: 411.6GB) [Container] ✔️ Cluster is quorate ✔️ Template debian-13-standard_13.1-2_amd64.tar.zst [local] ✖️ Container creation failed. Checking if template is corrupted or incomplete. ✖️ Template is valid, but container creation still failed. [ERROR] in line 1152: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" $? ### 🖼️ Additional context (optional). _No response_

kerem

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

closed this issue
added the
not a script issue

🛑 Failure to comply with the guidelines
labels

kerem commented

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

Author

Owner

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

#8216

@MickLesk commented on GitHub (Oct 10, 2025): #8216

kerem commented

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

Author

Owner

@briodan commented on GitHub (Oct 10, 2025):

#8216

that PR has nothing to do with uptime kuma, its related to rwmarkable

@briodan commented on GitHub (Oct 10, 2025): > [#8216](https://github.com/community-scripts/ProxmoxVE/pull/8216) that PR has nothing to do with uptime kuma, its related to rwmarkable

kerem commented

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

Author

Owner

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

#8126

Typo

But next time use search function for this issue, its answered round about 70 times

@MickLesk commented on GitHub (Oct 10, 2025): #8126 Typo But next time use search function for this issue, its answered round about 70 times

kerem referenced this issue

2026-02-26 13:33:13 +03:00

[PR #1766] [MERGED] openHAB - Use https and include doc url #3342

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

No description provided.

Rows
Columns