Here is a weird one and just wondering if anyone has some suggestions to isolate what is causing it.
my hassio.local stopped responding (Even via direct ip) but the .duckdns.org continues to work(!) - no idea how that is even possible
backstory is that I installed hass.io on new raspberry 2 days ago and been tinkering on/off and all been good. last night I setup some appdeamon automation and its been running fine for almost 24hrs.
Then I noticed some lights turning on/off that wasnāt as I expected and then wanted to look at logs - and then couldnāt reach homeassistant via local ip/names.
weirdly enough duckdns works.
while writing this I rebooted hass.io via the system menu but after restart same thing - duckdns works but local does not.
its very weird - Iām suspecting my netgear orbi network is misbehaving - its telling me iām not on an orbi network but no way I canāt be that as Iām able to post here
interesting, im fighting some related issues with duckdns, but not quite what your dealing with.
Also have an Orbi.
Do you have port forwarding setup? which ports are you using?
trying to read through the info online, it appears that once its all setup that you are supposed to use the same URL internally as externally? not sure im reading that right. thats from: https://www.home-assistant.io/docs/ecosystem/certificates/lets_encrypt/ which obviously doesnt apply if you are doing the duckdns add on setup, but was referencing that to see if i could find a hint.
Yes Port forwarding on my router to the ip of Hassio - which for reasons I canāt figure out is NOT reachable from my laptop.
What I can do though is to login into my nAS and then I can ping and ssh to Hassio just fine. Itās as if my laptop been isolated of from talking to hassio. So weird.