Hi!
I’m trying to reach my Hass.io installation from work.
I set up DuckDNS and could reach the UI outside my LAN but couldn’t access any addon from the panel_iframe: (IDE, Node-RED etc.). I have port forwarded the relevant ports in my router:
I have now installed the NGINX addon and seems to be able to reach the addons in the panel_iframe: when I’m using the Home Assistant app on my iPhone with wifi off.
However, when I try to access the addons in the panel_iframe: from work I get this error in the log:
You need to use a bearer token to access /api/config from 172.30.33.5
and
Login attempt or request with invalid authentication from 172.30.33.5
I log in using the new authenticator, with username and password.
I have removed everything from http: in my configuration.yaml as instructed after installation of the NGINX addon. I assume something isn’t right? How can I permit access to the addons in the panel_iframe: from work?
http:
# base_url: "MYDOMAINNAME.duckdns.org:8123"
# base_url: https://MYDOMAINNAME.duckdns.org
# ssl_certificate: /ssl/fullchain.pem
# ssl_key: /ssl/privkey.pem
# ip_ban_enabled: True
# login_attempts_threshold: 5
# trusted_networks:
# - 192.168.1.1
# api_password: !secret api_password
panel_iframe:
configurator:
title: Configurator
icon: mdi:wrench
url: https://MYDOMAINNAME.duckdns.org:3218
nodered:
title: Node-RED
icon: mdi:sitemap
url: https://MYDOMAINNAME.duckdns.org:1880
ide:
title: IDE
icon: mdi:code-braces
url: https://MYDOMAINNAME.duckdns.org:8321
motioneye:
title: motionEye
icon: mdi:camera
url: https://MYDOMAINNAME.duckdns.org:8765
tasmoadmin:
title: TasmoAdmin
icon: mdi:lightbulb-on
url: https://MYDOMAINNAME.duckdns.org:9541
pihole:
title: Pi-hole
icon: mdi:block-helper
url: https://MYDOMAINNAME.duckdns.org:4865
My Home Assistant is v.0.82.0. Hass.io supervisor v.139. Host system Resin OS 2.3.0+rev1.