I have a 100% reproducible problem concurrently running:
rqbit --log-file log.txt --socks-url "socks5://10.64.0.1:1080" download -e --overwrite -o ./ "${MAGNET}"
on v8.1.0 (and earlier versions).
The problem seems to be that the first invocation starts the server, the second detects this and tries to use it, but the API request fails.
Log of first process:
2025-06-12T11:44:18.673390Z INFO rqbit: increased open file limit limit=1048576
2025-06-12T11:44:18.756238Z WARN rqbit: Error checking HTTP API at http://127.0.0.1:3030/: error sending request
2025-06-12T11:44:18.756677Z INFO librqbit::session: Listening on 0.0.0.0:4240 for incoming peer connections
2025-06-12T11:44:18.756932Z INFO librqbit_dht::persistence: will store DHT routing table periodically filename="/root/.cache/com.rqbit.dht/dht.json"
2025-06-12T11:44:18.757731Z INFO librqbit_dht::dht: DHT listening on 0.0.0.0:37202
2025-06-12T11:44:18.757915Z INFO librqbit_dht::dht: starting up DHT with peer id 2d7251353330302d8a309251a4765288d4a271f3
2025-06-12T11:44:18.763962Z DEBUG dht:dht_framer: librqbit_dht::dht: error sending to [2a02:752:0:18::128]:25401: Address family not supported by protocol (os error 97)
2025-06-12T11:44:18.764177Z DEBUG dht:dht_framer: librqbit_dht::dht: error sending to [2a02:752:0:18::128]:25401: Address family not supported by protocol (os error 97)
2025-06-12T11:44:18.764331Z DEBUG dht:bootstrap{�[3mhostname�[0m�[2m=�[0m"dht.libtorrent.org:25401"}:find_node{�[3mtarget�[0m�[2m=�[0m"2d7251353330302d8a309251a4765288d4a271f3" �[3maddr�[0m�[2m=�[0m"[2a02:752:0:18::128]:25401"}: librqbit_dht::dht: error: Address family not supported by protocol (os error 97)
2025-06-12T11:44:18.764777Z DEBUG dht:dht_framer: librqbit_dht::dht: error sending to [2001:41d0:203:4cca:5::]:6881: Address family not supported by protocol (os error 97)
2025-06-12T11:44:18.764900Z DEBUG dht:dht_framer: librqbit_dht::dht: error sending to [2001:41d0:203:4cca:5::]:6881: Address family not supported by protocol (os error 97)
2025-06-12T11:44:18.765023Z DEBUG dht:bootstrap{�[3mhostname�[0m�[2m=�[0m"dht.transmissionbt.com:6881"}:find_node{�[3mtarget�[0m�[2m=�[0m"2d7251353330302d8a309251a4765288d4a271f3" �[3maddr�[0m�[2m=�[0m"[2001:41d0:203:4cca:5::]:6881"}: librqbit_dht::dht: error: Address family not supported by protocol (os error 97)
2025-06-12T11:44:18.791178Z INFO rqbit: starting HTTP API at http://127.0.0.1:3030
Log of second process:
2025-06-12T11:45:22.534190Z INFO rqbit: increased open file limit limit=1048576
2025-06-12T11:45:22.602450Z INFO rqbit: Connected to HTTP API at http://127.0.0.1:3030/, will call it instead of downloading within this process
2025-06-12T11:45:22.603110Z WARN rqbit: error adding <redacted> http://127.0.0.1:3030/torrents?overwrite=true&output_folder=.%2F&list_only=false -> 405 Method Not Allowed:
Best case for me would be if I could just disable the HTTP API, because I rely on each process ending when the respective torrent finishes.
I have a 100% reproducible problem concurrently running:
rqbit --log-file log.txt --socks-url "socks5://10.64.0.1:1080" download -e --overwrite -o ./ "${MAGNET}"on v8.1.0 (and earlier versions).
The problem seems to be that the first invocation starts the server, the second detects this and tries to use it, but the API request fails.
Log of first process:
Log of second process:
Best case for me would be if I could just disable the HTTP API, because I rely on each process ending when the respective torrent finishes.