SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

[Zigbee2MQTT] Advanced Settings results in [ERROR] in line 1127: exit code 0 #1296

New Issue
Closed
opened 2025-11-20 05:07:46 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:07:46 -05:00
Owner
Copy Link

Originally created by @benjamin-dcs on GitHub (Jun 19, 2025).

✅ 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). ### ✅ 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)
saavagebueno added the bug label 2025-11-20 05:07:46 -05:00
saavagebueno commented 2025-11-20 05:07:46 -05:00
Author
Owner
Copy Link

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

No Network on LXC - maybe the underline in hostname

@MickLesk commented on GitHub (Jun 19, 2025): No Network on LXC - maybe the underline in hostname
saavagebueno commented 2025-11-20 05:07:46 -05:00
Author
Owner
Copy Link

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

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

@benjamin-dcs commented on GitHub (Jun 19, 2025): spot-on! `zigbee2mqtt-poe` works. Thanks for the crazy fast respons!
saavagebueno commented 2025-11-20 05:07:47 -05:00
Author
Owner
Copy Link

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

I build an check for this in next PR

@MickLesk commented on GitHub (Jun 19, 2025): I build an check for this in next PR
saavagebueno commented 2025-11-20 05:07:47 -05:00
Author
Owner
Copy Link

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

fixed with next pr for all guys

@MickLesk commented on GitHub (Jun 19, 2025): fixed with next pr for all guys
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1296
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?