zwave-js / zwave-js-ui

Full featured Z-Wave Control Panel UI and MQTT gateway. Built using Nodejs, and Vue/Vuetify
https://zwave-js.github.io/zwave-js-ui
MIT License
974 stars 203 forks source link

No UI on port 8091 #2997

Closed DaveDixon closed 1 year ago

DaveDixon commented 1 year ago

System journal from last startup about 30 minutes ago:

Mar 12 20:01:35 zwave-js-ui.zwave-js-ui[19760]: 2023-03-12 20:01:35.224 INFO APP: Listening on port 8091 host 0.0.0.0 protocol HTTP Mar 12 20:01:42 zwave-js-ui.zwave-js-ui[19760]: 2023-03-12 20:01:42.441 ERROR Z-WAVE-SERVER: listen EADDRINUSE: address already in use 0.0.0.0:8091 Mar 12 20:01:42 zwave-js-ui.zwave-js-ui[19760]: Error: listen EADDRINUSE: address already in use 0.0.0.0:8091 Mar 12 20:01:42 zwave-js-ui.zwave-js-ui[19760]: 2023-03-12 20:01:42.441 ERROR Z-WAVE-SERVER: listen EADDRINUSE: address already in use 0.0.0.0:8091 Mar 12 20:01:42 zwave-js-ui.zwave-js-ui[19760]: Error: listen EADDRINUSE: address already in use 0.0.0.0:8091 Mar 12 20:01:42 zwave-js-ui.zwave-js-ui[19760]: 2023-03-12 20:01:42.441 ERROR Z-WAVE: Failed to start zwave-js server: listen EADDRINUSE: address already in use 0.0.0.0:8091 Mar 12 20:05:42 zwave-js-ui.zwave-js-ui[19973]: 2023-03-12 20:05:42.164 INFO APP: Listening on port 8091 host 0.0.0.0 protocol HTTP

netstat says no one is using port 8091. headless server, so I can only check the port remotely. ufw is open for tcp on port 8091. url times out. other ports on same ip address work fine, including homeassistant.

zwave-js-ui version 10.10.0 (snap installation) Ubuntu 22.04.2 Homeassistant 2022.6 Nodejs v16.15.1

Suggestions, anyone?

Thanks!

DaveDixon commented 1 year ago

zwave-js-ui seems to be playing well with homeassistant, btw..

kpine commented 1 year ago

Mar 12 20:01:42 zwave-js-ui.zwave-js-ui[19760]: 2023-03-12 20:01:42.441 ERROR Z-WAVE: Failed to start zwave-js server: listen EADDRINUSE: address already in use 0.0.0.0:8091

According to this log, you have changed the default websocket server port from 3000 to 8091, which is already in use by the GUI. Just change it back to the default 3000.

DaveDixon commented 1 year ago

Sorry, that was the wrong restart. This is what I get

Mar 12 20:08:19 zwave-js-ui.zwave-js-ui[20114]: 2023-03-12 20:08:19.450 INFO Z-WAVE-SERVER: ZwaveJS server listening on 0.0.0.0:3000 Otherwise it wouldn't be working with homeassistant, I suppose. But nothing in the log about port 8091, the ui, or serving http.

DaveDixon commented 1 year ago

Incidentally (not obviously connected but idk) I get this exception at startup

Mar 12 20:08:14 audit[20114]: AVC apparmor="DENIED" operation="mkdir" profile="snap.zwave-js-ui.zwave-js-ui" name="/var/snap/zwave-js-ui/122/" pid=20114 comm="node" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 Mar 12 20:08:14 kernel: audit: type=1400 audit(1678673294.390:969): apparmor="DENIED" operation="mkdir" profile="snap.zwave-js-ui.zwave-js-ui" name="/var/snap/zwave-js-ui/122/" pid=20114 comm="node" requested_mask="c" denied_mask="c" fsuid=0 ouid=0

robertsLando commented 1 year ago

Seems a snap issue, @jmgiaever any clue?

jmgiaever commented 1 year ago

Hi,

Looks like it doesn't have the correct rights to create files within the isolated mount.

That can be caused by rights issues in the OS, or a bad snapd setup.

Which OS are you running?

How are you trying to start ZUI? Have you enabled it as a daemon (sudo zwave-js-ui.enable or sudo snap enable zwave-js-ui) or just running it (e.g sudo zwave-js-ui.exec)?

Are you using sudo?

@DaveDixon could you also share the output of

snap list | grep zwave
DaveDixon commented 1 year ago

Ubuntu 22.04.2. Running a systemd deamon.

jmgiaever commented 1 year ago

Can you elaborate?

DaveDixon commented 1 year ago

I have a daemon running under systemd, so I guess that means I ran sudo zwave-js-ui.enable or equivalent at some point. It started out as ZWavejs2Mqtt and migrated, so the details are hazy. Just to be sure, I stopped the daemon and ran sudo zwave-js-ui.enable and the outcome was the same as it was before. It runs normally, no error messages, but no log messages about serving http on port 8091, either.

robertsLando commented 1 year ago

Hi Dave, have you been able to fix your problem? I'm sorry but I cannot give you so much support regarding snap side

DaveDixon commented 1 year ago

Daniel,

Thanks for asking.

No, nothing seems to make it work. Soon it won't matter. I'm about to switch to HA OS on a Raspberry Pi for unrelated reasons. I really liked having HA on a Linux server, but it looks like HA OS gets all the good stuff anymore. So I'm hoping I can expect more reliability, anyway.

Thanks again,

-dave

On 3/21/23 07:41, Daniel Lando wrote:

Hi Dave, have you been able to fix your problem? I'm sorry but I cannot give you so much support regarding snap side

— Reply to this email directly, view it on GitHub https://github.com/zwave-js/zwave-js-ui/issues/2997#issuecomment-1477859452, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6WACTWYE4WEHAD3CAF2R3W5GVZLANCNFSM6AAAAAAVYQXJWQ. You are receiving this because you were mentioned.Message ID: @.***>

robertsLando commented 1 year ago

OK let me know if with that everything works, I really have no clue what's the error here but for sure nothing strictly related to zui so closing this for now, feel free to reopen if needed