[Bug]: Auth fails when serving Frigate at a subpath

[sorenisanerd]

Describe the problem you are having

I'm serving Frigate ([2637541]) at a subpath. When I submit my login credentials in the auth form, it fails, because they are submitted to /api/login, not <my subpath>/api/login.

web/src/api/index.tsx takes the baseUrl that nginx injects and sets it as Axios' default baseURL:

frigate/web/src/api/index.tsx

Line 7 in 2637541

axios.defaults.baseURL = `${baseUrl}api/`;

However, web/src/api/index.tsx is not imported (directly or indirectly) by web/src/login.tsx, so that setting is never applied on the login form.

Next, the onSubmit handler in web/src/components/auth/AuthForm.tsx targets /api/login, even though /api is included in the baseURL:

frigate/web/src/components/auth/AuthForm.tsx

Line 46 in 2637541

"/api/login",

If the onSubmit handler is successful, it redirects to / rather than my desired subpath:

frigate/web/src/components/auth/AuthForm.tsx

Line 57 in 2637541

window.location.href = "/";

Finally, the logoutUrl points to /api/logout, lacking my subpath.

Submitting PR to address all of this in a few moments.

Steps to reproduce

Serve Frigate at a subpath, with the root being handled by something else.

Version

0.14.0-2637541c

Frigate config file

Does not apply

Relevant log output

Does not apply

Operating system

Other Linux

Install method

Docker Compose

Network connection

Wired

Camera make and model

Does not apply

Any other information that may be helpful

No response

[sorenisanerd]

This issue remains. #12815 fixed it and it shows as merged, but if you look in the dev branch or the 0.14.1 branch, it's nowhere to be found.

[sorenisanerd]

Maybe it got lost during whatever this was (screenshot from #12815):

[sorenisanerd]

...and maybe other stuff got lost, too. ¯\_(ツ)_/¯

[sorenisanerd]

Hm. This may be a local problem for me. I seem to be referencing a branch or tag that no longer exists. Gosh, that would explain a lot.