Was not working anymore with Gluetun and qbittorrent

[ptoleme24]

Hello,

I wanted to use your wonderful qsticky with the 2 below images

• lscr.io/linuxserver/qbittorrent:latest
• qmcgaw/gluetun:latest

And it was not working. I'm not a dev at all, but I think I have a good understanding of IT.

I had (with AI Help) rewrote the qsticky.py and rebuild to make it work.

Little summary of the additions.

cookie_jar = aiohttp.CookieJar(unsafe=True)

headers={
"Referer": self.base_url,
"Origin": self.base_url
},

I attach the full file.

I hope it will help you. And thanks again for the hard work.

And I wish you a nice day

qsticky.py

[monstermuffin]

Thanks.

I’ve tested this locally against current linuxserver/qbittorrent:latest and the behaviour is much more specific.

For the standard qSticky setup, where qBittorrent is reached by hostname on the Docker network as shown in the docs, the current qSticky code works correctly as-is. Login succeeds, preferences can be read, and the listen port can be updated without needing the changes you posted.

If qBittorrent is accessed by IP address instead of hostname, I can reproduce a case where part of your change makes sense. In that setup, aiohttp may reject qBittorrent’s session cookie unless CookieJar(unsafe=True) is used.

I have patched qSticky for that use case, but only when QBITTORRENT_HOST is an IP address, so the relaxed cookie handling is only enabled for IP-based configurations.

One note: if you are going to patch code, it helps to understand exactly which change solved the issue. In this case the posted patch mixes the actual fix with other changes that do not appear to be necessary, which makes it harder to review. It also would have helped to mention that your setup differs from the README example, since this does not reproduce in the standard documented configuration.

Still, the report was useful, and I will attach the fix soon. Please consider using the official image so that you can stay updated.

[ptoleme24]

HelloSorry for all the lacks. Like said in the issue : I m not devAnd I used AI. That’s why I sent you back the py file. And all the infos I could gather. And I m also new to Gitlab :)Thanks and have a nice dayNicolas MelotLe 24 mars 2026 à 19:14, muffn_ ***@***.***> a écrit :monstermuffin left a comment (monstermuffin/qSticky#84) Thanks. I’ve tested this locally against current linuxserver/qbittorrent:latest and the behaviour is much more specific. For the standard qSticky setup, where qBittorrent is reached by hostname on the Docker network as shown in the docs, the current qSticky code works correctly as-is. Login succeeds, preferences can be read, and the listen port can be updated without needing the changes you posted. If qBittorrent is accessed by IP address instead of hostname, I can reproduce a case where part of your change makes sense. In that setup, aiohttp may reject qBittorrent’s session cookie unless CookieJar(unsafe=True) is used. I have patched qSticky for that use case, but only when QBITTORRENT_HOST is an IP address, so the relaxed cookie handling is only enabled for IP-based configurations. One note: if you are going to patch code, it helps to understand exactly which change solved the issue. In this case the posted patch mixes the actual fix with other changes that do not appear to be necessary, which makes it harder to review. It also would have helped to mention that your setup differs from the README example, since this does not reproduce in the standard documented configuration. Still, the report was useful, and I will attach the fix soon. Please consider using the official image so that you can stay updated. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[monstermuffin]

Fixed in #86.

Please use the image from this repo and let me know if you still have issues.