Open maliiiith opened 4 months ago
Not sure if it's related, but I was having the same issue in qbittorrent 5.0.0. Turned out the scheduler was ignoring the timezone set in compose.yml, and used UTC instead. Configuring the scheduler times in UTC fixed it for me.
qBittorrent & operating system versions
qbittorrent-nox: 4.6.5-1
What is the problem?
Scheduling an alternative rate limit does not work. It always stays on the current state of the alternative rate limit toggle, even if I restart / tear up and recreate the container.
If I enable the rate limit manually, and when the scheduled start time comes, it will automatically get switched off. But it wouldn't automatically turn on at the scheduled end time.
Steps to reproduce
Additional context
Log(s) & preferences file(s)
docker-compose.yml
qBittorrent.log