error: request to http://qbittorrent:8080/api/v2/torrents/properties failed, reason: socket hang up

[KyleSanderson]

No description provided.

[bakerboy448]

Not likely a bug..?

your qbittorrent instance did not respond after the timeout

https://stackoverflow.com/questions/16995184/nodejs-what-does-socket-hang-up-actually-mean

[KyleSanderson]

autobrr/go-qbittorrent#3 it's easily fixable, and common behaviour with qBittorrent.

[bakerboy448]

autobrr/go-qbittorrent#3 it's easily fixable, and common behaviour with qBittorrent.

TL;DR of the high level fix?

[mmgoodnow]

common behaviour with qBittorrent.

what is the common behavior here, restarting? or not responding to requests while it's running?

[KyleSanderson]

common behaviour with qBittorrent.

what is the common behavior here, restarting? or not responding to requests while it's running?

Both, unfortunately. Responses from my experience can take upwards of 90s, and sometimes require multiple attempts. Usually if another client is waiting for a response they're queued.