Zigbee2MQTT - Web UI not opening - 502 Bad Gateway

Configuration Zigbee
, ,
5

Thanks for your reply. I have changed Z2M’s port to 8080, but the Web UI still is not working and I can’t access http://192.168.178.22:8080/.

6

I’m currently using http://192.168.178.22:8123/ to open my HA, does that make any difference?

7

If I change

mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://192.168.178.22:1883'

to

mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://192.168.178.22:8080'

Z2M won’t connect to MQTT at all (so say the logs).

8

No, because you want to open the WebUI of Zigbee2MQTT, not the one of Home Assistant.

  • did you restart Zigbee2MQTT after changing the configuration?
  • do you use Docker of another container / virtualization platform that requires extra steps to expose ports?
  • does sudo netstat -tlnp show an open port 8080 on IP 0.0.0.0?
9

  • did you restart Zigbee2MQTT after changing the configuration?
    Yes.

  • do you use Docker of another container / virtualization platform that requires extra steps to expose ports?
    No.

  • does sudo netstat -tlnp show an open port 8080 on IP 0.0.0.0?
    Yes.

10

Mensch, da fehlen ein paar Basics, oder?

  • mqtt://192.168.178.22:1883 is the URL that Zigbee2MQTT uses to connect to your Mosquitto broker (Mosquitto listens on port 1883). Infact you could even discard the port number as 1883 is the default
  • http://192.168.178.22:8080 is the URL that you type in your browser to connect to the frontend of Zigbee2MQTT. It cannot be port 1833, as this port on the target IP is used by Mosquitto.

When calling the netstat-command, what program is named in the last column (“PID/Program name”), maybe port 8080 is also blocked by another program? Firewall active?

11

I am also getting the same problem. same set up as you, its only just began happening though today.

12

Using Zigbee2MQTT version 1.17.0-dev (commit #d1a1035) with frontend on port 8080, I can access and use the Web UI on Zigbee2MQTT. I do not have a firewall in use.

13

I also do not use a firewall or any program that could block port 8080.

14

Zigbee2MQTT:error 2021-01-19 14:51:53: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-01-19 14:51:53: Failed to start zigbee
Zigbee2MQTT:error 2021-01-19 14:51:53: Exiting…
Zigbee2MQTT:error 2021-01-19 14:51:53: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)

15

That’s some different log than mine. I think you have something wrong with you Z2M config because it “failed to start Zigbee”. My Z2M starts as normal just the WEB UI does not work.

16

So i stopped addon, pulled out the usb stick, waited 10 seconds, put it back in and started addon again… working?!

17

Yesterday, after updated my Portainer (with HomeBridge) from node js 14.15.0 to 14.15.4 and npm version to 6.14.10) I got the also a 502: Bad Gateway

I changed nothing in my HA. No changes in the configuration oe anything else. The error I get:

READ THIS CAREFULLY
Refusing to start because configuration is not valid, found the following errors:
- friendly_name shoud atleast be 1 char long
If you don't know how to solve this, read https://www.zigbee2mqtt.io/information/configuration.html
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
npm
 ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR!
 [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm 
ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-02-02T07_39_38_916Z-debug.log
2021-02-02T08:39:39: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2021-02-02T08:39:39: PM2 log: App [npm:0] starting in -fork mode-
2021-02-02T08:39:39: PM2 log: App [npm:0] online
> [email protected] start /zigbee2mqtt-1.17.1
> node index.js

The error tells me to the configuration which I did not changed. Also ‘- friendly_name’ is not mentioned in my configuration of Zigbee2mqtt

my configuration:

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto:1883'
  user: mqtt
  password: ****
serial:
  port: /dev/ttyACM0
advanced:
  log_level: info
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false
18

I had this exact error when updating to latest zigbee2mqtt integration.

Rolled back to a previous snapshot and all okay again.

19

friendly_name shoud atleast be 1 char long issue here too…

For now I rolled back to previous z2m version trough a snapshot…

Does anyone has a solution yet?
Or maybe we have to wait till there’s a patch in version 1.17.2

20

Hello! I
had exactly the same error, and restoring the last copy with the previous version also helped. Four hours lost. :slightly_smiling_face:

21

Open groups.yaml in file editor and see if you have a random blank entry in there as that’s what I had. No idea how as never use zigbee groups but this is what caused the issue.

1 Like
22

Yes, for me that was the solution:
To erase everything inside groups.yaml

23

Hello! I had exactly the same error. Use CC2531 and now green LED all the time switch from “on” to “off” after 3-5 sec. after restarting the system. Before - it was all the time “on”.

24

Zigbee2MQTT:info Starting zigbee-herdsman (0.13.59)
Zigbee2MQTT: Error while starting zigbee-herdsman
Zigbee2MQTT: Failed to start zigbee
Zigbee2MQTT: Exiting…
Zigbee2MQTT: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)