Overseerr and caddy possible?

1. Caddy version (caddy version):v2.4.6 h1:HGkGICFGvyrodcqOOclHKfvJC0qTU7vny/7FhYp9hNw=

2. How I run Caddy: caddy start

a. System environment: Windows 10

d. My complete Caddyfile or JSON config:

domains {
        tls email@gmail.com
        basicauth /movies/* {
                user PasswordHash        }
        basicauth /series/* {
                user PasswordHash
        redir /movies /movies/ 308
        redir /series /series/ 308
        redir /overseerr /overseerr/ 308
        reverse_proxy /movies/* localhost:7878
        reverse_proxy /series/* localhost:8989
        route  /overseerr/* {
                uri strip_prefix /overseerr
        log {
                output file access.log

3. The problem I’m having:

I’m trying to get Overseerr working with reverse_proxy.

When I goto https://my.domain.tld/overseerr it redirects me to https://my.domain.tld/login instead of https://my.domain.tld/overseerr/login

If I remove the uri strip_prefix /overseerr I get the following: ERR_TOO_MANY_REDIRECTS

4. Error messages and/or full log output:

5. What I already tried:

rewrite /login* /overseerr/login

6. Links to relevant resources:

You’re probably running into this:

Best to use a subdomain for each service instead.

Just to follow up on this one, I also run Overseerr; but, unlike my Sonarr/Radarr/NZBGet/etc, it gets its own subdomain.

Base URLs cannot be configured in Overseerr. With this limitation, only subdomain configurations are supported.

They actually do provide a list of header and HTTP filter rewrites - in the form of an explicitly unsupported nginx config - that can be converted to Caddy config to hopefully achieve the same explicitly unsupported results (as in part 2.B. of the subfolder problem wiki post), but I’d recommend not bothering.

1 Like

Thanks for the reply guys, I’ll go with the subdomain.

1 Like

This topic was automatically closed after 30 days. New replies are no longer allowed.