Invalid local network

[KarlM]

Hi folks, can anyone advise on how I overcome this obstacle? It is saying that my local IP address (inc. http://homeassistant.local:8123) is invalid as my HTTPS certificate needs to cover it. Please note, although the screencap indicates I’ve manually typed https, that was just me testing if that was all it needed (wishful thinking on my part)… So it was - and has been restored to the default http and the ‘Automatic’ button has been resumed. Still no joy from either.

I have got duckdns as one but I also use the paid for HA Cloud, which as you’ll observe is enabled.

This same error occurs when I look at the voice assistants page.

So, any help on resolving this would be greatly appreciated.

[SVD-NL]

Just wondering, why are you bothering with DuckDNS and certificates if you’re using the HA Cloud subscription?

You should be able to leave your HA instance on http, so local communication works, and HA cloud will take care of external connectivity and Google Assistant connectivity

[KarlM]

Well, short version - I began doing the duckdns and couldn’t quite get it fully operational… and i figured i’d like to contribute to the team somehow, so doing the HA Cloud serves both purposes. I get guaranteed & reliable functionality and I support the invisible guys who keep this thing alive!

ETA: Also, I wanted an easy to remember domain for external access, as I gather, HA Cloud doesn’t offer an easy-to-remember url - just a random blathering of characters that I couldn’t hope to remember more than 3 of. Whereas Duckdns - offers a very nice url.

I have since disabled duckdns, let’s encrypt and nginx. Still no local access

[mterry63 (Martin)]

Certificates are only valid for names, not IP addresses. The error is telling you to supply a valid fully qualified domain name with https:// not an IP address as you have done.

[zoogara (Daryl)]

@KarlM

Still no local access

I have to ask, your screen shot shows you prefixing your local address with https://, have you changed that to http://?

[KarlM]

@zoogara

I have to ask, your screen shot shows you prefixing your local address with https://, have you changed that to http://?

@KarlM

Please note, although the screencap indicates I’ve manually typed https, that was just me testing if that was all it needed (wishful thinking on my part)… So it was - and has been restored to the default http and the ‘Automatic’ button has been resumed. Still no joy from either.

Short version, yes.

@mterry63

The error is telling you to supply a valid fully qualified domain name with https:// not an IP address as you have done.

Hmm, well how do I make a local domain?? It doesn’t accept homeassistant.local:8123 so I’m at a loss.

[zoogara (Daryl)]

@KarlM

Short version, yes

Oops missed your comment I did a similar reversal a year ago. One thing I forgot was to remove the settings that prevent local access in configuration.yaml, something like:

http:
  server_host: 127.0.0.1
  use_x_forwarded_for: true
  trusted_proxies: 127.0.0.1

Clutching at straws now I know.

[jfgoodhew1]

I’m struggling with the very same issue. No local access at all since ssl certificates were installed. And I still can’t install a SmartThings integration (the purpose of all this grafting with HA is the SmartThings air con control is USELESS), webhook comes back invalid. I’m not looking for answers to that on this post…