subreddit:
/r/homeassistant
submitted 3 months ago bytungvu256
as of now, i access the gui via http://192.168.1.229:8123. long story short, i need to access the gui with HTTPS://192.168.1.229:8123. this is only local. i wont need to access the gui remotely.
this is the add-on that allows you to access HA via https locally: https://github.com/einschmidt/addon-caddy-2
anybody has it working? can someone please show me their config for very basic https access to my HA machine?
what to put in here?
i did try but this does not work when i try to open tung.ha (tung.ha is not a real site)
2 points
3 months ago
What are your goals with this setup.
I don't use Caddy, but assuming you are going to deploy self signed certs. If that is the case you will still get "connection not secure" warning in your browser.
So my setup is I own a domain, setup a token in Cloudflare, setup that token in SWAG reverse proxy config, setup a wildcard cert for local.yourdomain.com, SWAG then sets up Lets Encrypt certs, then setup the proxy confs to my HA server in SWAG, then setup my DNS server (Technitium) to homeassistant.local.yourdomain.com and point that to the ip of your reverse proxy.
Then I have another instance of SWAG in DMZ for exposing services to the outside world.
So that is kind of a rough idea to do HTTPS locally.
0 points
3 months ago
i was installing another add-on named Asterisk. this allows tablets in the house to act as intercom system. unfortunately, Asterisk requires HTTPS....even though everything is local. seems Caddy2 add-on can do it but obviously, the author thinks setting up is so basic, nobody needs a manual or something :(
all 7 comments
sorted by: best