Did you try to connect to your Home Assistant with the outside or the local IP-address?
I’ve tried to access it through several different browsers on different machines and platforms. All exhibit the same Loading Data loop. I also tried accessing it through NabuCasa and ran into the same problem. Frustrating.
Did you also tried your local IP-address like https://xx.xx.xx.xx:8123 in a browser (the app will not work!)?
Yep. That’s typically the way I access the frontend. Nothing gets me past the “Loading Data”. I can access it through SSH and Samba share, but it really doesn’t do much else.
Ok, that is sad. I think I can not help you. 
Ok…so here’s a twist. I attempted to do another upgrade to 0.108.5 today from 0.107.7. I updated and left the browser window open and waited.
After it upgraded, the supervisor screen came back to life and I could access the lovelace frontend panels, the developer tools, supervisor, and configuration menus.
When attempting to access the Map, Logbook, History, and Profile tabs .I get a quick flash of: "Error while loading insert page name followed by the blue spinning circle of death.
If I try to access the frontend from any other browser window, tab, mobile device, or nabucasa…then it goes to blue spinning circle loop of death.
I rebooted the Pi to see if it would have any effect and when that happened I can no longer access with the browser screen from which I rebooted it from.
All my automations and devices function properly. i just can’t access or see the frontend?
At this point I’m assuming it’s a token issue? Any thoughts??
I had the problem yesterday evening again, after having it used the whole day without problems. The UI is not available locally and not via duckdns.
I had to reboot the Pi to get it to work again.
After 2 hours I stuck again and now the UI will only show “laoding data” after a reboot.
This is the supervisor log:
20-04-17 07:03:32 INFO (SyncWorker_6) [supervisor.docker.cli] Start CLI homeassistant/armv7-hassio-cli with version 25 - 172.30.32.5
20-04-17 07:03:32 INFO (SyncWorker_8) [supervisor.docker.audio] Start Audio homeassistant/armv7-hassio-audio with version 14 - 172.30.32.4
20-04-17 07:03:32 INFO (SyncWorker_5) [supervisor.docker.dns] Start DNS homeassistant/armv7-hassio-dns with version 9 - 172.30.32.3
20-04-17 07:03:32 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf
20-04-17 07:03:32 INFO (SyncWorker_15) [supervisor.docker.interface] Attach to homeassistant/raspberrypi4-homeassistant with version 0.108.5
20-04-17 07:03:33 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /
20-04-17 07:03:33 INFO (MainThread) [supervisor.hassos] Detect HassOS 3.13 / BootSlot A
20-04-17 07:03:35 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/git/aaa91bdd repository
20-04-17 07:03:35 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/git/40817795 repository
20-04-17 07:03:35 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/core repository
20-04-17 07:03:35 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/git/a0d7b954 repository
20-04-17 07:03:35 INFO (MainThread) [supervisor.store] Load add-ons from store: 117 all - 117 new - 0 remove
20-04-17 07:03:35 INFO (MainThread) [supervisor.addons] Found 7 installed add-ons
20-04-17 07:03:35 INFO (SyncWorker_4) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-samba with version 9.1.0
20-04-17 07:03:35 INFO (SyncWorker_7) [supervisor.docker.interface] Attach to hassioaddons/sonweb-armv7 with version 0.10.0
20-04-17 07:03:35 INFO (SyncWorker_9) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-mosquitto with version 5.1
20-04-17 07:03:35 INFO (SyncWorker_6) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-ssh with version 8.5.4
20-04-17 07:03:35 INFO (SyncWorker_14) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-configurator with version 5.0.0
20-04-17 07:03:35 INFO (SyncWorker_13) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-duckdns with version 1.11
20-04-17 07:03:35 INFO (SyncWorker_8) [supervisor.docker.interface] Attach to pschmitt/home-assistant-addon-armhf-flicd with version 1.3
20-04-17 07:03:35 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-04-17 07:03:35 INFO (MainThread) [supervisor.snapshots] Found 0 snapshot files
20-04-17 07:03:35 INFO (MainThread) [supervisor.discovery] Load 1 messages
20-04-17 07:03:35 INFO (MainThread) [supervisor.ingress] Load 32 ingress session
20-04-17 07:03:35 INFO (MainThread) [supervisor.secrets] Load Home Assistant secrets: 1
20-04-17 07:03:35 INFO (MainThread) [__main__] Run Supervisor
20-04-17 07:03:35 INFO (MainThread) [supervisor.api] Start API on 172.30.32.2
20-04-17 07:03:35 INFO (MainThread) [supervisor.utils.gdbus] Call de.pengutronix.rauc.Installer.Mark on /
20-04-17 07:03:35 INFO (MainThread) [supervisor.hassos] Rauc: A - marked slot kernel.0 as good
20-04-17 07:03:35 INFO (MainThread) [supervisor.addons] Phase 'initialize' start 0 add-ons
20-04-17 07:03:35 INFO (MainThread) [supervisor.addons] Phase 'system' start 2 add-ons
20-04-17 07:03:38 INFO (SyncWorker_8) [supervisor.docker.addon] Start Docker add-on hassioaddons/sonweb-armv7 with version 0.10.0
20-04-17 07:04:12 INFO (SyncWorker_1) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-mosquitto with version 5.1
20-04-17 07:04:16 INFO (MainThread) [supervisor.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
20-04-17 07:04:17 INFO (MainThread) [supervisor.addons] Phase 'services' start 4 add-ons
20-04-17 07:04:22 INFO (SyncWorker_17) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-samba with version 9.1.0
20-04-17 07:04:24 INFO (SyncWorker_4) [supervisor.docker.addon] Start Docker add-on pschmitt/home-assistant-addon-armhf-flicd with version 1.3
20-04-17 07:04:24 INFO (SyncWorker_9) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-duckdns with version 1.11
20-04-17 07:04:25 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for DVES_USER
20-04-17 07:04:25 ERROR (MainThread) [supervisor.homeassistant] Error on call https://172.30.32.1:8123/api/: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]
20-04-17 07:04:25 INFO (MainThread) [supervisor.auth] Home Assistant not running, check cache
20-04-17 07:04:25 INFO (SyncWorker_12) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-ssh with version 8.5.4
20-04-17 07:04:25 INFO (MainThread) [supervisor.auth] Cache hit for DVES_USER
20-04-17 07:04:30 INFO (SyncWorker_1) [supervisor.docker.interface] Start homeassistant/raspberrypi4-homeassistant
20-04-17 07:04:45 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_sonweb
20-04-17 07:10:10 INFO (MainThread) [supervisor.api.security] /core/logs access from core_ssh
20-04-17 07:10:35 INFO (MainThread) [supervisor.api.security] /supervisor/logs access from core_ssh
20-04-17 07:13:19 INFO (MainThread) [supervisor.api.security] /supervisor/logs access from core_ssh
and this is the core log:
2020-04-17 09:04:47 INFO (MainThread) [homeassistant.bootstrap] Config directory: /config
2020-04-17 09:04:47 INFO (SyncWorker_1) [homeassistant.loader] Loaded fritzbox_tools from custom_components.fritzbox_tools
2020-04-17 09:04:47 INFO (SyncWorker_2) [homeassistant.loader] Loaded hacs from custom_components.hacs
2020-04-17 09:04:47 INFO (SyncWorker_7) [homeassistant.loader] Loaded ical from custom_components.ical
2020-04-17 09:04:47 INFO (SyncWorker_3) [homeassistant.loader] Loaded homeassistant from homeassistant.components.homeassistant
2020-04-17 09:04:47 INFO (SyncWorker_4) [homeassistant.loader] Loaded persistent_notification from homeassistant.components.persistent_notification
2020-04-17 09:04:48 INFO (MainThread) [homeassistant.setup] Setting up homeassistant
2020-04-17 09:04:48 INFO (MainThread) [homeassistant.setup] Setup of domain homeassistant took 0.0 seconds.
2020-04-17 09:04:48 INFO (MainThread) [homeassistant.setup] Setting up persistent_notification
2020-04-17 09:04:48 INFO (MainThread) [homeassistant.setup] Setup of domain persistent_notification took 0.0 seconds.
2020-04-17 09:04:48 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for fritzbox_tools which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-04-17 09:04:48 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-04-17 09:04:48 INFO (SyncWorker_2) [homeassistant.loader] Loaded harmony from homeassistant.components.harmony
2020-04-17 09:04:48 INFO (SyncWorker_2) [homeassistant.loader] Loaded http from homeassistant.components.http
2020-04-17 09:04:48 INFO (SyncWorker_13) [homeassistant.loader] Loaded homekit from homeassistant.components.homekit
2020-04-17 09:04:48 INFO (SyncWorker_15) [homeassistant.loader] Loaded pi_hole from homeassistant.components.pi_hole
2020-04-17 09:04:48 INFO (SyncWorker_5) [homeassistant.loader] Loaded nut from homeassistant.components.nut
2020-04-17 09:04:48 INFO (SyncWorker_17) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend
2020-04-17 09:04:48 INFO (SyncWorker_0) [homeassistant.loader] Loaded automation from homeassistant.components.automation
2020-04-17 09:04:48 INFO (SyncWorker_4) [homeassistant.loader] Loaded group from homeassistant.components.group
2020-04-17 09:04:48 INFO (SyncWorker_14) [homeassistant.loader] Loaded media_player from homeassistant.components.media_player
2020-04-17 09:04:48 INFO (SyncWorker_13) [homeassistant.loader] Loaded fritzbox from homeassistant.components.fritzbox
2020-04-17 09:04:48 INFO (SyncWorker_15) [homeassistant.loader] Loaded device_tracker from homeassistant.components.device_tracker
2020-04-17 09:04:48 INFO (SyncWorker_17) [homeassistant.loader] Loaded discovery from homeassistant.components.discovery
2020-04-17 09:04:48 INFO (SyncWorker_6) [homeassistant.loader] Loaded config from homeassistant.components.config
2020-04-17 09:04:48 INFO (SyncWorker_18) [homeassistant.loader] Loaded met from homeassistant.components.met
2020-04-17 09:04:48 INFO (SyncWorker_12) [homeassistant.loader] Loaded mqtt from homeassistant.components.mqtt
2020-04-17 09:04:48 INFO (SyncWorker_8) [homeassistant.loader] Loaded input_select from homeassistant.components.input_select
2020-04-17 09:04:48 INFO (SyncWorker_11) [homeassistant.loader] Loaded sensor from homeassistant.components.sensor
2020-04-17 09:04:48 INFO (SyncWorker_3) [homeassistant.loader] Loaded system_health from homeassistant.components.system_health
2020-04-17 09:04:48 INFO (SyncWorker_7) [homeassistant.loader] Loaded tts from homeassistant.components.tts
2020-04-17 09:04:48 INFO (SyncWorker_1) [homeassistant.loader] Loaded ssdp from homeassistant.components.ssdp
2020-04-17 09:04:48 INFO (SyncWorker_19) [homeassistant.loader] Loaded script from homeassistant.components.script
2020-04-17 09:04:48 INFO (SyncWorker_9) [homeassistant.loader] Loaded light from homeassistant.components.light
2020-04-17 09:04:48 INFO (SyncWorker_16) [homeassistant.loader] Loaded sun from homeassistant.components.sun
2020-04-17 09:04:48 INFO (SyncWorker_2) [homeassistant.loader] Loaded logbook from homeassistant.components.logbook
2020-04-17 09:04:48 INFO (SyncWorker_10) [homeassistant.loader] Loaded emulated_hue from homeassistant.components.emulated_hue
2020-04-17 09:04:48 INFO (SyncWorker_0) [homeassistant.loader] Loaded switch from homeassistant.components.switch
2020-04-17 09:04:48 INFO (SyncWorker_5) [homeassistant.loader] Loaded history from homeassistant.components.history
2020-04-17 09:04:48 INFO (SyncWorker_17) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api
2020-04-17 09:04:48 INFO (SyncWorker_15) [homeassistant.loader] Loaded upnp from homeassistant.components.upnp
2020-04-17 09:04:48 INFO (SyncWorker_14) [homeassistant.loader] Loaded map from homeassistant.components.map
2020-04-17 09:04:48 INFO (SyncWorker_4) [homeassistant.loader] Loaded ios from homeassistant.components.ios
2020-04-17 09:04:48 INFO (SyncWorker_13) [homeassistant.loader] Loaded person from homeassistant.components.person
2020-04-17 09:04:48 INFO (SyncWorker_6) [homeassistant.loader] Loaded lovelace from homeassistant.components.lovelace
2020-04-17 09:04:48 INFO (SyncWorker_12) [homeassistant.loader] Loaded zeroconf from homeassistant.components.zeroconf
2020-04-17 09:04:48 INFO (SyncWorker_18) [homeassistant.loader] Loaded updater from homeassistant.components.updater
2020-04-17 09:04:48 INFO (SyncWorker_8) [homeassistant.loader] Loaded hassio from homeassistant.components.hassio
2020-04-17 09:04:48 INFO (SyncWorker_11) [homeassistant.loader] Loaded mobile_app from homeassistant.components.mobile_app
2020-04-17 09:04:48 INFO (SyncWorker_9) [homeassistant.loader] Loaded zone from homeassistant.components.zone
2020-04-17 09:04:48 INFO (SyncWorker_1) [homeassistant.loader] Loaded binary_sensor from homeassistant.components.binary_sensor
2020-04-17 09:04:48 INFO (SyncWorker_7) [homeassistant.loader] Loaded scene from homeassistant.components.scene
2020-04-17 09:04:48 INFO (SyncWorker_3) [homeassistant.loader] Loaded icloud from homeassistant.components.icloud
2020-04-17 09:04:48 INFO (SyncWorker_19) [homeassistant.loader] Loaded api from homeassistant.components.api
2020-04-17 09:04:48 INFO (SyncWorker_17) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
2020-04-17 09:04:48 INFO (SyncWorker_10) [homeassistant.loader] Loaded webhook from homeassistant.components.webhook
2020-04-17 09:04:48 INFO (SyncWorker_10) [homeassistant.loader] Loaded auth from homeassistant.components.auth
2020-04-17 09:04:48 INFO (SyncWorker_0) [homeassistant.loader] Loaded device_automation from homeassistant.components.device_automation
2020-04-17 09:04:48 INFO (SyncWorker_15) [homeassistant.loader] Loaded onboarding from homeassistant.components.onboarding
2020-04-17 09:04:48 INFO (SyncWorker_14) [homeassistant.loader] Loaded search from homeassistant.components.search
2020-04-17 09:04:48 INFO (SyncWorker_6) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log
2020-04-17 09:04:48 INFO (MainThread) [homeassistant.bootstrap] Setting up {'system_log'}
2020-04-17 09:04:48 INFO (MainThread) [homeassistant.setup] Setting up http
2020-04-17 09:04:48 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds.
2020-04-17 09:04:48 INFO (MainThread) [homeassistant.setup] Setting up system_log
2020-04-17 09:04:48 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds.
2020-04-17 09:04:49 INFO (MainThread) [homeassistant.setup] Setting up recorder
2020-04-17 09:04:49 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.1 seconds.
2020-04-17 09:04:49 INFO (MainThread) [homeassistant.setup] Setting up fritzbox_tools
2020-04-17 09:04:49 INFO (MainThread) [homeassistant.setup] Setup of domain fritzbox_tools took 0.0 seconds.
I think I really need help!
1 Like
After rebooting yesterday evening Home Assistant is not available this morning:
Core logs:
2020-04-18 05:43:50 INFO (Thread-4) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
2020-04-18 05:45:22 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 1 s
2020-04-18 05:45:55 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 2 s
2020-04-18 05:46:29 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 4 s
2020-04-18 05:47:06 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 8 s
2020-04-18 05:47:46 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 16 s
2020-04-18 05:48:34 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 32 s
2020-04-18 05:49:38 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 64 s
2020-04-18 05:51:14 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 128 s
2020-04-18 05:52:47 INFO (Thread-12) [pyhap.hap_server] 192.168.178.140 - "GET /characteristics?id=1410598936.5 HTTP/1.1" 207 -
2020-04-18 05:53:54 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 256 s
2020-04-18 05:58:42 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 300 s
2020-04-18 06:04:14 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 300 s
2020-04-18 06:09:46 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 300 s
2020-04-18 06:12:46 INFO (Thread-12) [pyhap.hap_server] 192.168.178.140 - "GET /characteristics?id=1410598936.5 HTTP/1.1" 207 -
2020-04-18 06:15:18 WARNING (Thread-4) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 300 s
2020-04-18 06:17:11 INFO (Thread-6) [pyhap.hap_server] Got connection with ('192.168.178.78', 56395).
2020-04-18 06:17:11 INFO (Thread-50) [pyhap.hap_server] 192.168.178.78 - "POST /pair-verify HTTP/1.1" 200 -
2020-04-18 06:17:11 INFO (Thread-50) [pyhap.hap_server] 192.168.178.78 - "POST /pair-verify HTTP/1.1" 200 -
2020-04-18 06:17:11 INFO (Thread-50) [pyhap.hap_server] 192.168.178.78 - "GET /accessories HTTP/1.1" 200 -
supervisor log (endless loops of this):
20-04-18 04:19:08 ERROR (MainThread) [supervisor.homeassistant] Error on call https://172.30.32.1:8123/api/:
20-04-18 04:19:08 INFO (MainThread) [supervisor.auth] Home Assistant not running, check cache
20-04-18 04:19:08 INFO (MainThread) [supervisor.auth] Cache hit for DVES_USER
20-04-18 04:19:16 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for DVES_USER
20-04-18 04:19:18 ERROR (MainThread) [supervisor.homeassistant] Error on call https://172.30.32.1:8123/api/:
20-04-18 04:19:18 INFO (MainThread) [supervisor.auth] Home Assistant not running, check cache
20-04-18 04:19:18 INFO (MainThread) [supervisor.auth] Cache hit for DVES_USER
20-04-18 04:19:26 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for DVES_USER
20-04-18 04:19:28 ERROR (MainThread) [supervisor.homeassistant] Error on call https://172.30.32.1:8123/api/:
20-04-18 04:19:28 INFO (MainThread) [supervisor.auth] Home Assistant not running, check cache
20-04-18 04:19:28 INFO (MainThread) [supervisor.auth] Cache hit for DVES_USER
20-04-18 04:19:36 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for DVES_USER
20-04-18 04:19:38 ERROR (MainThread) [supervisor.homeassistant] Error on call https://172.30.32.1:8123/api/:
20-04-18 04:19:38 INFO (MainThread) [supervisor.auth] Home Assistant not running, check cache
20-04-18 04:19:38 INFO (MainThread) [supervisor.auth] Cache hit for DVES_USER
20-04-18 04:19:44 INFO (MainThread) [supervisor.api.security] /supervisor/logs access from core_ssh
Can someone help me? Thank you!
Sometimes simply closing and reopening the browser tab works for me.
Wes
There was an issue with the Sonos integration in 0.108.x which could cause this problem depending on which radio station you were playing (or not playing, since pausing would exacerbate the problem).
It should be fixed in 0.108.6.
1 Like
This worked until four days or so. Also it worked to use the local and not the duckdns address. But today was totally different. No browser, also no private browsing worked, only ssh was working. And there it is something in the log as if Home Assistant itself is not longer running.
I am not using any Sonos speakers. I am using a LMS server (running on a PI4 with piCorePlayer installation) and piCorePlayer with Squeezelite/Jivelite.
0.108.6 seems to have fixed my problem and I was running Radio Station streams through Sonos. Thank you!!!
1 Like
There is a similar issue with binary_sensor.bayesian which is not yet fixed: "Event is not JSON serializable" occurs when using templating in Bayesian sensor · Issue #33929 · home-assistant/core · GitHub
I don’t use them.
But my Home Assistant was not reachable 10 minutes ago. 20 minutes ago it was working fine. It looks like Home Assistant (is it a docker image in HassOS?) itself is not longer running.
After “ha host reboot” it worked.
I also tried “ha core start” and “ha core restart” but none of them was working. There was nothing happening.
Now it has happened another time.
I am using 0.108.6 of Home Assistant.
@carsten_h This log line jumps out at me:
I see this error in my supervisor logs a lot anytime I restart home assistant but its a little bit different and it goes away once it comes up:
20-04-18 21:03:33 ERROR (MainThread) [supervisor.homeassistant] Error on call http://172.30.32.1:8123/api/: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]
So couple questions I’d ask about this:
- You said you normally access your HA instance via its IP. Usually when people do that it means they don’t have HA exposed externally and only access it internally. And often when people don’t have external access they don’t enable SSL but your supervisor clearly thinks SSL is enabled. Is it? And did you mean for it to be?
- If so what’s the status of the certificate? Is it in the place HA expects it to be? Is it self-signed and if so is there something that needs to be set for that to be ok with supervisor? I’m honestly asking, I use the Nginx Proxy Manager add-on for external access so everything is HTTP inside the network so I have no experience making supervisor talk to HA via SSL.
I also googled this line in particular Cannot connect to host 172.30.32.1:8123 ssl:None which lead me to this extremely active github issue and this follow-on smaller one. Unfortunately there doesn’t seem to be a clear resolution but there is a few suggestions in there to possibly try.
One thing I did notice is it looks like a lot of discussion on the MQTT add-on which it appears you use as well. Maybe try disabling it temporarily to see if its related to that? If so that would at least narrow down the focus for the issue.
EDIT: I realize I may have misread a bit, @mboarman said he accesses HA via internal IP, @carsten_h you didn’t say that. Whoops! Sorry about that.
Ok, to make it clear how I work here.
I have HassOS installed on a Pi 4. I am using the DuckDNS extension with Let’s Encrypt support (normal HassOS add-on).
So I have an external address for use eg. with the iOS app:
https://xxxxxxx.duckdns.org:8123 (the certificate is valid!)
also I can use the local address (only in a browser as the iOS app want work!):
https://192.168.178.108:8123
The 172…-address is from a docker instance on HassOS I think. I am not using it, it must be internally used.
I am using the Mosquitto MQTT broker add-on from HassOS. I need it for all the tasmota switches and lamps. That is a main part of my automations, so I can not work without it.
Thank you for pointing me to the thread!
No problem. 
Oh yea I figured that wasn’t a permanent solution. I was suggesting to temporarily disable it and see if that fixes your issue. If it does then you know what to focus attention on.
In fact, searching a bit it looks like port conflicts with addons is a common cause of this problem, where you’ve got two things trying to liston on the same port and failing. I found this post and this post as well where it seems like the authors were able to resolve the issue by disabling all addons and then re-enabling them one by one until the port conflict was identified. Then you can adjust the network settings of that addon to get it on a different port.
For the record, one reason the iOS app might not be working is because you’re getting a certificate error. LetsEncrypt will only give you certificates for public URLs and they are valid only for that specific URL (the duckdns one in your case). I’m guessing when you went to https://192.168.178.108:8123 the first time you got a warning in your browser telling you that the secure connection failed due to a certificate error and asking if you wanted to proceed anyway, right? That’s a certificate error because the application is presenting a certificate which is valid only for xxxxxx.duckdns.org and telling you to use it on 192.168.178.108. Browsers will give you an option to ignore that error and proceed anyway but many apps and services will not.
This is actually what I was wondering about supervisor. Since supervisor is trying to connect to https://172.30.32.1:8123 that should have the same issue with the certificate (presenting a certificate for xxxxxx.duckdns.org for 172.30.32.1). But reading these other posts it seems an addon port conflict is more likely, supervisor must have a way to handle that.
Ok, I will try…
I looked at all used ports from the installed add-ons and I didn’t found a ports that is used twice.
Ok, I will try this too.
Sure. Thank you for the explanation. It’s clear that a certificate will only work for a name and not an IP-address. The browser is telling me that it is insecure, but because it is my own LAN, I am sure I can trust the Pi.