200Something went wrong... Code: 403 with qBittorrent WebUI

[steakhutzeee]

Hi :)

On my Odroid HC2 running OMV5 on top of Armbian i set up heimdall with this container https://hub.docker.com/r/linuxserver/heimdall

I'm also using qBittorrent with this container https://hub.docker.com/r/linuxserver/qbittorrent

I can reach the qBittorrent container just fine via Heimdall but when i try to put in my Web UI credentials in Heimdall to see the Enhanced App i receive the following pop up error:

"200Something went wrong... Code: 403"

Any idea why?

Thanks!

[bn326160]

Wanted to pitch in to mention I have the same issue on Docker on Ubuntu Server LTS 20.04.

However, when I added it anyway, it seems to be working?

[steakhutzeee]

Yes! It actually works, even with that error. That was not working when i opened the issue. Strange.

[jmu]

I googled and found the solution by reddit user u/joseamaria
Web UI Tab > Enable Cross-Site Request Forgery (CSRF) protection

https://www.reddit.com/r/docker/comments/gfkwwq/qbittorrent_webui_linking_problem/

[steakhutzeee]

I googled and found the solution by reddit user u/joseamaria
Web UI Tab > Enable Cross-Site Request Forgery (CSRF) protection

https://www.reddit.com/r/docker/comments/gfkwwq/qbittorrent_webui_linking_problem/

Hi,
the issue posted by the reddit user is different by mine.

Anyway i have that option disabled by long time and the issue is still present.

[steakhutzeee]

Actually with latest version of qbittorrent and heimdall the issue is present again, nothing happens when using qbittorrent credentials.

[ahmedelakkad]

r

Actually with latest version of qbittorrent and heimdall the issue is present again, nothing happens when using qbittorrent credentials.

Same!

[avdept]

Any update on this?

[Dexogen]

Well, I found workaround.

1. Connect qBittorrent container to the same docker network (e.g. heimdall_default).

$ docker inspect qbittorrent
...
"Networks": {
                "heimdall_default": {
                    "IPAMConfig": {},
                    "Links": null,
                    "Aliases": [
                        "7aca1bf06489",
                        "qbittorrent"
...
$ docker inspect heimdall
...
"Networks": {
                "heimdall_default": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": [
                        "heimdall",
                        "5a059215554e"
                    ]
...

2. Add this subnet into bypass whitelist (Options > WebUI > Authentication > Bypass authentication for clients)
   
3. Go to the Heimdall and insert URL the using internal ip or alias w/o username and password. If "Host Header Check" is enabled, then add an alias to the server's domains.
   
4. Success
   

[ProfessorX]

this one works for me on unraid.

[ChristophorusReyhan]

Works, but insecure 🤕

[Hurray0]

Any update?
I cannot use subnet bypass whitelist which is not safety for me.
Wish there can be other method to solving this problem

[ChristophorusReyhan]

Found it. Check your qbittorrent logs (for me /.local/share/qBittorrent/logs/qbittorrent.log).
If you got
(W) 2024-10-26T14:47:19 - WebAPI login failure. Reason: IP has been banned, IP: ::ffff:10.0.0.104, username: admin
Then try to reboot your qbittorrent service (for me systemctl restart qbittorrent-nox.service).

Test it again.