Frigate not loading when using a subpath with a reverse proxy

[Mario1159]

Frigate has worked well for me in the root path, but when serving the app in a subpath such as <mydomain>/frigate I had some problems.
Previously I was using nginx as my reverse proxy. With just the proxy_pass specified the page didn't load, just the icon was retrieved, but when forwarding the header as followed it worked.

location /frigate {
  proxy_set_header Host $host;
  proxy_set_header X-Real-IP $remote_addr;
  proxy_set_header X-Ingress-Path "/frigate";
  proxy_pass https://<mydomain>:5000/;
}

Now I'm migrating to traefik, but I came back to the previous problem when the page stays in blank.
This is my entrypoint:

entrypoints:
  web:
    address: :80
    forwardedHeaders:
      insecure: true

And these are my docker labels:

labels:
  - "traefik.enable=true"
  - "traefik.http.routers.frigate.rule=(Host(`<mydomain>`) && Path(`/frigate`))"
  - "traefik.http.routers.frigate.entrypoints=web"
  - "traefik.http.services.frigate.loadbalancer.server.port=5000"
  - "traefik.http.middlewares.frigateHeaders.headers.customrequestheaders.X-Ingress-Path=/frigate"
  - "traefik.http.routers.frigate.middlewares=frigateHeaders@docker"

[newmindJP]

same issue here - how to fix this? is there another header missing?

[newmindJP]

I did some further investigations - whatever page I load within sub-path "/frigate/" the UI always return the default index file - e.g. I extracted the link to css file (/frigate/assets/index-9ad6681a.css) and will get the same index file as response.
in the response the sub-path is listed correctly: <script>window.baseUrl="/frigate/";</script>
I'm more than happy for any hint (already spent several hours on this topic)

also here in the reference I cannot see any other important headers: https://github.com/blakeblackshear/frigate-hass-addons/blob/main/frigate_proxy/rootfs/etc/nginx/includes/proxy_params.conf

[newmindJP]

found out that nginx try to access file "/opt/frigate/web/frigate/assets/index-9ad6681a.css" instead of "/opt/frigate/web/assets/index-9ad6681a.css" - seems that he add the path from the url sub-path also to the file path. Any ideas?

[vajonam]

I couldn't get the subpath to work, i have moved to subdomains as its more compatible with more apps like frigate. the instructions are on the docs page.

[newmindJP]

this is not an option for me - I could make it to work with a "dirty hack":
copied the nginx.conf locally (here is the reference: https://github.com/blakeblackshear/frigate/blob/dev/docker/main/rootfs/usr/local/nginx/conf/nginx.conf) and mapped per docker-compose

    volumes:
      - ./nginx.conf:/usr/local/nginx/conf/nginx.conf

then I added following line (~line 55) below "listen 5000;":

     server {
          listen 5000;
          rewrite ^/frigate(/.*)$ $1 last

If I read the whole file I have no idea how this could ever work just with setting header "X-Ingress-Path"

[bdoiron74]

I've stumbled onto this thread searching for an answer to my question.

Seeing your "X-Ingress-Path" header option solved it for me.. and to avoid having to type the trailing slash, I'm using a redirect:

location = /frigate {
    return 302 /frigate/;
}

location /frigate/ {
  proxy_http_version 1.1;
  proxy_cache_bypass $http_upgrade;
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection $http_connection;
  proxy_set_header Host $http_host;
  proxy_set_header X-Ingress-Path "/frigate";
  proxy_set_header Authorization "";
  proxy_pass https://frigate:5000/;
  access_log off;
}