![]() ![]() network TLD so a great suggestion would be work or work. You need a domain name that you own that you can use for your network. The HTTPS support, in this case, is just to secure data being transferred on your local network. Check out Nabu Casa ($5/month) to access Home Assistant outside your network or looking into setting up WireGuard/VPN (coming in a later article). To reiterate, this does not allow you to access your services outside your network. Every machine on the network knows where to access automatically. ![]() Don’t want to open any ports on my router for validation or usage.Wanted to access my services at subdomains like and.To summarize, my requirements when I started this project were: Therefore, I wanted to get HTTPS working without having to open any ports on my router. I’m okay using VPN (or WireGuard) to connect to my network to use my application. I run lots of different services on my network and don’t want them exposed via the reverse proxy to the internet. If you’re like me, you’re a bit wary about forwarding ports on your router to your local network. Maybe a bit overkill, but it does give you the nice green badge in your browser too. This will give us a secure connection on our LAN so that when we connect to the application we know there is no one listening while on our network. On top of creating a reverse proxy in today’s article, we’ll also be adding HTTPS support via Let’s Encrypt. For example, instead of accessing Home Assistant at I can instead type. What is a reverse proxy? It allows you to access your services at a nice easy to remember URL rather than an IP Address and port. If you’ve got a slew of different applications running on your home network, it might be time to add a reverse proxy. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |