Accessing HA locally after installing Letsencrypt and Duckdns

Configuration
1

After a bit of effort I have managed to get secure access. to my Home Assistant. After finding thus post

I found out to use https://locall_ip:8123. to get access on my local network. This access is shown as non secure by my browser. Do I need to worry about chasing that down??

2

All certificates are only valid for the domain name it was created for. Your local IP is not a match for the domain, so it will never be valid. There are a couple of things you can do.

  1. don’t use https for local connection
  2. if you’re using a PC to browse HA, you can edit your hosts file so the domain will point the local IP
  3. if your router supports hairpinning, the domain lookup will work on your local network

I used to believe that most routers did hairpinning, but that is not true at all. My network is really weird. Hairpinning works for wireless connections but not for wired connections. Therefore, on my PC I edited my hosts file, and it just works on my phone because its wireless. Weird.

3

Thanks for your prompt response.

IF I dont use https : I can not connect to my local HA. When I use https. I get a not secure warning on my desk. I added the demand to my hosts. on my desktop (which is what yor8 are calling a PC. Ny router supports hand spring . Do I really care of my local commection is not secure??

4

Locally, no. Internet wide, definitely yes.

5

This is why I started using Nginx Proxy Manager (NPM). It lets you keep your internal local addresses (http) and provides SSL for your domain/subdomains for external access (https). It does this by only forwarding ports 80 (for Let’s Encrypt services) and 443 (for external access to your domain/subdomains), so you don’t have to forward other ports to access other services you might be hosting on your local network. It’s a win-win-win all around. Fair warning - if you attempt to setup NPM, it does come with a learning curve and a lot of the documentation and walk-throughs available on the interwebz are older and convoluted. The trickiest part, my opinion, is making sure you have the right trusted proxy subnet. Which, if you’re using HAOS on bare metal or via hypervisor, should be the docker subnet that HA core and any other Apps you have installed are using.

6

I know a lot of people like nginx family. but I am an old dog VERY old and semi comfortable with adobe. Thanks for your input I am using HAOS on a linux virtual machine. running on a Mac OSX host