Ben Sarmiento
patreon
New Nightly Implements probable BW Limit Fix
🕑 Added 2024-10-13 10:07:51 +0000 UTCRecently, a second user reported successfully bypassing Real-Debrid (RD) bandwidth restrictions using Zurg's nightly release. The first user who identified this issue was operating on version 0.9.3. With these two data points, we observed a correlation linked to the unrestrict caching mechanism.
Understanding the Issue: My analysis suggests that when a non-residential IP reaches the 400GB bandwidth limit, the restriction primarily applies to previously unrestricted download links. If a new link is unrestricted after hitting this limit, downloads from this new link continue as though the bandwidth cap has not been reached.
Implemented Fix: To address this bandwidth limitation, I've introduced a probable fix in today's nightly release (it is already live). The update works as follows:
Token Expiry Handling: Whenever a bandwidth limit is reached and a token expires, the system attempts to unrestrict a new link.
Cache Management: If successfully unrestricted, the unrestrict cache is cleared, effectively resetting the bandwidth usage.
Continuous Monitoring: If the unrestrict attempt fails, the system will retry every minute until successful.
We encourage all users to test this new nightly release and report any notable findings or improvements. Your feedback is invaluable to improve everyone's zurg experience.
Looking forward to your insights and continued support.
Comments
Stephen Temkin
Thank you for the great work!
Ben Sarmiento
This is fixed on the next release
Stephen Temkin
Logs are also unintelligible. The log page is just full of numbers and no stats as previously enjoyed. I'm using the Windows amd64 release.
Fola Dawodu
It's also added the unfortunate effect of maxing out my 50 Mbps bandwidth whilst 'Assigning Torrents' on a fresh start for whatever reason
