#NGINX - for internal use only.

1 messages · Page 1 of 1 (latest)

visual swift
#

The ONLY reason I installed Lets Encrypt is so I could get the mic to work on Assistant. Other than that, no reason.
Now that my instance uses https for everything there are several other things that don't work. I don't have time to dive into each one and fix them. So, how might I configure NGINX or get the mic to work w/out https?
I cannot set up remote access since I use Starlink. So I subscribe to Nabu Casa for remote access and have since it was created.

winter wasp
#

You need https for the mic; that's a restriction imposed by browsers that neither you nor home assistant has control over in this case

visual swift
#

I guess a self signed SSL cert might be the best route here.

winter wasp
#

I'm not sure if that would meet the browser requirement, but you could research that

visual swift
#

actually, no, that wont work. I still need to access HA w/ http for my apps, and https for browsers/companion app.

#

it turns out Im not the only one in this pickle... I've been scouring search results for hours.

#

I honestly hate how complicated SSL is.

winter wasp
#

You may need to figure out the other things that aren't working individually, really. I'm running a somewhat similar setup but it did take some doing -- nginx & letsencrypt with a DNS challenge to cloudflare for local access only, with Nabu Casa for external access, with a DNS name set up in NC and my modem to make the URL always the same (to avoid the annoying reloads in the app, mostly)

#

With nginx doing SSL, you should be able to still access over HTTP on port 8123, with https on 443