can't run frontend - Githubissues

mojijafari commented 3 years ago

Dear nurikk,

thank you very my for your kind effort, I appreicate it. However, I configured the configuration.yaml based on zigbee2mqtt.io but the webUI is not working. I tried some other ports but can't run it. Do you have any idea what the problem is? is there any other configuration?

nurikk commented 3 years ago

Hello, it's really hard to help with this amount of information. Kindly attach z2m and browser console logs as well as your configuration.yaml, and mode how'd you run z2m (docker, hass addon, vanilla installation, etc)

dlopc commented 3 years ago

Hi. I also have problems with the frontend UI. Zigbee2mqtt runs fine, but no web UI. Port 8080 is in use, so I trying to use 8089. When I open IPADDRESS:8089 I am getting

{"real_path": "", "method": "GET", "path": "/", "protocol_version": "HTTP/1.0", "request_version": "HTTP/1.1", "query": ""}

Environment:

Orange PI PC
Openmediavault
Docker
Homeassistant reinstalled from scratch few days ago (docker)
Zigbee2mqtt (docker)

configuration.yaml as follows

homeassistant: true
permit_join: true
mqtt:
base_topic: home/zigbee2mqtt
server: 'mqtt://localhost'
client_id: zigbee2mqtt
include_device_information: true
advanced:
homeassistant_discovery_topic: home
serial:
port: /dev/ttyACM0
frontend:
port: 8089
devices:
'0x00158d000522911a':
friendly_name: Volumetrico01
'0x00158d0002f2514b':
friendly_name: Puerta02
'0x00158d0005447df6':
friendly_name: Puerta01

Web UI does not show up on port on `ipaddress:8089' . And if I include the host (either localhot or 192.168.1.40), the whole zigbee2mqtt restarts forever, and log is as follows

Using '/app/data' as data directory

> zigbee2mqtt@1.17.0 start /app
> node index.js

[32mZigbee2MQTT:info [39m 2021-02-01 20:08:26: Logging to console and directory: '/app/data/log/2021-02-01.20-08-24' filename: log.txt
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:26: Starting Zigbee2MQTT version 1.17.0 (commit #07cdc9d)
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:26: Starting zigbee-herdsman (0.13.46)
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:30: zigbee-herdsman started
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:30: Coordinator firmware version: '{"meta":{"maintrel":2,"majorrel":2,"minorrel":7,"product":2,"revision":20190425,"transportrev":2},"type":"zStack30x"}'
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:30: Currently 3 devices are joined:
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:30: Puerta02 (0x00158d0002f2514b): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:30: Volumetrico01 (0x00158d000522911a): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:30: Puerta01 (0x00158d0005447df6): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
[33mZigbee2MQTT:warn [39m 2021-02-01 20:08:30: `permit_join` set to  `true` in configuration.yaml.
[33mZigbee2MQTT:warn [39m 2021-02-01 20:08:30: Allowing new devices to join.
[33mZigbee2MQTT:warn [39m 2021-02-01 20:08:30: Set `permit_join` to `false` once you joined all devices.
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:30: Zigbee: allowing new devices to join.
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:30: Started frontend on port localhost:8089
events.js:291
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE: address already in use 127.0.0.1:8089
    at Server.setupListenHandle [as _listen2] (net.js:1316:16)
    at listenInCluster (net.js:1364:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1501:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:68:8)
Emitted 'error' event on Server instance at:
    at emitErrorNT (net.js:1343:8)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '127.0.0.1',
  port: 8089
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zigbee2mqtt@1.17.0 start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.17.0 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-01T19_08_30_483Z-debug.log
Using '/app/data' as data directory

> zigbee2mqtt@1.17.0 start /app
> node index.js

[32mZigbee2MQTT:info [39m 2021-02-01 20:08:39: Logging to console and directory: '/app/data/log/2021-02-01.20-08-37' filename: log.txt
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:39: Starting Zigbee2MQTT version 1.17.0 (commit #07cdc9d)
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:39: Starting zigbee-herdsman (0.13.46)
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:43: zigbee-herdsman started
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:43: Coordinator firmware version: '{"meta":{"maintrel":2,"majorrel":2,"minorrel":7,"product":2,"revision":20190425,"transportrev":2},"type":"zStack30x"}'
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:43: Currently 3 devices are joined:
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:43: Puerta02 (0x00158d0002f2514b): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:43: Volumetrico01 (0x00158d000522911a): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:43: Puerta01 (0x00158d0005447df6): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
[33mZigbee2MQTT:warn [39m 2021-02-01 20:08:43: `permit_join` set to  `true` in configuration.yaml.
[33mZigbee2MQTT:warn [39m 2021-02-01 20:08:43: Allowing new devices to join.
[33mZigbee2MQTT:warn [39m 2021-02-01 20:08:43: Set `permit_join` to `false` once you joined all devices.
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:43: Zigbee: allowing new devices to join.
[32mZigbee2MQTT:info [39m 2021-02-01 20:08:43: Started frontend on port localhost:8089
events.js:291
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE: address already in use 127.0.0.1:8089
    at Server.setupListenHandle [as _listen2] (net.js:1316:16)
    at listenInCluster (net.js:1364:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1501:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:68:8)
Emitted 'error' event on Server instance at:
    at emitErrorNT (net.js:1343:8)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '127.0.0.1',
  port: 8089
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zigbee2mqtt@1.17.0 start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.17.0 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-01T19_08_43_661Z-debug.log
Using '/app/data' as data directory

> zigbee2mqtt@1.17.0 start /app
> node index.js

Thanks for any help or any url I could have a look at.

ChankyTheConqueror commented 3 years ago

Hi sorry for hijacking this thread, im also experiencing the same problem: Im running z2m on docker on a Raspberry Pi Model B Plus Rev 1.2, my docker-compose looks as follows: '-----------------------------------------------------------------------------------' zigbee2mqtt: container_name: zigbee2mqtt image: koenkk/zigbee2mqtt:latest-dev platform: linux/arm/v6 volumes:

/home/pi/zigbee2mqtt_data:/app/data
/run/udev:/run/udev:ro devices:
/dev/ttyACM0 restart: always ports:
"8080:8080" links:
"mqtt:broker" privileged: true environment:
TZ=Europe/Vienna '--------------------------------------------------------------------- ' I have added the tag below on my configuration.yaml: '-----------------------------------------------------------------------' frontend: port: 8080 '----------------------------------------------------------------------' when i call :8080 i cant reach the frontend. How can i debug this? any help is high appreciated

Thanks in advance!

ChankyTheConqueror commented 3 years ago

works now with:

dirkclemens commented 3 years ago

i also can't get the frontend to run.

my configuration.yaml (I am running homebridge on port :8080 in parallel on this maschine).

...
frontend:
  port: 8888
  # Optional, default 0.0.0.0
  host: 127.0.0.1
...

this does not work when leaving it empty or default 0.0.0.0 and zigbee2mqtt at all wont't even start when setting "host" to 192.168.2.222 (which is actually the machine it is running on)

I am running Nginx in parallel, is any configuration needed for that? Using Chrome and Safari.

and this is the log

Zigbee2MQTT:info  2021-02-13 12:16:03: Logging to console and directory: 'data/log' filename: log.txt
Zigbee2MQTT:info  2021-02-13 12:16:04: Starting Zigbee2MQTT version 1.17.1-dev (commit #a63b6c3)
Zigbee2MQTT:info  2021-02-13 12:16:04: Starting zigbee-herdsman (0.13.68)
Zigbee2MQTT:info  2021-02-13 12:16:06: zigbee-herdsman started
Zigbee2MQTT:info  2021-02-13 12:16:06: Coordinator firmware version: '{"meta":{"maintrel":2,"majorrel":2,"minorrel":7,"product":2,"revision":20190425,"transportrev":2},"type":"zStack30x"}'
Zigbee2MQTT:info  2021-02-13 12:16:06: Currently 8 devices are joined:
...
Zigbee2MQTT:info  2021-02-13 12:16:06: ThermostatMultiraum (0x5c0272fffe7f7e1e): TS0601_thermostat - TuYa Radiator valve with thermostat (EndDevice)
...
Zigbee2MQTT:info  2021-02-13 12:16:06: Started frontend on port 127.0.0.1:8888
Zigbee2MQTT:info  2021-02-13 12:16:07: Connecting to MQTT server at mqtt://192.168.2.222:1883
Zigbee2MQTT:info  2021-02-13 12:16:07: Connected to MQTT server
...
Zigbee2MQTT:info  2021-02-13 12:16:59: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"a63b6c3","coordinator":{"meta":{"maintrel":2,"majorrel":2,"minorrel":7,"product":2,"revision":20190425,"transportrev":2},"type":"zStack30x"},"log_level":"info","network":{"channel":12,"extendedPanID":"0x00124b0018ed325d","panID":6754},"permit_join":true,"version":"1.17.1-dev"}'

Thanks for supporting me :-)

nurikk commented 3 years ago

i also can't get the frontend to run.

my configuration.yaml (I am running homebridge on port :8080 in parallel on this maschine).

...
frontend:
  port: 8888
  # Optional, default 0.0.0.0
  host: 127.0.0.1
...

this does not work when leaving it empty or default 0.0.0.0 and zigbee2mqtt at all wont't even start when setting "host" to 192.168.2.222 (which is actually the machine it is running on)

I am running Nginx in parallel, is any configuration needed for that? Using Chrome and Safari.

and this is the log

Zigbee2MQTT:info  2021-02-13 12:16:03: Logging to console and directory: 'data/log' filename: log.txt
Zigbee2MQTT:info  2021-02-13 12:16:04: Starting Zigbee2MQTT version 1.17.1-dev (commit #a63b6c3)
Zigbee2MQTT:info  2021-02-13 12:16:04: Starting zigbee-herdsman (0.13.68)
Zigbee2MQTT:info  2021-02-13 12:16:06: zigbee-herdsman started
Zigbee2MQTT:info  2021-02-13 12:16:06: Coordinator firmware version: '{"meta":{"maintrel":2,"majorrel":2,"minorrel":7,"product":2,"revision":20190425,"transportrev":2},"type":"zStack30x"}'
Zigbee2MQTT:info  2021-02-13 12:16:06: Currently 8 devices are joined:
...
Zigbee2MQTT:info  2021-02-13 12:16:06: ThermostatMultiraum (0x5c0272fffe7f7e1e): TS0601_thermostat - TuYa Radiator valve with thermostat (EndDevice)
...
Zigbee2MQTT:info  2021-02-13 12:16:06: Started frontend on port 127.0.0.1:8888
Zigbee2MQTT:info  2021-02-13 12:16:07: Connecting to MQTT server at mqtt://192.168.2.222:1883
Zigbee2MQTT:info  2021-02-13 12:16:07: Connected to MQTT server
...
Zigbee2MQTT:info  2021-02-13 12:16:59: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"a63b6c3","coordinator":{"meta":{"maintrel":2,"majorrel":2,"minorrel":7,"product":2,"revision":20190425,"transportrev":2},"type":"zStack30x"},"log_level":"info","network":{"channel":12,"extendedPanID":"0x00124b0018ed325d","panID":6754},"permit_join":true,"version":"1.17.1-dev"}'

Thanks for supporting me :-)

don't bind to 127.0.0.1 unless you're clearly know what are you doing, stick to default 0.0.0.0 and you're on safe side

dirkclemens commented 3 years ago

don't bind to 127.0.0.1 unless you're clearly know what are you doing, stick to default 0.0.0.0 and you're on safe side

sure, I am trying all combinations but with host: 0.0.0.0 I still can't get it to work. referring to the logs, the frontend seems to be started in my (gui less) ubuntu server box, but I can't open it in the browser from my iMac

btw. I am running z2m within a docker container.

Zigbee2MQTT:info  2021-02-14 14:10:28: Started frontend on port 0.0.0.0:8888
Zigbee2MQTT:info  2021-02-14 14:10:28: Connecting to MQTT server at mqtt://192.168.2.222:1883
Zigbee2MQTT:info  2021-02-14 14:10:28: Connected to MQTT server
Zigbee2MQTT:info  2021-02-14 14:10:28: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'

dirkclemens commented 3 years ago

Update: quite simple solution for the port issue: configuration.yaml

...
frontend:
  port: 1881
...

remove old docker images and then run a new docker image simply with the port on the command line like docker run -itd -p 1881:1881 --name=zigbee2mqtt --restart=always ... koenkk/zigbee2mqtt:latest-dev

dlopc commented 3 years ago

I had a try yesterday I got it working. Not clear if because of new version or because of changes on configuration.yaml, I only changed the yaml. As follows:

before:

frontend:
  port: 8089

now:

frontend:
  port: 8058
  host: 0.0.0.0

nurikk / zigbee2mqtt-frontend

can't run frontend #264