February 2, 20224 yr My Home Assistant VM consistently loses accessibility via subdomain. SETUP SWAG In a docker container. Working as expected for all other apps (all those are in Docker). I followed the SpaceinvaderOne video to set up LetsEncrypt/SWAG and DuckDNS for this. .conf file for homeassistant has the IP of the VM in it, instead of a variable for upstream_app. "Host access to custom networks:" in Docker settings is Enabled Did this to see if it would resolve my issue. VM - Home Assistant OS (using this VM for the Supervisor as the Docker doesn't have it). TESTING Local access works fine. Remote access using IP:PORT works fine. Remote access through the subdomain works fine TEMPORARILY. This always breaks over x amount of time and the only way I can restore it is to reboot the VM. I do not see anything in the SWAG log to indicate something changing. I also don't see anything in the VM's log. Does anyone have any ideas about how this relationship behaves and where I should look to find out what's causing the subdomain to stop being correctly assigned.. or to stop working? Edited February 2, 20224 yr by BzzLghtyr
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.