@ipjaeger wrote:
OK, I’ve read a ton of threads about the whole DuckDNS/NGINX not being able to access from the outside. And while some of them sound similar, none of them seem to be exactly what I’m seeing (although as a noob with this stuff, I could be very wrong, and I apologize for that up front!)
From the start, I was never able to access HA via the hassio.local:8123 address… always had to go via the direct IP at 192.168.1.X:8123. What I didn’t look for at the time was whether that gave me a secure connection or not BEFORE I tried the DuckDNS stuff for remote access.
Went through the setups in the following two threads that proved to be helpful… except it still doesn’t work:
DuckDNS - It's not just me - it's you!
https://help.konnected.io/support/solutions/articles/32000023964-set-up-hass-io-with-secure-remote-access-using-duckdns-and-nginx-proxyThe Konnected link shows a log from the NGINX app that shows it creating dhparams and a snakeoil certificate. My logs just say “INFO: Running nginx…” and it doesn’t change when I hit refresh.
.
.So I’ve done a few other things to see what’s going on:
- Port Forwarding works because when I use an outside (i.e. iphone) access and pull up the actual ip address of my router with the X.X.X.X:443 I get the HomeAssistant welcome page but it’s “Not Secure.”
- FROM EXTERNAL: I can ping the XXX.duckdns. org address and get a return (averages about 55ms) and it shows that it’s going to the correct IP address
- FROM EXTERNAL: When I tracert / traceroute the duckDNS address or direct IP address, it always goes dead at the same node: agg1.rcsntxiw01m.tx.rr. com
- FROM INTERNAL: I cannot ping or Traceroute either the DuckDNS or direct IP address.
I’m probably missing something simple, but I’ve been at this for 1.5 days now and it’s driving me crazy!
Halp!
Posts: 2
Participants: 2