Is there an existing issue for this?
Current Behavior
Might be related to qbittorrent/qBittorrent#21651
Docker image: lscr.io/linuxserver/qbittorrent:5.1.4-libtorrentv1
When connecting to the web UI via HTTP the browser gives the following error message as a response:
Cookie “SID” has been rejected because a non-HTTPS cookie can’t be set as “secure”.
The request being sent is /api/v2/sync/maindata?rid=1
The RID is not being incremented.
This results in the memory usage slowly increasing until container or system crashes. It doesn't appear to release the memory when you close the browser.
A work around is possible by using HTTPS, however I don't think allowing HTTP connections that result in a memory leak style situation should be allowed.
Expected Behavior
The web UI should be able to run without exhausting the server of memory.
Steps To Reproduce
- Connect to web UI via http
- Leave web UI running
- Watch memory usage increase.
Environment
- OS: Linux pi5 6.12.34+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.34-1+rpt1~bookworm (2025-06-26) aarch64 GNU/Linux
- How docker service was installed: apt-get install docker
CPU architecture
arm64
Docker creation
services:
qbittorrent:
image: lscr.io/linuxserver/qbittorrent:5.1.4-libtorrentv1
container_name: qbittorrent
Container logs
#Nothing useful ever printed in docker logs. Only shows startup message.
Is there an existing issue for this?
Current Behavior
Might be related to qbittorrent/qBittorrent#21651
Docker image: lscr.io/linuxserver/qbittorrent:5.1.4-libtorrentv1
When connecting to the web UI via HTTP the browser gives the following error message as a response:
Cookie “SID” has been rejected because a non-HTTPS cookie can’t be set as “secure”.The request being sent is
/api/v2/sync/maindata?rid=1The RID is not being incremented.
This results in the memory usage slowly increasing until container or system crashes. It doesn't appear to release the memory when you close the browser.
A work around is possible by using HTTPS, however I don't think allowing HTTP connections that result in a memory leak style situation should be allowed.
Expected Behavior
The web UI should be able to run without exhausting the server of memory.
Steps To Reproduce
Environment
CPU architecture
arm64
Docker creation
services: qbittorrent: image: lscr.io/linuxserver/qbittorrent:5.1.4-libtorrentv1 container_name: qbittorrentContainer logs
#Nothing useful ever printed in docker logs. Only shows startup message.