[travestree]

I've been having the issue where hugefiles.net files will successively fail down the queue because there is a wait timer between file downloads for free users, but instead of failing straight away, it asks for a captcha, which eats into captcha brotherhood credits.
I've tried setting the limit 1 download per hoster but it doesn't help once the cool down period starts.

23.03.16 06.33.37 <--> 24.03.16 00.04.13 jdlog://9262842995541/

[raztoki]

interesting NPE, in your log!

there is no wait timer, the error shown in the log indicates that they have a slot based system based on a given download (link).

>The file have reached the download limit for guest users at the moment, Try again later... <

this triggers ERROR_TEMPORARILY_UNAVAILABLE exception, which I think is 15/30min retry wait.

they only show this after a captcha event, so we can only try download and on error throw exception. If you rather not eat credits please use package customiser rules and lower the priority of hugefiles.

[Jiaz]

[travestree]

Originally Posted by raztoki

interesting NPE, in your log!

there is no wait timer, the error shown in the log indicates that they have a slot based system based on a given download (link).

>The file have reached the download limit for guest users at the moment, Try again later... <

this triggers ERROR_TEMPORARILY_UNAVAILABLE exception, which I think is 15/30min retry wait.

they only show this after a captcha event, so we can only try download and on error throw exception. If you rather not eat credits please use package customiser rules and lower the priority of hugefiles.

Ah, ok looked at the customizer rules.
The ability to lower priority is a possible option if the queue is filled with enough alternatives, but if there aren't the problem remains.

[raztoki]

@travestree
for sure, but its not anything we can fix/prepare for. One doesn't know restriction is in place until you try it!. Either lower the priority or don't add mirrors from huge files, or delete the mirrors from hugefiles.