I can’t seem to get into HA after connecting to my Raspberry Pi 4 remotely. I had been operating HA locally through (IP address):8123 successfully. I recently added secure remote access capability using DuckDNS and LetsEncrypt per JuanMTech’s latest instruction. When I log into my HA through my newly created DuckDNS domain name, it takes me to the HA login page which I think means that the SSL and port forwarding stuff worked properly but after entering my login information I get the HA logo with “Unable to connect to Home Assistant. RETRY” underneath it. I can access HA through my iPhone cell service in this new configuration but not my laptop on wifi. Any ideas why that would be?
Here are the responses I get:
http://192.168.xxx.xxx:8123 – “This page isn’t working.192.168.254.181 didn’t send any data. ERR_EMPTY_RESPONSE”
https://192.168.xxx.xxx:8123 – “Your search - https://192.168.xxx.xxx:8123 - did not match any documents.”
https://my-domain.duckdns.org (on laptop wifi) – HA login followed by “Unable to connect to Home Assistant. RETRY” Note: at the HA login screen, it says “You’re about to give https://my-domain.duckdns.org/ access to your Home Assistant instance. Logging in with Home Assistant Local.”
https://my-domain.duckdns.org (on iPhone wifi) – “Unable to connect to Home Assistant. RETRY” No HA login screen.
https://my-domain.duckdns.org (on iphone cell service) – Successful HA login.
I’m guessing this stuff is not relevant since I’m getting to my HA server but if not, here are my DuckDNS and SSL settings:
– I have a static IP address established for my Hassio server and established a DuckDNS url
– Port 443 is forwarded to 8123 on my router
– I installed DuckDNS with the following settings:
–I put the http: integration info into my configuration.yaml as follows:
base_url: my-subdomain .duckdns.org