I have overseer running on docker at 192.168.29.2:5055
Overseerr doesn’t support configuring the base_url and hence I cannot simply use reverse_proxy /overseerr/* 192.168.29.2:5055
I found the following issues on github #3266 and #2813 and as suggested I am using the above Caddyfile.
handle_path seems to strip the /overseerr in the request properly as the page is redirected to login, but the problem is that it is being redirected to https://example.duckdns.org/login instead of https://example.duckdns.org/overseerr/login. I get a blank page.
What should I do to make sure the response also contains the /overseerr subpath?
4. Error messages and/or full log output:
This is the response I get using curl -v https://example.duckdns.org/overseerr
I understand that a subdomain is a better route to take but duckdns provides 5 subdomains max per account. I am already using them for other services like nextcloud. It would be a lot more convenient if there was a way to run these services on a subpath instead.
I am not sure how it can be done but is there a way to detect if the response coming from the service is changing the URL. If so maybe something can be done to ensure the URL always has the subpath prefixed to it. Maybe a rewrite rule that could do this but on the response?
No, you have unlimited. You don’t need to register a new duckdns domain, you do a subdomain of your duckdns domain. Like I wrote above, a 4th level label. DuckDNS resolves all subdomains of your registered domain to the same IP address as the main domain.