Hi,
I just set up my first home assistant and explore possibilities to access it and found a surprising road block.
How I usually go about this is to route the http port of the container providing webserver services (here homeassistant) to my (apache) webserver which does the http to https conversion, cert management, etc. The apache webserver is then visible from home and remote networks with the same url like https://my.full.dns/servicename/whatever
This requires the “servicename” as part of the urls generated by the service which seems to be impossible with ha. Really?
I seen many posts and the documentation that this is not possible for external urls, not sure if that is also valid for internal urls.
I know there is a workaround with subdomains, but these are very limited for me, so not usable for every service. I don’t want to end up with some/most services using paths and some using subdomains, the cert hassles, …
I don’t need that feature at that early stage of evaluating, so is there some work in progress providing this? Or is there a technical reason why this is not implemented/possible with home assistant?
It is very hard or even impossible to configure a (reverse)proxy to catch all urls for rewrite (and not rewrite urls just meant as text, not missing java script stuff, …)
Regards,
Joachim