Authorize via reverse proxy not working

[teunehv]

Home Assistant release with the issue:

Home Assistant 0.80.0 (via Hass.io)

Last working Home Assistant release (if known):

Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io

Component/platform:

https://www.home-assistant.io/components/google_assistant/

Description of problem:
I’m running Hass.IO behind a reverse nginx proxy.

    location /hassioproxy/ {
      include /config/nginx/proxy.conf;
      rewrite /hassioproxy/(.*) /$1 break;
      proxy_pass http://my.local.hassio:8123;

In configuration.yaml I have the entry

    http:
      base_url: https://my.external.url/hassioproxy

I can connect to the API endpoint at: https://my.external.url/hassioproxy/api/

When I browse to the authentication url: https://my.external.url/hassioproxy/auth/authorize
it redirects to: https://my.external.url/frontend_es5/authorize.html

So it seems the redirect doesn't take the reverse proxy into account.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

    http:
      base_url: https://my.external.url/hassioproxy

Traceback (if applicable):

Additional information:
Already confirmed by awarecan it's an issue, see
https://community.home-assistant.io/t/v0-80-new-google-assistant-auth-behind-proxy-redirect-issue/72994

[awarecan]

The issue is not about google assistant component, but for the HA in general. Do we want to support base_url with path? There are several 302 redirect in the code will redirect base on absolute path, if we want to fix it, we may need add virtual_path or something similar in http config.

[tschundler]

I was confused trying to set it up today. I have a variety of things on different paths like Octoprint, Jupyter Notebook, with authentication managed through the nginx.
Even if base_url doesn't support paths, X-Script-Name header would help. That's a standard approach for what I think you're imagining "virtual_path" configuration would be.

[marchingphoenix]

i use an nginx reverse proxy and do not currently have any issues on 83+
Can one of you please test and see if this is still a problem?

[benleb]

@marchingphoenix maybe you want to show us your nginx config?

[teunehv]

i use an nginx reverse proxy and do not currently have any issues on 83+
Can one of you please test and see if this is still a problem?

Just tested on 0.89, for the issue is still present.

@marchingphoenix can you post your nginx config perhaps?

[benleb]

It seems that nobody (from the home assistant team) cares about this, but why?!
Are there really just a hand full people which want to use a stable and extensively tested reverse proxy in front of (sometimes beta-like) home assistant?!

[awarecan]

Reverse proxy works, we have tons of guide in the community to show you the way. The issue here is about host HA in a virtual path, and it is complex. The most recent discussion at here: home-assistant/architecture#156

[teunehv]

Got it workin tonight via https://community.home-assistant.io/t/nginx-reverse-proxy-set-up-guide-docker/54802

Its not using the path but a subdomain, for me this workaround suits my needs for now.

[balloob]

Going to close this as we don't intend to support this now, and no one is going to work on this in the foreseeable future.