[GH-ISSUE #5290] [Zigbee2MQTT] Advanced Settings results in [ERROR] in line 1127: exit code 0 #1117

Closed
opened 2026-02-26 12:47:46 +03:00 by kerem · 4 comments
Owner

Originally created by @benjamin-dcs on GitHub (Jun 19, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/5290

Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Zigbee2MQTT

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/zigbee2mqtt.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Creating the LXC with default setting does work. Using advanced settings results in the following:

🧩 Using Advanced Settings on node pve
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Privileged
🔐 Root Password: ********
🆔 Container ID: 9102
🏠 Hostname: zigbee2mqtt_poe
💾 Disk Size: 4 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 1024 MiB
🌉 Bridge: vmbr0
📡 IP Address: dhcp
🌐 Gateway IP Address: Default
📡 APT-Cacher IP Address: Default
🚫 Disable IPv6: yes
⚙️ Interface MTU Size: Default
🔍 DNS Search Domain: Host
📡 DNS Server IP Address: Host
🏷️ Vlan: Default
📡 Tags: community-script;smarthome;zigbee;mqtt
🔑 Root SSH Access: yes
🗂️ Enable FUSE Support: no
🔍 Verbose Mode: no
🚀 Creating a Zigbee2MQTT LXC using the above advanced settings
✔️ Using local for Template Storage.
✔️ Using local for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Template is ready to use.
✖️ Container creation failed. Checking if template is corrupted.
✖️ Container creation failed, but template is not corrupted.

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

🔄 Steps to reproduce the issue.

Paste the full error output (if available).

🖼️ Additional context (optional).

Image

Originally created by @benjamin-dcs on GitHub (Jun 19, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/5290 ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Zigbee2MQTT ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/zigbee2mqtt.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Creating the LXC with default setting does work. Using advanced settings results in the following: 🧩 Using Advanced Settings on node pve 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Privileged 🔐 Root Password: ******** 🆔 Container ID: 9102 🏠 Hostname: zigbee2mqtt_poe 💾 Disk Size: 4 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 1024 MiB 🌉 Bridge: vmbr0 📡 IP Address: dhcp 🌐 Gateway IP Address: Default 📡 APT-Cacher IP Address: Default 🚫 Disable IPv6: yes ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: community-script;smarthome;zigbee;mqtt 🔑 Root SSH Access: yes 🗂️ Enable FUSE Support: no 🔍 Verbose Mode: no 🚀 Creating a Zigbee2MQTT LXC using the above advanced settings ✔️ Using local for Template Storage. ✔️ Using local for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✖️ Container creation failed. Checking if template is corrupted. ✖️ Container creation failed, but template is not corrupted. [ERROR] in line 1127: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/create_lxc.sh)" $? ### 🔄 Steps to reproduce the issue. - ### ❌ Paste the full error output (if available). - ### 🖼️ Additional context (optional). ![Image](https://github.com/user-attachments/assets/821b77b4-1cbb-48cf-a4a6-0a9b8e358261)
kerem 2026-02-26 12:47:46 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@MickLesk commented on GitHub (Jun 19, 2025):

No Network on LXC - maybe the underline in hostname

<!-- gh-comment-id:2988232553 --> @MickLesk commented on GitHub (Jun 19, 2025): No Network on LXC - maybe the underline in hostname
Author
Owner

@benjamin-dcs commented on GitHub (Jun 19, 2025):

spot-on! zigbee2mqtt-poe works. Thanks for the crazy fast respons!

<!-- gh-comment-id:2988245932 --> @benjamin-dcs commented on GitHub (Jun 19, 2025): spot-on! `zigbee2mqtt-poe` works. Thanks for the crazy fast respons!
Author
Owner

@MickLesk commented on GitHub (Jun 19, 2025):

I build an check for this in next PR

<!-- gh-comment-id:2988291221 --> @MickLesk commented on GitHub (Jun 19, 2025): I build an check for this in next PR
Author
Owner

@MickLesk commented on GitHub (Jun 19, 2025):

fixed with next pr for all guys

<!-- gh-comment-id:2988420109 --> @MickLesk commented on GitHub (Jun 19, 2025): fixed with next pr for all guys
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#1117
No description provided.