I have quite unusual case, and literally zero clues on how it could be made in OB, so any help would be much appreciated 
each proxy should make it through all blocks only N times per minute. so if I would make a config with a single block, which would send http request (GET) to google.com and launch it with 1000 proxies, each proxie should execute this block only N (5 or more) times per 60 seconds.
I feel like a combination of these 2 would somehow work
Basically after 5 tries ban the proxy and leave it banned for 60 seconds
2 Likes
lol, I was literally typing message about this exact thing in settings, but didn’t fully realise how to approach it in this exact case, using proxy ban time seems clever, should work, so if I’ll make proxy ban time 60s, all banned proxies will unban automatically after 60s? should I set “no valid proxy behaviour” to “DoNothing” for this to work tho?
You need to set unban (and not reload) as no valid proxy behaviour, otherwise this will not work.
Thanks for pointing that out
1 Like
“no valid proxy behaviour” set to “unban” won’t unban all proxies as soon as 100% of them will go to ban? it’s gonna wait for “hidden timer” to tick 60s?
DoNothing = don’t unban and don’t reload, just sit there forever, useful only if you don’t want proxies to be used anymore after they are banned.
Unban = unban only the ones that can be unbanned (it takes into account the proxy ban time).
Reload = fetch a new batch of proxies from the sources (e.g. reads the file again or calls your remote API to get fresh proxies), hence losing all information about their previous ban time.
2 Likes
I see how it’s a bit confusing anyways. You can check the code for yourself here
1 Like
gotcha, thanks so much, OB is just in beta, but it’s already so huge, I can’t thank you (and everyone who’s participating in development) enough for all the effort! gonna donate for sure when crowdfunding will be open again
2 Likes