Frontend not starting #624
Comments
|
I got the same issue |
|
For me it was the groups: I removed the one under '65289' and everything started. Not sure how and why this impacted the startup. So this seems it was not an addon issue, but I'm leaving this open until we find the root cause and create an issue on the right repository. |
|
I dont have a group with those high IDs. I have up to 11 groups |
|
I don't think the high ID number was the issue. I had to recreate the group (because it was appearing in the UI but I could not delete it) with empty devices array and Zigbee2MQTT was still booting, so probably the issue lies somewhere regarding devices in a group. |
|
I removed the contents of my |
|
I have it when i enable the availability in the frontend config. Once restarted the plugin i just get the error 502. When i remove the availability config it just works fine.. |
|
For me removing the groups section of the config file did not help, but like @jvleeuwen removing the "availability" section of my config file solved it and I can now access the zigbee2mqtt dashboard again. |
|
Can confirm, removing “availability: true” from configuration.yaml solves it. Changing it to false still makes it not start. Re-adding it from the gui also make it not start. |
|
I confirm as well, I commented out availabilty section in the config and the interface is now working again. |
|
For the people here whose problem was fixed by removing "availability: true" Seems like there is a fix on the dev branch. Other thread with what I believe is the same problem we had: Not sure if this thread can be closed as I don't think #23316 will fix the issue caused by the "groups" configuration problem... Guessing that is something else |
|
I have the same issue but I do not see were i can make the changes to availability. |
@herbod-nl If for some reason you don't want to upgrade to the latest version, please check that the line "availability: true" it is not at the bottom of the config file somewhere. (Are you sure you have shared the whole file?) A few other notes:
|
|
I deleted the 2 entries I had in groups from the UI before updating, and it has fixed it for me. |
|
Same issue here on 1.40, nothing in the logs. Deleting the groups from configuration.yaml fixed it. |
|
Same issue here on 1.40.1-1 |
|
Same issue here on 1.40.1-1 |
|
i've the same problem.. After removing the group from configuration.yaml (because WebUI doesn't want to delete), the WebUI doesn't start anymore :( |
i reverted to version 1.39 and it works |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
|
I still have this issue, any extra info I can provide? |
|
I tried removing the availability setting, setting it to true and false. I've tried removing all groups, etc. The only error I see is on stop: |
|
Any news? The same for me. Running on docker in Proxmox. Really strange. Out of a sudden it worked again. Changed in logging "host: localhost" to "host: 0.0.0.0" and UI worked. Changed back: UI still working. |
Description of the issue
Since upgrading to 1.39.0-1 I cannot access Zigbee2MQTT's frontend, getting "502: Bad Gateway" instead. Other addon frontends are accessible via ingress. There's nothing interesting in logs either:
[09:16:27] INFO: Preparing to start...
[09:16:28] INFO: Socat not enabled
[09:16:28] INFO: Enabled Zigbee2MQTT watchdog with value 'default'
[09:16:28] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT with watchdog (60000,300000,900000,1800000,3600000).
This is my configuration file:
And this is the add-on configuration:
I also tried uninstalling and reinstalling the addon. The addon itself is working, I can control Zigbee devices and I get sensor data into HomeAssistant. What can I do further to debug the issue?
edit: comparing with the logs from the edge version I already had installed, I see that in the logs there should be a line
Started frontend on port 8099, so the frontend is clearly not starting. Any reason for that?Thanks.
Addon version
1.39.0-1
Platform
Core 2024.6.4
Supervisor 2024.06.2
Operating System 12.4
Frontend 20240610.1
Logs of the issue (if applicable)
The text was updated successfully, but these errors were encountered: