At least they will pay your last month of service when you leave 👍. I agree that they should not have changed the terms later and then rolled back the pr and everything after they terminated the program.

It makes me wonder how much income this actually provided to AWS.

I tried something like this with Traefik just recently using add prefix and strip prefix rules. It had limited success until until I encountered an application that doesn’t have everything behind a sub path, Like /lovelace (home assistant)or something like that. If the application just basis it off the host with a root path, than you can’t really apply the prefix rule as the reverse proxy will not know how to route the request as the application is asking for a path that is not already a sub. You may come into this situation more often with several applications. I ended up just switching back to virtual hosts myself.

$80 1Gbps symmetrical fiber. Speed tests are usually 800+ down/1Gb up, but usually can get 1Gb down on steam games. Portland, Or

Same in Portland

Seems like someone has had this type of error before and the only way to restart HA was to remove the file. Though the issue wasn’t resolved but was perhaps fixed with an update. https://github.com/home-assistant/core/issues/85381

I’m wondering if the default configuration is finding something on the network that is producing this error. You could try starting home assistant without enabling the default configuration by omitting the line from configuration.yaml:

default_config:

Have you added anything to your network recently? By default I believe home assistant does auto discovery so it could be discovering something that is not fully compatible with.