Alternative rate limit scheduler is not working properly on qbittorrent-nox

[maliiiith]

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

1. Spin up a clean qbittorrent-nox container.
2. Apply an alternative rate limit schedule (where it should change the state the moment you save, at least how that's how it works on qBittorrent desktop app.)

Additional context

Log(s) & preferences file(s)

docker-compose.yml

services:
  qbittorrent-nox:
    image: docker.io/qbittorrentofficial/qbittorrent-nox:latest
    container_name: qbittorrent-nox
    restart: always
    environment:
      QBT_EULA: accept
      QBT_VERSION: "latest"
      TZ: "Asia/Colombo"
    ports:
      - 6881:6881/tcp
      - 6881:6881/udp
      - 8080:8080/tcp
    tmpfs:
      - /tmp
    tty: true
    volumes:
      - ./downloads:/downloads
      - ./config:/config

qBittorrent.log

(N) 2024-07-16T02:36:53 - qBittorrent v4.6.5 started
(N) 2024-07-16T02:36:53 - Using config directory: /config/qBittorrent/config
(N) 2024-07-16T02:36:53 - Trying to listen on the following list of IP addresses: "0.0.0.0:6881,[::]:6881"
(I) 2024-07-16T02:36:53 - Peer ID: "-qB4650-"
(I) 2024-07-16T02:36:53 - HTTP User-Agent: "qBittorrent/4.6.5"
(I) 2024-07-16T02:36:53 - Distributed Hash Table (DHT) support: ON
(I) 2024-07-16T02:36:53 - Local Peer Discovery support: ON
(I) 2024-07-16T02:36:53 - Peer Exchange (PeX) support: ON
(I) 2024-07-16T02:36:53 - Anonymous mode: OFF
(I) 2024-07-16T02:36:53 - Encryption support: ON
(I) 2024-07-16T02:36:53 - Successfully listening on IP. IP: "127.0.0.1". Port: "TCP/6881"
(I) 2024-07-16T02:36:53 - Successfully listening on IP. IP: "127.0.0.1". Port: "UDP/6881"
(I) 2024-07-16T02:36:53 - Successfully listening on IP. IP: "172.24.0.2". Port: "TCP/6881"
(I) 2024-07-16T02:36:53 - Successfully listening on IP. IP: "172.24.0.2". Port: "UDP/6881"
(I) 2024-07-16T02:36:53 - Successfully listening on IP. IP: "::1". Port: "TCP/6881"
(I) 2024-07-16T02:36:53 - Successfully listening on IP. IP: "::1". Port: "UDP/6881"
(I) 2024-07-16T02:36:53 - UPnP/NAT-PMP support: ON
(W) 2024-07-16T02:36:53 - Couldn't load IP geolocation database. Reason: No such file or directory
(N) 2024-07-16T02:36:54 - Using built-in WebUI.
(W) 2024-07-16T02:36:54 - Couldn't load WebUI translation for selected locale (C).
(N) 2024-07-16T02:36:54 - WebUI: Now listening on IP: *, port: 8080
(I) 2024-07-16T02:36:54 - IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: Mon Jul 1 00:34:52 2024.
(I) 2024-07-16T02:36:54 - Successfully updated IP geolocation database.
(I) 2024-07-16T02:36:54 - Detected external IP. IP: "x.x.x.x"
(N) 2024-07-16T02:37:28 - WebAPI login success. IP: ::ffff:172.24.0.1
(N) 2024-07-16T02:37:43 - WebUI translation for selected locale (en) has been successfully loaded.
(W) 2024-07-16T02:39:29 - UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP: no router found"
(W) 2024-07-16T02:39:29 - UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP: no router found"