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

Zigbee2MQTT Alpine LXC no frontend, Stuck in Onboarding #2410

New Issue
Closed
opened 2026-02-05 04:45:11 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-05 04:45:11 +03:00
Owner
Copy Link

Originally created by @radry on GitHub (Jan 28, 2026).

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

Zigbee2MQTT LXC

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Alpine

📈 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.

After creating the container the webinterface can't be reached.
Changing the onboarding url in /etc/conf.d/zigbee2mqtt to 0.0.0.0 makes the onboarding reachable and can be configured. However even after waiting several minutes or restarting the container it still only redirects to the onboarding. This might be an issue with Z2M itself but the original issue, that the webinterface can't be reached initially seems to be a configuration issue with the default installation?

I managed to reach it randomly two times but it always claimed there is an error in configuration.yaml although I use the default one or one generated by https://www.zigbee2mqtt.io/guide/configuration/

🔄 Steps to reproduce the issue.

❌ Paste the full error output (if available).

🖼️ Additional context (optional).

💡 PVE Version 8.4.16 (Kernel: 6.8.12-18-pve)
🖥️ Operating System: alpine
🌟 Version: 3.23
📦 Container Type: Privileged
🆔 Container ID: 102
🏠 Hostname: alpine-zigbee2mqtt
💾 Disk Size: 1 GB
🧠 CPU Cores: 1
🛠️ RAM Size: 256 MiB
🌉 Bridge: vmbr0
📡 IPv4: 192.168.1.93/24
📡 IPv6: auto
🗂️ FUSE Support: no
📦 Nesting: Enabled
🎮 GPU Passthrough: no
💡 Timezone: Europe/Vienna
🔍 Verbose Mode: yes
🚀 Creating a Alpine-Zigbee2MQTT LXC using the above advanced settings
✔️ Updated app defaults: /usr/local/community-scripts/defaults/alpine-zigbee2mqtt.vars
✔️ Storage local (Free: 58.7GB Used: 11.7GB) [Template]
✔️ Storage local-lvm (Free: 85.3GB Used: 59.0GB) [Container]
✔️ Storage 'local-lvm' (lvmthin) validated
✔️ Template storage 'local' validated
✔️ Template search completed
✔️ Template alpine-3.23-default_20260116_amd64.tar.xz [local]
✔️ LXC Container 102 was successfully created.
✔️ USB passthrough configured
✔️ Started LXC Container
✔️ Customized LXC Container
💡 No SSH keys to install (skipping).
✔️ Set up Container OS
✔️ Network Connected: 192.168.1.93
✔️ Internet: ✔ IPv4 DNS: 140.82.121.4
⏳ Updating Container OS(1/4) Upgrading alpine-release (3.23.2-r0 -> 3.23.3-r0)
(2/4) Upgrading libcrypto3 (3.5.4-r0 -> 3.5.5-r0)
(3/4) Upgrading libssl3 (3.5.4-r0 -> 3.5.5-r0)
(4/4) Upgrading alpine-base (3.23.2-r0 -> 3.23.3-r0)
OK: 36.4 MiB in 73 packages
✔️ Updated Container OS
⏳ Installing Alpine-Zigbee2MQTT( 1/12) Installing ca-certificates (20251003-r0)
( 2/12) Installing libgcc (15.2.0-r2)
( 3/12) Installing libstdc++ (15.2.0-r2)
( 4/12) Installing ada-libs (3.3.0-r0)
( 5/12) Installing icu-data-en (76.1-r1)
Executing icu-data-en-76.1-r1.post-install
*

  • If you need ICU with non-English locales and legacy charset support, install
  • package icu-data-full.

( 6/12) Installing icu-libs (76.1-r1)
( 7/12) Installing simdjson (3.12.0-r0)
( 8/12) Installing simdutf (7.5.0-r1)
( 9/12) Installing sqlite-libs (3.51.2-r0)
(10/12) Installing nodejs (24.13.0-r1)
(11/12) Installing zigbee2mqtt (2.7.0-r0)
Executing zigbee2mqtt-2.7.0-r0.pre-install
(12/12) Installing zigbee2mqtt-openrc (2.7.0-r0)
Executing busybox-1.37.0-r30.trigger
Executing ca-certificates-20251003-r0.trigger
OK: 136.8 MiB in 85 packages

  • service zigbee2mqtt added to runlevel default
  • Caching service dependencies ... [ ok ]
  • Starting Zigbee2MQTT ... [ ok ]
  • Open http://127.0.0.1:8080 to configure Zigbee2MQTT.
  • You can change this URL in /etc/conf.d/zigbee2mqtt if needed.
    ✔️ Installed Alpine-Zigbee2MQTT
  • service sshd added to runlevel default
    ssh-keygen: generating new host keys: RSA ECDSA ED25519
  • Starting sshd ... [ ok ]
    ✔️ Completed successfully!
Originally created by @radry on GitHub (Jan 28, 2026). ### ✅ 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? Zigbee2MQTT LXC ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-zigbee2mqtt.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Alpine ### 📈 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. After creating the container the webinterface can't be reached. Changing the onboarding url in /etc/conf.d/zigbee2mqtt to 0.0.0.0 makes the onboarding reachable and can be configured. However even after waiting several minutes or restarting the container it still only redirects to the onboarding. This might be an issue with Z2M itself but the original issue, that the webinterface can't be reached initially seems to be a configuration issue with the default installation? I managed to reach it randomly two times but it always claimed there is an error in configuration.yaml although I use the default one or one generated by https://www.zigbee2mqtt.io/guide/configuration/ ### 🔄 Steps to reproduce the issue. - Run script - http://nodes_ip_adress:8080 no connection - Change the onboarding url in /etc/conf.d/zigbee2mqtt to 0.0.0.0 - Restart node - Onboarding can be reached at http://nodes_ip_adress:8080 and Z2M configured. - Wait and/or restart node. - Still no frontend/webinterface - remove onboarding url in /etc/conf.d/zigbee2mqtt - http://nodes_ip_adress:8080 no connection ### ❌ Paste the full error output (if available). - ### 🖼️ Additional context (optional). 💡 PVE Version 8.4.16 (Kernel: 6.8.12-18-pve) 🖥️ Operating System: alpine 🌟 Version: 3.23 📦 Container Type: Privileged 🆔 Container ID: 102 🏠 Hostname: alpine-zigbee2mqtt 💾 Disk Size: 1 GB 🧠 CPU Cores: 1 🛠️ RAM Size: 256 MiB 🌉 Bridge: vmbr0 📡 IPv4: 192.168.1.93/24 📡 IPv6: auto 🗂️ FUSE Support: no 📦 Nesting: Enabled 🎮 GPU Passthrough: no 💡 Timezone: Europe/Vienna 🔍 Verbose Mode: yes 🚀 Creating a Alpine-Zigbee2MQTT LXC using the above advanced settings ✔️ Updated app defaults: /usr/local/community-scripts/defaults/alpine-zigbee2mqtt.vars ✔️ Storage local (Free: 58.7GB Used: 11.7GB) [Template] ✔️ Storage local-lvm (Free: 85.3GB Used: 59.0GB) [Container] ✔️ Storage 'local-lvm' (lvmthin) validated ✔️ Template storage 'local' validated ✔️ Template search completed ✔️ Template alpine-3.23-default_20260116_amd64.tar.xz [local] ✔️ LXC Container 102 was successfully created. ✔️ USB passthrough configured ✔️ Started LXC Container ✔️ Customized LXC Container 💡 No SSH keys to install (skipping). ✔️ Set up Container OS ✔️ Network Connected: 192.168.1.93 ✔️ Internet: ✔ IPv4 DNS: 140.82.121.4 ⏳ Updating Container OS(1/4) Upgrading alpine-release (3.23.2-r0 -> 3.23.3-r0) (2/4) Upgrading libcrypto3 (3.5.4-r0 -> 3.5.5-r0) (3/4) Upgrading libssl3 (3.5.4-r0 -> 3.5.5-r0) (4/4) Upgrading alpine-base (3.23.2-r0 -> 3.23.3-r0) OK: 36.4 MiB in 73 packages ✔️ Updated Container OS ⏳ Installing Alpine-Zigbee2MQTT( 1/12) Installing ca-certificates (20251003-r0) ( 2/12) Installing libgcc (15.2.0-r2) ( 3/12) Installing libstdc++ (15.2.0-r2) ( 4/12) Installing ada-libs (3.3.0-r0) ( 5/12) Installing icu-data-en (76.1-r1) Executing icu-data-en-76.1-r1.post-install * * If you need ICU with non-English locales and legacy charset support, install * package icu-data-full. * ( 6/12) Installing icu-libs (76.1-r1) ( 7/12) Installing simdjson (3.12.0-r0) ( 8/12) Installing simdutf (7.5.0-r1) ( 9/12) Installing sqlite-libs (3.51.2-r0) (10/12) Installing nodejs (24.13.0-r1) (11/12) Installing zigbee2mqtt (2.7.0-r0) Executing zigbee2mqtt-2.7.0-r0.pre-install (12/12) Installing zigbee2mqtt-openrc (2.7.0-r0) Executing busybox-1.37.0-r30.trigger Executing ca-certificates-20251003-r0.trigger OK: 136.8 MiB in 85 packages * service zigbee2mqtt added to runlevel default * Caching service dependencies ... [ ok ] * Starting Zigbee2MQTT ... [ ok ] * Open http://127.0.0.1:8080 to configure Zigbee2MQTT. * You can change this URL in /etc/conf.d/zigbee2mqtt if needed. ✔️ Installed Alpine-Zigbee2MQTT * service sshd added to runlevel default ssh-keygen: generating new host keys: RSA ECDSA ED25519 * Starting sshd ... [ ok ] ✔️ Completed successfully!
OVERLORD added the bug label 2026-02-05 04:45:11 +03:00
OVERLORD commented 2026-02-05 04:45:15 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 28, 2026):

You have followed the Post Install Guide or complete ignored?

@MickLesk commented on GitHub (Jan 28, 2026): You have followed the Post Install Guide or complete ignored?
OVERLORD commented 2026-02-05 04:45:17 +03:00
Author
Owner
Copy Link

@radry commented on GitHub (Jan 28, 2026):

I already had a working Z2M LXC with an old version. Because upgrading didn't work I decided to start fresh.

I followed the post install guide but that didn't make any difference. Are you refering so something specific in there?

@radry commented on GitHub (Jan 28, 2026): I already had a working Z2M LXC with an old version. Because upgrading didn't work I decided to start fresh. I followed the post install guide but that didn't make any difference. Are you refering so something specific in there?
OVERLORD commented 2026-02-05 04:45:22 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 29, 2026):

i test it manually, it working smooth:

Image Image

Steps:
1.) Deployed Script
2.) Followed the Guide #410 (pass usb / device)
3.) Change config and restart

@MickLesk commented on GitHub (Jan 29, 2026): i test it manually, it working smooth: <img width="2493" height="621" alt="Image" src="https://github.com/user-attachments/assets/b48cf5ae-4efc-4081-9bd5-12f046a6a972" /> <img width="2693" height="1214" alt="Image" src="https://github.com/user-attachments/assets/c08a1a9c-b606-4c2e-9942-dc14dc501076" /> Steps: 1.) Deployed Script 2.) Followed the Guide #410 (pass usb / device) 3.) Change config and restart
OVERLORD commented 2026-02-05 04:45:23 +03:00
Author
Owner
Copy Link

@radry commented on GitHub (Jan 29, 2026):

@MickLesk Can you post the configuration.yaml that you used?

I have the suspicion that my Zigbee USB adapter is broken or something in the latest proxmox update.

@radry commented on GitHub (Jan 29, 2026): @MickLesk Can you post the configuration.yaml that you used? I have the suspicion that my Zigbee USB adapter is broken or something in the latest proxmox update.
OVERLORD commented 2026-02-05 04:45:24 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 29, 2026):

i have an ethernet ELZB06, not an usb. so thats useless for you. Create an Discussion maybe another one can help you.

You can Start the tool with:
ZIGBEE2MQTT_DATA=/etc/zigbee2mqtt zigbee2mqtt

for testing

@MickLesk commented on GitHub (Jan 29, 2026): i have an ethernet ELZB06, not an usb. so thats useless for you. Create an Discussion maybe another one can help you. You can Start the tool with: ZIGBEE2MQTT_DATA=/etc/zigbee2mqtt zigbee2mqtt for testing
OVERLORD commented 2026-02-05 04:45:26 +03:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 2, 2026):

This issue has been automatically locked. Please open a new issue for related bugs and reference this issue if needed.

@github-actions[bot] commented on GitHub (Feb 2, 2026): This issue has been automatically locked. Please open a new issue for related bugs and reference this issue if needed.
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#2410
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?