Error during access "Unable to connect Home Assistant" with blue house logo and Retry

Configuration
1

I have EndeavourOS server with VirtualBox and a guest vm with Home Assistant OS with supervisor, Hacs, ecc.
On home Assistant I use “Duck DNS” to keep sync IP and SSL Let’s Encrypt. I do not use NGINX Home assistant SSL Proxy and do NOT use also NGINX Home Assistant SSL proxy.

EndeavourOS is an AMD x86_64 SERVER full updated and HA is 2023.11.03
On EndeavourOS i run as services zigbee2mqtt, ssh server, nomachine server, mosquitto, ecc.
EndeavourOS server has his own static IP 192.168.1.7 and HomeAssistantOS vm has IP 192.168.1.25.
I have a duckdns registered domain with Let’s Encrypt SSL secure key.
My router is Openwrt Linksys and is configured with port forwarding to forward inboud port to:
8123 to (192.168.1.25) 8123, 443 to (192.168.1.25) 8123, 80 to (192.168.1.25) 80

On local inside LAN I can access in browsers with https://192.168.1.25:8123/
From outside I can enter with https://XXXXX.duckdns.org:8123/

first problem: I have problem to access home assistant web page from:
locally on browsers (firefox and Chrome) on 192.168.1.7 I can’t access to https://192.168.1.25:8123/
becouse I receive the blue ha house with Unable to connect Home Assistant and Retry

second problem 2: I have one android new phone (not rooted) Motorola Moto-G53 5G in witch I can’t access from ha app
and i obtain the same blue ha house with Unable to connect Home Assistant and Retry
If I enter from browser (always https://XXXXX.duckdns.org:8123/) instead it’s ok and I can enter

From another old android phone (rooted) I have no problem to access also from app

Inside my LAN I access from all Linux Pc (and Windows) with https://XXXXX.duckdns.org:8123/

This is ok from many time.

2

Did you just updated HA, with the latest OS-update, today/yesterday ? 11.2

Another user with also DUCKDNS just reported same issue, however he can use chrome, due to “security settings enabled” to allow access to insecure site ( that’s what he reported anyway )
If that is the issue , i haven’t found a way through FF, however in EDGE you can also “enable access to insecure sites” with additional settings

05.12.2023_20.30.22_REC
05.12.2023_20.30.22_REC955×80 2.05 KB

3

no… 11.1. anymore with browser (firefox or chrome) I can access. Why insecure? I use Let’s encrypt.

4

No, this(the pic) is just a “note” in EDGE when one apply the xtra settings, to let the browser treat it as “secure” … same as before when the browser shoved a page … " this site is insecure, click yes to continue anyway" … it’s possible to apply such extra setting in EDGE and Chrome,… Firefox has decided to just refuse the user to access a site they consider as insecure( i.e an http-site, or sites with certain SSL-certificate(not listed in their “approval” list ) .

But ot be honest , i have hard to understand which ways you can access and which ways you can not access now

Seems like you have port-forwarded 3 ports (be careful)

And sorry have not much to add as i only access mine HA through internal IP-numbers, i have no DuckDNS, or anything, and never use https, or domain or host names locally

5

solved first problem. was a browser problem.

1 Like
6

but not second problem.