Can't load frontend - docker image

[jmceara]

Hi!
I'm trying to run z2m using docker-compose. Everything seens to being loaded fine, except frontend.
I'm running on debian 11 (fresh install), firewall disabled (no rules at all), containers looks runing fine, but can't access frontend....seens that is not being loaded at container level, but I'm not sure how to check this.
This is my configuration.yaml file for this instance:

# Home Assistant integration (MQTT discovery)
homeassistant: true

# allow new devices to join
permit_join: false

# MQTT settings
mqtt:
  # MQTT base topic for zigbee2mqtt MQTT messages
  base_topic: zigbee2mqtt-b2
  # MQTT server URL
  server: 'mqtt://172.16.2.23'
  # MQTT server authentication, uncomment if required:
  user: mqttuser
  password: HIDDEN

# Serial settings
serial:
  # I'm using ZBridge + tasmota
  port: tcp://172.16.2.48:8888
  adapter: ezsp

frontend:
  port: 8080
  host: 0.0.0.0

advanced:
  # Optional: Logging level, options: debug, info, warn, error (default: info)
  log_level: debug

My docker-compose file:

version: '3.8'
services:
  zigbee2mqtt_b2:
    container_name: zigbee2mqtt_b2
    image: koenkk/zigbee2mqtt
    restart: unless-stopped
    volumes:
      - ./data-b2:/app/data
      - /run/udev:/run/udev:ro
    ports:
      # Frontend port
      - 8080:8080
    environment:
      - TZ=America/Sao_Paulo
    devices:
      # Make sure this matched your adapter location
      - /dev/null:/dev/ttyACM0

And finally, the log (that doesn't show anything related to the frontend):

z2m@zigbee2mqtt-b2:~$ docker-compose up zigbee2mqtt_b2
[+] Running 1/0
 ⠿ Container zigbee2mqtt_b2  Created                                                                                                                      0.0s
Attaching to zigbee2mqtt_b2
zigbee2mqtt_b2  | Using '/app/data' as data directory
zigbee2mqtt_b2  | Zigbee2MQTT:debug 2021-12-16 11:35:07: Loaded state from file /app/data/state.json
zigbee2mqtt_b2  | Zigbee2MQTT:info  2021-12-16 11:35:07: Logging to console and directory: '/app/data/log/2021-12-16.11-35-05' filename: log.txt
zigbee2mqtt_b2  | Zigbee2MQTT:info  2021-12-16 11:35:07: Starting Zigbee2MQTT version 1.22.1 (commit #c2b5229)
zigbee2mqtt_b2  | Zigbee2MQTT:info  2021-12-16 11:35:07: Starting zigbee-herdsman (0.13.176)
zigbee2mqtt_b2  | Zigbee2MQTT:debug 2021-12-16 11:35:07: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/app/data/coordinator_backup.json","databaseBackupPath":"/app/data/database.db.backup","databasePath":"/app/data/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"adapter":"ezsp","path":"tcp://172.16.2.48:8888"}}'
zigbee2mqtt_b2  | Assertion failed
zigbee2mqtt_b2  | Assertion failed
zigbee2mqtt_b2  | Zigbee2MQTT:info  2021-12-16 11:35:13: zigbee-herdsman started (resumed)
zigbee2mqtt_b2  | Zigbee2MQTT:info  2021-12-16 11:35:13: Coordinator firmware version: '{"meta":{"maintrel":"9 ","majorrel":"6","minorrel":"7","product":8,"revision":"6.7.9.0 build 405"},"type":"EZSP v8"}'
zigbee2mqtt_b2  | Zigbee2MQTT:debug 2021-12-16 11:35:13: Zigbee network parameters: {"channel":11,"extendedPanID":221,"panID":6754}
zigbee2mqtt_b2  | Zigbee2MQTT:info  2021-12-16 11:35:13: Currently 0 devices are joined:
zigbee2mqtt_b2  | Zigbee2MQTT:info  2021-12-16 11:35:13: Zigbee: disabling joining new devices.
zigbee2mqtt_b2  | Zigbee2MQTT:info  2021-12-16 11:35:13: Connecting to MQTT server at mqtt://172.16.2.23
zigbee2mqtt_b2  | Zigbee2MQTT:debug 2021-12-16 11:35:13: Using MQTT login with username: mqttuser

And docker ps:

root@zigbee2mqtt-b2:~# docker ps
CONTAINER ID   IMAGE                COMMAND                  CREATED          STATUS              PORTS                                       NAMES
101a472bc2de   koenkk/zigbee2mqtt   "docker-entrypoint.s…"   51 minutes ago   Up About a minute   0.0.0.0:8080->8080/tcp, :::8080->8080/tcp   zigbee2mqtt_b2

[mausch]

I don't see anything wrong in your config but just in case have you tried host network mode? (see https://github.com/Koenkk/zigbee2mqtt/blob/master/docker/docker-compose.yml for reference)

[poseidogithub]

THIS did the trick for me, thanks

[danka621]

Instead of --network_mode=host, I had to use --network="host", otherwise I would not receive "Connected to MQTT server". Like this:

sudo docker run \
   --name zigbee2mqtt \
   --restart=unless-stopped \
   --network="host" \
   --device=/dev/ttyACM0:/dev/ttyACM0 \
   -p 8081:8081 \
   -v $(pwd)/data:/app/data \
   -v /run/udev:/run/udev:ro \
   -e TZ=Europe/Amsterdam \
   koenkk/zigbee2mqtt

docker --version
Docker version 27.1.1, build 6312585

[ErikBooij]

FYI, I just ran into the exact same issue, so I'm just sharing what the problem was for me, in case anyone else runs into this.

In my case, the connection to the MQTT broker wasn't succeeding. I was trying to connect through the docker-compose container_name resolution, that didn't work in network_mode: host. Changing the MQTT broker address to mqtt://127.0.0.1:1883 did the trick.

Note that the frontend is only started after the MQTT connection succeeds and when that connection succeeds, the logs will show Connected to MQTT server.

[diabolo86]

I ran into the same issue.
Using the pi's IP in the confi file course to an issue, using localhost brings no failure but also no frontend.
For me the "network_mode: host" in docker-compose brings success.

[joshward9182]

I too, can only get the frontend to show by using 'network_mode: host' in docker-compose.

Is this intentional?
I get the idea that it isn't, due to the documentation (https://www.zigbee2mqtt.io/guide/installation/02_docker.html#docker-compose).

[cs224]

I have the same problem. "network_mode: host" works, but mapping a port doesn't. If I use "network_mode: host" the logs clearly say:

Zigbee2MQTT:info 2022-08-29 07:24:40: Started frontend on port 0.0.0.0:8080

If I use port mapping then this message is missing, but I also do not see any error message?

[cs224]

Ok. I think I have part of a solution. The problem is connecting to the MQTT server. My mqtt server is running on another computer in my local network called "odroid"

I installed telnet into the container to do some further analysis: apk --update --no-cache add busybox-extras.

In the zigbee2mqtt container I can do a nslookup odroid and it resolves the correct ip address 192.168.178.81. But when I do a telnet odroid 1883 then it hangs and cannot connect. When I do a telnet 192.168.178.81 1883 it works again. I do not know why this name resolution problem exists in this alpine container, but changing the mqtt configuration to the following does the trick:

mqtt:
  server: mqtt://192.168.178.81

[d3jong]

I had the same frontend issue and this solved it: (without putting it in host mode)

https://www.zigbee2mqtt.io/guide/configuration/frontend.html

Simply add frontend: true to your configuration.yaml

[abiola0m]

This was the problem in my case.

[HerraTee]

This worked for me too.

[dholmeswoo]

Sanity saver. thank you!

[lux73]

completely expected behavior:

https://www.zigbee2mqtt.io/guide/configuration/

Please RTFM Guys 🙃

[RupertDeRuyver]

This worked, you are the best!

[jkokiyo]

Thank you very much guys, I was very lost and this very simple solution has helped me a lot.

[drashish87]

Guys i am having the same issue, cant load frontend. I am running MQTT and Zigbee 2MQTT on LXI proxmox and HA on Proxmox too!

I have tried the solution offered!
network_mode:host

frontend: true

frontend:
port:8080

frontend:
port:8080
host:192.168.68.25

Zigbee devices are working but the Zigbee webui page won't load, any suggestions please?

[edrzns]

Guys i am having the same issue, cant load frontend. I am running MQTT and Zigbee 2MQTT on LXI proxmox and HA on Proxmox too!

I have tried the solution offered! network_mode:host

frontend: true

frontend: port:8080

frontend: port:8080 host:192.168.68.25

Zigbee devices are working but the Zigbee webui page won't load, any suggestions please?

Ever managed to fix it? I have exact same issue right now as you

[hoangtran355]

Guys i am having the same issue, cant load frontend. I am running MQTT and Zigbee 2MQTT on LXI proxmox and HA on Proxmox too!

I have tried the solution offered! network_mode:host

frontend: true

frontend: port:8080

frontend: port:8080 host:192.168.68.25

Zigbee devices are working but the Zigbee webui page won't load, any suggestions please?

I have the same problem with you.
In my case, I got the log saying that "Started frontend on port 8008" but still can access the WebUI

Turn out the port configuration on my docker-compose is conflict with my configuration.yaml
On the docker-compose, I was mapping like this:

    ports:
      # Frontend port
      - 8008:8080

Which will map from the port 8008 on the host to port 8080 on the container

But on the configuration.yaml I set the frontend port to 8008

frontend: 
#  port: 8008

Which mean on the container, the WebUI is running on port 8008, not 8080. When I tried to connect from host port 8008, it goes to port 8080 on container and see nothing.

Once I change the configuration.yaml to run the frontend on default port 8080, everything works:

frontend: true
#  port: 8008 

Hope this help

[canoez]

props to @hoangtran355

Once I change the configuration.yaml to run the frontend on default port 8080, everything works

this is exactly what I face! it feels strange that network type shall be host, but it is nowhere documented. This issue seems to be public as long as this thread, since 2021. Is there any bug-ticket raised?

For reference: I run an containerized setup of

• Unraid 7.2 OS
• Homeassistant from Unraid Apps (did not manage to move to docker-compose yet)
• Mosquitto from docker-compose
• zigbee2mqtt from docker compose