Local access using DuckDNS and Let's Encrypt

Configuration
1

Hi,
I have over the last few days got HA (Hass.io) set up and working quite well using DuckDNS and Let’s Encrypt.

Is there any way when I am on the same network that I can connect to HA using its local 192.168.1.x IP address or do I always need to use https://mydomain.duckdns.org?

I hope this is a simple question but if not I am happy to provide any further information!!

1 Like
2

Simple answer: Yes, always use the duckdns url

Complicated answer: No, you can still use local access if you need to, but need is a subjective term, and depending on what your needs are will depend on how complicated this answer actually becomes.

General answer: I just use the duckdns url, and if that is working for you and you have a reliable Internet connection, then you’re already sorted.

Hope this helps.

1 Like
3

I use the duckdns address internally. You can use the local IP address if you think you need to - you just need to navigate past the security warnings in your browser.

Why don’t you want to use the duckdns internally?

4

If your Internet is down, I assume your DuckDNS url won’t resolve. Yes? Personally I use 3rd party/external service minimally. I always use my internal IP. If I am away. I connect back using OpenVPN. Yes I get an SSL security warning, but it doesn’t bother me.

5

Best of both worlds is to use NGINX for the SSL Duck DNS stuff, and use http internally - saves a lot of complication if you keep hass HTTP only and use the proxy for the SSL piece as you can still access hass with the internal IP.

1 Like
6

Self signed cert works fine internally and externally. I do have a Duck DNS url so I can use custom Alexa intents, but I don’t use Let’s Encrypt and I never use my Duck DNS to access my HA gui. I don’t use any proxies either. One could use just Duck DNS for external resolution and self signed SSL and NAT through their router. I use HA on Raspbian, so this may not work for hass.io.

7

You can’t use self signed if you want to use Google Assistant component

8

I was unaware. Amazon has no problem with this.

9

Thanks everyone…

I was only asking because using the local address just felt ‘cleaner’ when on my own network. I have a reliable internet connection so it isn’t a real issue…
…although I had not considered that I would lose access if (when?) my internet does go down.

@DavidFW1960 - I don’t get warnings in my browser, it just flat refuses to let me through. But I expect you’ll tell me that is my fault for using Edge?! :wink:

10

Hahaha most probably Edge. Lol. There should be a way in there to bypass the error.

11

Ooops. Yes, you’re right. You can click ‘Details’ and be told ‘The hostname in the website’s security certificate differs from the website you are trying to visit.’
But under that in tiny writing I can ‘Go on to the webpage’. Although in red text it is ‘(Not recommended)’ :scream:

Thanks for the nudge (I shouldn’t have needed it) and it’s good to know Edge wasn’t really the problem :grinning: - actually I think it is a better browser than it is given credit for.

12

the problem for me is my internet doesnt stop working constently, its just that i have really slow 1mbps upload speed

13

I setup a DNS server and added a host which if the URL for my external IP was queried it would simply point it to the local IP. So internally every time the URL is queried it will point the user to the internal URL and externally it will use the external IP.

DNSMASQ - Add On

hosts:

1 Like
14

Brad,
I know 0 about DNS server configuration. Can you show me how you configured this (dnsmasq) ?
Thanks
Cbalas