A new build for handling bandwidth limits (getting a HTTP 503 error)

Hey everyone,

The new nightly build is being released earlier today. This update includes a proper handler for BW limits, along with a suggestion from @Mystified from RD support.

Key Updates:

• BW Limits Handling: Unfortunately, there's no way to bypass the bandwidth limit imposed by Real-Debrid. However, Zurg now optimizes all file checks by using HEAD requests instead.

• Bandwidth Efficiency: Based on my testing, this method doesn't consume any bandwidth. So, if you set serve_from_rclone: true, Zurg will not use any bandwidth at all, even during repairs, and will pass everything to rclone.

Context:

A few days ago, Real-Debrid started limiting bandwidth, with many users reporting limits ranging from 1 to 2TB of traffic per day. This has been causing a repair loop: if Zurg tries to download a file from Real-Debrid and encounters an error due to the bandwidth limit being reached, it attempts to repair the file and all other files in the torrent. Since downloading is impossible, the process repeats endlessly.

I hope this update will significantly improve your experience and resolve the ongoing issues with bandwidth limits. As always, thank you for your support and feedback!