qBittorrent and Caddy reverse proxy

[francislavoie]

@unknownsoldier08

When I use curl -v to the subfolder, I get the following response;

C:\>curl -v media.personaldomainname.com/qbittorrent

You’re just getting an HTTP->HTTPS redirect here. There’s no problem there.

@unknownsoldier08

<hr><center>openresty</center>

This looks suspicious though. What’s openresty? Seems like it’s causing the redirect.

@unknownsoldier08

			header_up Host localhost:8080
			header_up X-Forwarded-Host {host}:8080
			header_up -X-Forwarded-For
			header_up -Origin
			header_up -Referer

I don’t think you need any of these lines. Caddy already sets the appropriate headers.

@unknownsoldier08

http://media.personaldomainname.com {
	handle /qbittorrent* {

I don’t recommend using a subpath for proxying services like this; they typically need specific support for being run under a subpath. It’s better to use a subdomain for each service. See this article for details:

The "subfolder problem", OR, "why can't I reverse proxy my app into a subfolder?"

Have you ever tried to reverse proxy an app into its own little subfolder of your domain name? Makes things neat, doesn’t it? Using example.com/foo/ for one app, example.com/bar/ for another. If you’re coming here from one of the selfhosted communities, you might be thinking along the lines of example.com/sonarr/, example.com/radarr/ etc. Chances are, you’ve tried some configuration along these lines: example.com { redir /sonarr /sonarr/ handle_path /sonarr/* { reverse_proxy localhost…