qBittorrent

For users that run qBittorrent via Microsoft IIS as a reverse proxy some extra headers are needed. You must install the URL Rewrite and Application Request Routing addons first. Reverse proxy support will be enabled when creating the first rule.

In the IIS Manager, Click on the machine name to view general configuration options
Click on Application Request Routing Cache
On the Right hand side, Click on Server Proxy Setting, then tick the Enable Proxy box
Create a new site that will handle the reverse proxy requests
Select the site and then open URL Rewrite
On the right hand side, open View Server Variables
Click Add and in the box that appears enter HTTP_X_Forwarded_Host
Repeat this for HTTP_X_Forwarded_For and RESPONSE_Set_Cookie
Return to the rules page
Open Add Rules and select Reverse Proxy
Enter the server IP:Port without http:// (for example 127.0.0.1:8080), then click OK
Open the new rule and change the path to a subdirectory if needed (for example qbweb/(.*) = http://domain.tld/qbweb/)
Under Server Variables add the following rules:

Server variable name Value

HTTP_X_Forwarded_Host {HTTP_HOST}

HTTP_X_Forwarded_For {REMOTE_ADDR}
Apply and return to the rules page
Open Add Rules and select Blank rule under Outbound rules
Enter the name Update Cookie Path
Change Matching scope to Server Variable
Enter the variable name RESPONSE_Set_Cookie
Enter the pattern ^(.*; path=/)$
Under Action Properties enter the value {R:1}; Secure
Apply

Server variable name	Value
HTTP_X_Forwarded_Host	{HTTP_HOST}
HTTP_X_Forwarded_For	{REMOTE_ADDR}

The result should look similar to this in your web.config (Note: you must use the GUI first so reverse proxy support is enabled in IIS):

            <rules>
                <rule name="Reverse Proxy">
                    <match url="qbweb/(.*)" />
                    <action type="Rewrite" url="http://127.0.0.1:8080/{R:1}" />
                    <serverVariables>
                        <set name="HTTP_X_Forwarded_Host" value="{HTTP_HOST}" />
                        <set name="HTTP_X_Forwarded_For" value="{REMOTE_ADDR}" />
                    </serverVariables>
                </rule>
            </rules>
            <outboundRules>
                <rule name="Update Cookie Path">
                    <match serverVariable="RESPONSE_Set_Cookie" pattern="^(.*; path=/)$" negate="false" />
                    <action type="Rewrite" value="{R:1}; Secure" />
                </rule>
            </outboundRules>

You can use HTTPS to access the URL via IIS and it will use HTTP to communicate with qBittorrent. There is no need for HTTPS on localhost.

Note: If you find yourself seeing WebAPI login failure. Reason: IP has been banned, IP: 127.0.0.1 and needing to restart qBittorrent, you may want to set the ban after failure count to 0 which will disable it.

This tutorial is based on the assistance of Chocobo1 in this thread and in this thread for version 3.3.13 onwards.

General

Troubleshooting

External programs

Search plugins

List of unofficial search plugins

Themes

Translation

How to translate qBittorrent

WebUI

WebUI API

State	Version
Current	qBittorrent ≥ v4.1
Previous	qBittorrent v3.2.0 - v4.0.x
Obsolete	qBittorrent < v3.2.0

General

Troubleshooting

External programs

Search plugins

Themes

Translation

WebUI

WebUI API

WebAPI clients

Alternate WebUI

Reverse proxy setup for WebUI access

WebUI HTTPS configuration

Linux

Development

Compilation

*BSD, Linux

macOS

Windows