Closed Varming73 closed 9 months ago
it should be fixed on the next hotfix that i am testing but it shouldn't affect functionality. You should increase your API timeouts instead.
I just reverted to hotfix7, never saw that error there with api_timeout_secs: 30
# basic functionality
host: "[::]" # do not change this if you are running it inside a docker container
port: 9999 # do not change this if you are running it inside a docker container
concurrent_workers: 32
check_for_changes_every_secs: 15
# reliability configs
api_timeout_secs: 30 # API requests timeout, changed default from 60s to 4s (increase this if you're having API timeout issues)
retries_until_failed: 5 # api failures until considered failed
rate_limit_sleep_secs: 6 # wait time after getting a 429 from Real-Debrid API
download_timeout_secs: 2 # download requests timeout, default is set to 2s
# misc configs
ignore_renames: true
enable_repair: true
expose_full_path: false # this helps plex or jellyfin or infuse identify content better. Might break *Arrs if enabled.
retain_folder_name_extension: true # if true, zurg won't modify the filenames from real-debrid
retain_rd_torrent_name: false # if true, it will strictly follow RD API returned torrent name which should make this more compatible with rdt-client
auto_delete_rar_torrents: false
verify_download_link: false # if true, zurg will check if the link is truly streamable; only relevant if serve_from_rclone is set to true (as it already does this all the time if serve_from_rclone is false)
repair_every_mins: 60 # repair is now triggered on demand by broken torrents or by schedule as set here. Default is 60 mins.
This is fixed on the next release
Just upgraded, will test and report back.
Would be very nice if you could keep the version tracker updated, @yowmamasita. It's a bit hard to be efficient in the testing if we don't know what have changed.
Oops, yes will do asap
Haven't seen this error again on the new release.