From 64cbe3dd1fd8b89ae04a5f6bfd446a5b6063f480 Mon Sep 17 00:00:00 2001 From: Greg Hellings Date: Thu, 21 Apr 2022 07:46:52 -0500 Subject: [PATCH] Fix internal proxies --- hosts/2maccabees/home-assistant.nix | 5 +---- hosts/2maccabees/vhosts.nix | 1 - 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/hosts/2maccabees/home-assistant.nix b/hosts/2maccabees/home-assistant.nix index d935184..ac77178 100755 --- a/hosts/2maccabees/home-assistant.nix +++ b/hosts/2maccabees/home-assistant.nix @@ -93,10 +93,7 @@ in # multiple layers of proxies, then add more of them in the list. The list also accepts subnet notation in case you have # multiple potentially incoming connections. So you could do "10.88.0.1/24", according to the docs. However, that has not # worked in my testing, as Home Assistant throws an error on start up saying that value is invalid - greg.proxies."smart.thehellings.lan" = { - target = "http://127.0.0.1:8123"; - ssl = false; - }; + greg.proxies."smart.thehellings.lan".target = "http://127.0.0.1:8123"; # Ensure that both ports are up and running. We keep 8123 directly open because we are on the LAN and sometimes want to connect # directly for troubleshooting Nginx configuration diff --git a/hosts/2maccabees/vhosts.nix b/hosts/2maccabees/vhosts.nix index 1d85381..1a2fd22 100644 --- a/hosts/2maccabees/vhosts.nix +++ b/hosts/2maccabees/vhosts.nix @@ -7,7 +7,6 @@ { greg.proxies."dns.thehellings.lan" = { target = "http://127.0.0.1:8384/"; - ssl = false; path = "/sync/"; };