-
-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run overseerr on subpath, Base URL #274
Comments
This comment has been minimized.
This comment has been minimized.
You could always run it through a proxy on a subdomain, if your setup permits. Subpath will take some time to figure out. Might be awhile :( |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Isn't this just a matter of setting the baseurl in next config and doing namespace in express? Can you elaborate on what is hindering this @sct ? |
iirc |
Oh, yeah that's true. So the solution for us would be to prepend every use we have of express, links etc with an env variable we can pass in to the docker image for instance? |
Sounds a little hacky, unless you have something centralized that would generate links already. I didn't check your codebase yet. I'd personally settle with setting it at build-time, it's not often you will change this i feel. |
Changing base path in next.config.js is only part of solution. It works and makes app to listen on correct base path (this is a build time setting). I've tried it and it works. I was planning to do this, but was busy past few weeks finishing #538. But if somebody is doing this, then let me know and I won't look at this. |
This comment has been minimized.
This comment has been minimized.
As far as I understand it, setting the base url at build time doesn't work super well with Docker because generally a base url change will require the frontend to be recompiled, which means that you'd either have to
Neither is very appealing in the long run, though they're both far better in the short term than not being able to use the app at all (for many of our use-cases). To be able to set the base url at runtime, you'd need a couple things:
|
This comment has been minimized.
This comment has been minimized.
All, There is an unsupported workaround in the overseerr docs. Please use it at your own risk! This could break at any point. No support will be given for this workaround. If you are having issues please verify that it is reproducible when accessing overseerr directly! https://docs.overseerr.dev/extending-overseerr/reverse-proxy-examples#nginx |
And to be clear, we are still looking into building this support into Overseerr directly. But ETA for that is still unknown. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
@ElMoselYEE wrote:
your fork is gone :( @mmozeiko wrote:
|
Unfortunately with version 1.30.0 of Overseerr the workaround in the documentation for this has broken: https://docs.overseerr.dev/extending-overseerr/reverse-proxy I had to revert back to 1.29.1 to get it working again. |
There is already a fix. Check out the support channel in our discord. |
When testing this with subfolders I noticed that the currently suggested sub_filter rules left certain parts broken, such as if you refreshed the page it wouldn't work since the URL wouldn't be correct. It works when clicking around, but a refresh would break. "sw.js" and "offline.html" were also missing. In case someone else is interested, this is what I came up with for nginx:
|
This comment was marked as spam.
This comment was marked as spam.
After a nice chat with @danshilm at Discord I revisited my sub_filter rules to make sure Web Push and PWA was working, it turned out they needed some additional tuning. I don't know if it works on iPhone, but it works in Chrome on my Samsung phone. If Overseerr would run in a subfolder (just about anything so that rewrites can go against the subfolder instead of /) by default this could probably be shortened to a few lines. Due to the many special corner cases etc this is probably very brittle and could break at next update, but this is what I came up with:
|
If Overseerr was changed to use relevant paths rather than / wouldn’t that solve the issue too?
css/file.casimages/file.png ……etc Rather than /css/file.cas/images/file.png ……etc
|
This seems to be working. Thanks a lot 😃 |
This configuration didn't work well for me. When requesting a movie, overseerr seems to be prefixing radarr's root folder with the base path as well, causing the Missing Root Folder error in radarr Edit: Removing |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as spam.
This comment was marked as spam.
I added this line to enable the new image caching feature:
But something isn't working quite right still. Maybe there is something else needed? On the first page load of a movie detail page, the URI for the image will be for example:
This doesn't load. This image does load. |
You can try it like this |
Are there any configs for this to work in Apache and base URL? domain.tld/overseerr |
i'm very interesting in this!!! have you find a solution with apache ? |
Since there seems to exist mainly misunderstanding of what the issue with base URLs are, especially how the fixes for subdomains and matching paths do not apply for path rewriting (you just can't, especially without insane overhead, imagine subdomains working being more of a fluke than actual functionality). Here's an apt writing about the subject: Long story short, with all URI factors in play (actual compatibility and standard implementation), implement "URL Base" support or watch the community forced to transition elsewhere. |
Still no progression? |
Is your feature request related to a problem? Please describe.
I'm reverse-proxying all services on main domain with caddy. Like https://example.com/radarr/ and https://example.com/sonarr/ and I want to do same with https://example.com/overseerr/
But currently it expects to be available on / path.
Describe the solution you'd like
Solution would be either to use relative URL's throughout the project. Or allow to specify base url/path in startup parameters, like PORT is specific in env variables. Like
export BASE=/overseerr
would be good enough for me.The text was updated successfully, but these errors were encountered: