Not showing the page

[videobuff]

Problem/Motivation

On a fresh raspberry pi HA system, i installed tasmoadmin but it won't show.

(Why the issue was filed) I says go click on oepn-web-ui (https://192.168.178.126:9541) but then nothing on that page. error.

Expected behavior

Show the page

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

Take a fresh sd card - install ha and then try to install tasmadmin

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix, describe the rationale behind it)

[Garywoo]

Please post the error you are seeing when you click on the web UI link.

[videobuff]

The best i can do is show a screenprint. FYI, i run Home Assistant ona raspberry 4 (fresh install) in my home network.

[Garywoo]

It appears that the web server isn't running for the add-on. Are there any errors in the Log tab of the add-on?

[Urs-O]

Doenst work for me either, even bricked Esphome Addon. Had to uninstall it to get esphome back runnin

[mondo2020]

Switching SSL off works for me

[frenck]

Please share the add-on logs.

[Rakha555]

Hi Frank.

I have the same problem. Here is my log. Hope it helps. Thanks for all your work

I have restarted the app 2 times. Reinstalled 1 time. It has stood for 10 minutes each time. but won't go on

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service base-addon-banner: starting

Add-on: TasmoAdmin Centrally manage all your Sonoff-Tasmota devices

Add-on version: 0.22.0 You are running the latest version of this add-on. System: Home Assistant OS 9.4 (amd64 / generic-x86-64) Home Assistant Core: 2022.12.6 Home Assistant Supervisor: 2022.11.2

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service base-addon-log-level: starting s6-rc: info: service fix-attrs successfully started Log level is set to DEBUG s6-rc: info: service base-addon-log-level successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service init-tasmoadmin: starting s6-rc: info: service init-nginx: starting [00:56:42] DEBUG: Symlinking data directory to persistent storage location... s6-rc: info: service init-tasmoadmin successfully started s6-rc: info: service php-fpm: starting s6-rc: info: service php-fpm successfully started [00:56:42] INFO: Starting PHP-FPM server... s6-rc: info: service init-nginx successfully started s6-rc: info: service nginx: starting s6-rc: info: service nginx successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [00:56:42] INFO: Starting NGINX server...

---

Hi. I made it work. Uninstall and install again. Changed the network port.

Hope you had a nice Christmas. Happy New Year :-)

p.s. Thanks for a great plugin

[fpb3rd]

Hi Frank. Hi. I made it work. Uninstall and install again. Changed the network port.

Hope you had a nice Christmas. Happy New Year :-)

p.s. Thanks for a great plugin

Did you change to a specific port? I have this problem as well, SSL disabled or not.

[Rakha555]

Hi Frank. Hi. I made it work. Uninstall and install again. Changed the network port. Hope you had a nice Christmas. Happy New Year :-) p.s. Thanks for a great plugin

Did you change to a specific port? I have this problem as well, SSL disabled or not.

SSL is disabled. No I just set it to 8125 (Random)

[CaptClaude]

For me, SSL = OFF & default(?) port of 9541 works. With SSL = on, I get connection refused. This is what a successful start looks like in the logs (for me at least):

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
 Add-on: TasmoAdmin
 Centrally manage all your Sonoff-Tasmota devices
-----------------------------------------------------------
 Add-on version: 0.23.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.4  (amd64 / qemux86-64)
 Home Assistant Core: 2023.1.6
 Home Assistant Supervisor: 2022.12.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-tasmoadmin: starting
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-tasmoadmin successfully started
s6-rc: info: service php-fpm: starting
s6-rc: info: service php-fpm successfully started
[21:10:01] INFO: Starting PHP-FPM server...
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[21:10:01] INFO: Starting NGINX server...

PS: I love this add-on. Managing only 20 Tasmota devices was a nightmare before this.

[github-actions[bot]]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!