I just suddenly lost access through ip | Home Assistant | Page 1

midnight geode Jul 13, 2022, 6:41 AM

#

Locally are you using http:// or https://?

worn sapphire Jul 13, 2022, 7:05 AM

#

Https

midnight geode Jul 13, 2022, 7:05 AM

#

What error are you getting remotely then?

worn sapphire Jul 13, 2022, 7:07 AM

#

A generic SSL error in the app

#

I'd send a screenshot but it won't let me

#

ERR_SSL_PROTOCOL_ERROR

#

From the ip

midnight geode Jul 13, 2022, 7:07 AM

#

Well, the IP will give you errors

#

You have to use the hostname

worn sapphire Jul 13, 2022, 7:08 AM

#

I restored to a few days ago when everything worked.

#

But still everything remained broken.

#

The https://192.168.1.xx:8123 has worked for months

midnight geode Jul 13, 2022, 7:09 AM

#

It should always have thrown an error, that's how SSL works

#

The certificate isn't valid for the IP

worn sapphire Jul 13, 2022, 7:10 AM

#

Duckdns keeps doing a countdown

midnight geode Jul 13, 2022, 7:10 AM

#

I have no idea what that means

worn sapphire Jul 13, 2022, 7:10 AM

#

Unable to connect. Retrying in 60 seconds

midnight geode Jul 13, 2022, 7:11 AM

#

https://www.yougetsignal.com/tools/open-ports/ test that the port is open

worn sapphire Jul 13, 2022, 7:11 AM

#

The app is set up with duckdns.

midnight geode Jul 13, 2022, 7:11 AM

#

Check that your router is configured for NAT reflection

worn sapphire Jul 13, 2022, 7:11 AM

#

Which number?

midnight geode Jul 13, 2022, 7:12 AM

#

What?

worn sapphire Jul 13, 2022, 7:12 AM

#

Which port number?

midnight geode Jul 13, 2022, 7:13 AM

#

The port you forwarded on your router...

#

I'd guess either 443 or 8123, but you should know...

worn sapphire Jul 13, 2022, 7:13 AM

#

443 is open

#

It has been months since I set this up

#

It was working perfectly until I tried adding an automation that broke the UI.

#

Then restarting it led to losing duckdns access.

midnight geode Jul 13, 2022, 7:15 AM

#

Well, all DuckDNS does is resolve a hostname (example.duckdns.org) to an IP (your WAN IP, typically)

#

Have you tried connecting when not on WiFi?

worn sapphire Jul 13, 2022, 7:17 AM

#

The pi or the device accessing it?

midnight geode Jul 13, 2022, 7:18 AM

#

The device accessing HA

#

Hopefully the Pi isn't on WiFi, because that'd suck

worn sapphire Jul 13, 2022, 7:20 AM

#

That is the case due to the sheer volume of devices connected. But the device accessing it was wired.

midnight geode Jul 13, 2022, 7:21 AM

#

Client isolation could cause issues there, if enabled on your router

worn sapphire Jul 13, 2022, 7:22 AM

#

I have 1 router handling 6 people each with multiple devices. Ethernet ports are not something I have in abundance.

midnight geode Jul 13, 2022, 7:22 AM

#

Switches are your friend

worn sapphire Jul 13, 2022, 7:23 AM

#

I have a switch connected as well. Power outlets are also limited. Plus I need my pi close to my door for zwave.

midnight geode Jul 13, 2022, 7:24 AM

#

The Z-Wave mesh should handle that, assuming you've built one

worn sapphire Jul 13, 2022, 7:24 AM

#

I noticed that internal 8123 forwards to 443.

midnight geode Jul 13, 2022, 7:24 AM

#

Well, hopefully 443 forwards to 8123

worn sapphire Jul 13, 2022, 7:25 AM

#

Internal 8123 external 443

midnight geode Jul 13, 2022, 7:26 AM

#

Now take your mobile phone, disconnect from WiFi, and see if you can connect to https://example.duckdns.org/ (obviously with your hostname)

worn sapphire Jul 13, 2022, 7:26 AM

#

Still same countdown

midnight geode Jul 13, 2022, 7:27 AM

#

And you said that https://www.yougetsignal.com/tools/open-ports/ with your DuckDNS hostname and port 443 worked?

#

Or did you not test with the hostname?

worn sapphire Jul 13, 2022, 7:28 AM

#

I used the external address it identified.

midnight geode Jul 13, 2022, 7:29 AM

#

Try the hostname

worn sapphire Jul 13, 2022, 7:29 AM

#

Just tried it and "Invalid remote addres"

midnight geode Jul 13, 2022, 7:29 AM

#

Well, looks like you need to check what's going on with your DuckDNS hostname/account

worn sapphire Jul 13, 2022, 7:31 AM

#

I'm gonna undo a fix I tried earlier but I did check my duckdns configuration.

#

Other than a brief moment where it banned the internal up of the router it has been working fine until todaym

#

Working now. I disabled nginx which I installed to fix things.

#

This was overall the dumbest error to cascade into other areas. The root cause was a bulb that lost connection with my ZigBee hub. This wiped out my sidebar, somehow broke duckdns, and removed entire pages like scenes.

midnight geode Jul 13, 2022, 7:38 AM

#

A bulb can't break DuckDNS

#

Correlation != Causation

worn sapphire Jul 13, 2022, 7:38 AM

#

That is the only thing I ended up removing to fix.

#

When I removed that initially the sidebar and pages returned.

#

Which explains why restoring my setup didn't do anything because it was still a broken link in an automation.

#

I have no idea why it would affect anything else though.

midnight geode Jul 13, 2022, 7:41 AM

#

It shouldn't break anything other than automations

worn sapphire Jul 13, 2022, 7:42 AM

#

I'd agree with you but removing the group it was part of from my configuration.yaml and automation tab led to restoring the setup.

#

Would a broken link in the configuration file have a cascading effect?

#I just suddenly lost access through ip