Zigbee2MQTT Web Ui not working after host update #23134
Comments
|
I am seeing the same issue after updating Proxmox this morning. I am running the latest version 1.39.0-1, but when trying to get into the UI I get a cloudflare error as I run HA behind CF. I am using port 8099 and even trying to connect via the local IP and port I get no response. Nothing is being reported in the logs either. Z2MQTT works fine in every other way, it's just that I cannot reach the Web UI. |
|
I want to add another experience I have, after I made it working as mentioned in my edit of first message, I had to shutdown the host where Proxmox is running, and once again after the startup I was having the same Z2M issue. So it seems something related of when the host is booting up (or at least Z2M is booting up). I did again the trick of changing the driver back and forth, but it is not a definitive solution |
|
I am running the Sonoff CC2652P adaptor, but I get no errors for the adapter or the Web UI in the logs. It was working this morning before the Proxmox updates so I am guessing that something changed there to stop the Web UI from working now. Will wait and see if others have similar issues after carrying our a Proxmox update. |
|
Rolling back to 1.38.0-1 fixed the issue for me. I updated to the latest update and I lose access to the UI again. Rolling back a 2nd time restores it. |
|
i have this problem on a raspberry pi installation, was working for min 1 year, but now I see in the zigbee logs the ui port is open, but no access to the ui, also no open port when I check with ss -ltn in the terminal. |
|
I have similar symptoms, but have not updated my host system (Home Assistant Yellow). I did update to Home Assistant 2024.7.0 yesterday and for a few hours the web UI worked fine. But after adding two new devices, the UI is not reachable anymore and gives Rolling back to 1.38.0-1 fixed it for me as well. |
|
also another problem, with the safari browser the gui is never working, only with a browser like chrome for me :/ |
|
similar issue to here |
|
Fix it with a STRG+F5 in Firefox (Delete Cache/Reload). |
|
I have managed to get mine working again with the latest update after removing all entries in the group.yaml file. I saw it mentioned here and that allows the frontend to work with the latest update. I deleted the 2 entries I had in groups from the UI before updating, and it has fixed it for me. |
|
I have the same issue with latest. I get no UI, not even an open port (at 8080), everything is working, except the web UI. Nothing in the log file about frontend or any other error. |
|
same here. no UI. no connection from z2m to MQTT broker. happened over night with no changes made. |
|
For me mqtt and everything works, just not the web interface. |
What happened?
Hello,
before the activities of this morning, all the infrastructure were working very fine since many months, Z2M ok, MQTT ok, HA ok, no issue.
This morning I did a Proxmox update as it offered me to install some updates. After that, the Z2M web interface stopped working with the ERR_CONNECTION_REFUSED error.
I did not change anything in the Z2M LXC specifically, I even tried restoring a backup from yesterday, but the issue is still persisting. This is my configuration yaml, this file has had no changes for many weeks. The last modification I made around april is moving to the ember driver, as defined in the following configuration:
Besides the web interface not being accessible, it seems that the MQTT is not actually receiving any data, so all the functionalities are currently offline.
I did a quick check on all existing VM and LXC and it seems that the only issue generated by this update is this one, so I'm not sure if the root cause of the issue is on the Proxmox host side or the specific Z2M LXC.
I already lost 3 hours on this, I tried to reboot many times, restoring backup from yesterday, updating the coordinator firmware, rebooting both Z2M and MQTT, rebooting the coordinator itself, rebooting the entire Proxmox, checking the Z2M logs over and over, I'm currently out of ideas and a bit hopeless on this matter.
I appreciate any help I can receive on this.
Thank you
Zigbee2MQTT version
1.38.0
Adapter firmware version
core firmware: v2.3.6, zigbee firmware: 20240510
Adapter
SM-LIGHT SLZB-06M
Setup
Beelink SER5 miniPC with Proxmox 8.2.4 - Z2M installed as LXC separated from Home Assistant
Debug log
[EDIT]
From the terminal I changed the configuration to [adapter: ezsp] and started again. It seems is now back to working, but I did not change recently this one, the ember configuration has been running since more than 1 month.
After this, I tried to revert back again to ember (and did a restart) and it seems to be still running, so not sure what was the problem here or what is changed for the resolution. I'm getting a lot of battery sensor offline but I guess they went on timeout after a long period of time with the coordinator being down, I guess they will come back sooner or later.
This is the log after the last restart, ember driver is back and I did the final restart
The text was updated successfully, but these errors were encountered: