Repository navigation
Conversation
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Seemed to resolve the issue I was having with 401 errors on login when upgrading to 5.2.x. Not sure what other maintainer validation is needed here (or backwards compatibility requirements/testing), but commenting to avoid the bot from auto closing it. |
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Bump! |
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Description
Fix qBittorrent CSRF 401 behind reverse proxy on v5.2.0+.
Replaces
Host $upstream_app:$upstream_portwithHost $hostand addsOrigin "https://$host"so the CSRF check in v5.2.0+ passes. RemovesReferer ''(old workaround, no longer needed).Applied to
qbittorrent.subfolder.conf.sampleandqbittorrent.subdomain.conf.sampleacross all location blocks.How Has This Been Tested?
Tested with SWAG (linuxserver/nginx) proxying linuxserver/qbittorrent v5.2.x. 401 resolved with these headers. Both subfolder and subdomain configs verified working.
References