Nothing. I think just the wording they used to log in
I added ngix and now I can’t access TasmoAdmin from my iframe panel…I’m not forwarding port 9541 in my router since I was told I don’t need to since I’m using ngix…
Check the x-frame-options in the header for NGINX. Setting to SAMEORIGIN will cause that error.
I’m not sure where that config would reside? It’s not under the add-on itself, is it in a file somwhere?
it will be in an addon file/config somewhere but I don’t use NGNIX so can’t say where. Check here https://securityheaders.com/ That will tell you what your headers are set to anyway
can some one tell me the default username / password stuff?
I don’t think there is one until you set it on first run of the addon
ok so where would it be stored, I literally deleted the add-on, rebooted and re-added the add-on and the password did not reset…
just notice that if you upgrade your tasmotas with 9.5.0.6 the backups fail , still working with 9.5.0.3
huh??? What backups?
sorry wrong thread i meant tasmobackup
Anybody come across this message…
“The client and server don’t support a common SSL protocol version or cipher suite.”
I’m getting this when trying to open the WebUI from TasmoAdmin. Its been working fine for ages and now I can’t start it, I have deleted duckdns and reinstalled it, in case it was an ssl key error but that hasn’t worked…I’ve also cleared the browser cache but nothing gives
Add-on version: 0.15.0
You are running the latest version of this add-on.
System: Home Assistant OS 6.3 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2021.9.4
Home Assistant Supervisor: 2021.09.0
I’ve not looked over after my HASSIO configuration for a while now. Seems to be working fine as it was. Just updated things so now and then.
But now I’ve figured out that the Tasmoadmin plugin is suddenly not working annymore. I did not made anny changes besides updating HASSIO.
I’ve configured my setup with the HAASKA setup en reaching out to it via duckdns.
I get the following message on a blank screen when I try to enter Tasmoadmin.
".duckdns.org gebruikt een niet-ondersteund protocol"
(.duckdns.org is using a not supported protocol)
Annyone knows what could went wrong over time? And more important, how to fix it?
p.s. When opened in it’s own screen, I recieve the following error too:
“ERR_SSL_VERSION_OR_CIPHER_MISMATCH”
There is an update to the add on from 15.0 to 15.1 which I believe fixes this issue…It just need Frenck to update it when he is better…
1 Like
Thanks for the reply! I thought it could be something with HASSIO or my my settings.
But then I will wait patiently for an update! 
have the same issue: “ERR_SSL_VERSION_OR_CIPHER_MISMATCH”, so just patiently waiting for an update?
Same problem here. Hope for a quick resolution. Thanks for all the great work.
Здравствуйте. После последнего обновления следующая ошибка:
( /var/www/tasmoadmin/tasmoadmin/tmp/cache/i18n/php_i18n_16dff9cb66d1ffd73722a1bb89ef4fca___L_ru.cache.php on line 421
Т.е. находит все устройства, но останавливается на одном и не дает их добавить в список.
Она возникает на устройствах, где более одного выключателя/реле.
I also have the same problem after the last update.
log:
`s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
Add-on: TasmoAdmin
Centrally manage all your Sonoff-Tasmota devices
Add-on version: 0.19.0
You are running the latest version of this add-on.
System: Home Assistant OS 8.2 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2022.6.6
Home Assistant Supervisor: 2022.05.3
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/tasmoadmin.sh
cont-init: info: /etc/cont-init.d/tasmoadmin.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun php-fpm (no readiness notification)
s6-rc: info: service legacy-services successfully started
[15:52:48] INFO: Starting PHP-FPM server…
[15:52:49] INFO: Starting NGINX server…`
