How to configure 2nd nginx (openresty) for ssl proxying?

[S-Przybylski]

Hi
what should I do to enhance a running Nginx Proxy Manager (not on hass os) to access Frigate?
Adding a simple additional location "/frigate" --> http://IP-Frigate:5000 besides Home Assistant doesn't help at all.

Wanted scenario:
Client --> https://IP-Synology:4443/frigate --> http://IP-Frigate:5000

Environment:
I use Frigate on a Raspi (IP-Frigate) and Home Assistant on Docker on Synology (IP-Synology).
In addition to that I have installed Nginx Proxy Manager on Synology (Docker) to provide interally SSL
I have created local certificates and imported them.
Home Assistant runs well.
I do not use subdomains.
No external connection defined.

[blakeblackshear]

Easiest way is to use a subdomain. If you can't do that, you can use nginx to inject a base url via the x-ingress-path header.

[simeon-walker]

I'm just trying this and there's something a little odd shows up. I have basically the same config as above.

When I go to the /frigate url I do get the page, however, when I click on a link such as Events, Cameras etc then the new page loads but the url shown in the browser is /events rather than /frigate/events

I'm not a JS programmer but I suspect the page is changing the url in response to the click but not taking the /frigate path into account. Since it's not a plain old page load to the browser, it looks wrong but did work.

Pressing reload on such a page will fail of course.

[thehijacker]

Same here but until I press reload all clicks are working. Done something better. Installed Wireguard VPN. Now can access all via local IP wnd port. Using Homer dashboard to bookmark all local IP addresses and port. Best combination ever.

[hack2spider]

I believ best thing is to run frigate on itself on a separate machine .. like this you can reach it with nginx ...

[simeon-walker]

It doesn't matter if you have a separate machine or where the nginx proxy runs. The issue is the way in which the web application handles the path through which it is accessed via the proxy.

[naanlizard]

This is still an issue, three years later. Any idea how to fix the URLs not updating properly to e.g. hostname.tld/frigate?

[mitchross]

I wrote an article on this https://mitchross09.medium.com/how-i-self-host-my-own-sites-and-applications-with-unraid-docker-authelia-and-cloudflare-1f0d8e6f8912

[yen9912]

This works for me. Set X-Forwarded-For to $proxy_add_x_forwarded_for instead of $remote_addr did it. Keeps the '/frigate' prefix even if you click on other links.

    server {
        location /frigate/ {
            proxy_pass http://frigate-ip:5000/;
            proxy_set_header Host $host;
            proxy_set_header X-Ingress-Path "/frigate";
            proxy_set_header X-Forwarded-Host $host:$server_port;
            proxy_set_header X-Forwarded-Server $host;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Scheme $scheme;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
        }
    }

Before adding X-Ingress-Path, I was getting forwarded to a blank page or Bad Gateway error. Thanks blakeblackshear