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?
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:
http:
base_url: my-subdomain .duckdns.org
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
Mutt, thanks for the response. I tried your recommendation step by step and got the same results from the mydomain.duckdns.org. The one good bit is that I can now connect locally via hassserverIP:8123 which I could not before. The bad news is that I now lost my Smartthings integration which is the main reason I’m trying to do set up secure remote access. Hmmm.
I’m confused that my iPhone lets me connect via cell service but not the laptop via wifi (the cell phone can’t connect via wifi either). Seems like the the answer is somewhere there. Whatever differentiates the iPhone’s cell communication from the laptop’s wifi should be the answer. I’m too much of a noob to know what that difference is.
Hmmmm,
This sounds like your modem/router is having problems with hairpin nat (ie it thinks the external address is external and does not recognise that it should be talking to itself. You may be fine if you are actually trying to communicate from an actual external location (like your phone is doing because its routed through your cell providers external system)
You could try Google search for hairpin and your modem make/model.
All of this doesn’t help you if need smartthings.
The best alternative is using Nabu casa, there’s a month free to test and get things going but ultimately its a paid solution that ‘may’ be worth it.
Good Luck
Just to close the loop (pun unintended), I ended up doing a lot of research on NAT loopback/hairpin and it sounds like Mutt was correct that this was the source of my problem. It’s explained very nicely here. My old ISP provided Arris router did not support NAT loopback. I replaced my router with an Orbi RBR50 which does support NAT loopback and I’m now able to access my external URL Raspberry Pi HA server from inside the same network. Many thanks Mutt.