origin
(Ben Heynow)
January 11, 2021, 8:42pm
1
Thanks so much for taking the time to read my post and thanks for any help you give!
1. Caddy version (caddy version
):
Caddy v2 (v2.2.1)
2. How I run Caddy:
I’m running Caddy with elevated windows command prompt
a. System environment:
Windows 10 20H2
b. Command:
caddy.exe start
caddy.exe stop
c. Service/unit/compose file:
NA (I think)
d. My complete Caddyfile or JSON config:
myddns.com:80 {
respond ":-P" 403
}
myddns:443 {
respond ":-P" 403
}
myddns.com:9100 {
reverse_proxy 127.0.0.1:8096
}
myddns.com:10500 {
reverse_proxy 127.0.0.1:10000 {
header_up X-Forwarded-Host {host}:10500
header_up -Origin
header_up -Referer
}
}
3. The problem I’m having:
I am trying (and failing) to hook up qbittorrent’s WEBUI with a reverse proxy via caddy v2.
4. Error messages and/or full log output:
NA
5. What I already tried:
I have forwarded port 10500 to 10000 on the server running qbittorrent; I’ve also setup the WEBUI to use port 10000.
I’ve tried to hack together a v2 caddyfile for this, using caddy v1 files as a base (e.g. Reverse Proxy With QBittorrent Web UI ) and trying to update the language so its v2 compliant.
The relevant bit in my caddyfile is:
myddns.com:10500 {
reverse_proxy 127.0.0.1:10000 {
header_up X-Forwarded-Host {host}:10500
header_up -Origin
header_up -Referer
}
}
Trying to access the WEBUI with
https://myddns.com:10000
then I reach a webpage that says ‘Unauthorized’ and nothing else.
I can confirm that I am able to reach the qbittorrent WEBUI with
192.168.1.67:10000
6. Links to relevant resources:
I’m trying to setup a reverse proxy to access the QBittorrent web UI. I found this post on the forums: qBittorrent Web UI -- Reverse Proxy Help - #2 by Whitestrake but I still can’t get it to work.
This is what I have in my Caddyfile:
localhost:4488, 192.168.1.205:4488 {
proxy / 127.0.0.1:9292 {
header_upstream X-Forwarded-Host {host}:9292
header_upstream Origin ''
header_upstream Referer ''
}
}
It returns an 502 Bad Gateway error when I attempt to go to localhost:4488
The following …
You can actually use {hostport}
in Caddy v2. But I’m not why this would be necessary
Maybe you can try to add header_up Host 127.0.0.1:10000
as well, since the Host
header in Caddy v2 is inherited from the original request.
Either way, if that doesn’t fix it, I can try myself tonight on my Windows machine.
origin
(Ben Heynow)
January 11, 2021, 8:55pm
3
Amazing!
header_up Host 127.0.0.1:10000
totally worked!
I’ve also taken your other suggestion on board and my caddyfile snippet now works like this:
myddns:10500 {
reverse_proxy 127.0.0.1:10000 {
header_up Host 127.0.0.1:10000
header_up X-Forwarded-Host {host}:{hostport}
header_up -Origin
header_up -Referer
}
}
Thank you so much!
You misunderstood, that should be just {hostport}
, because {hostport}
is the host plus the port, already.
Glad it worked!
origin
(Ben Heynow)
January 11, 2021, 9:01pm
5
Oops. Thanks for catching my mistake.
So, just for completeness x2 (in case any one is stuck in the future) my caddyfile looks like this
myddns:10500 {
reverse_proxy 127.0.0.1:10000 {
header_up Host 127.0.0.1:10000
header_up X-Forwarded-Host {hostport}
header_up -Origin
header_up -Referer
}
}
Thanks again!
1 Like
system
(system)
Closed
February 10, 2021, 8:42pm
6
This topic was automatically closed after 30 days. New replies are no longer allowed.