I am new to OB2 and i have a question regarding proxy loading after they are banned/invalid from remote source. I have noticed that it didn’t work for me, i am using the latest OB2 native and i also tried it on the webclient. Here are my settings:
I wonder because it is working with the same settings in the OB 1.2.2 with the same configuration and the proxies are being reloaded from the remote source after they are banned/invalid everytime but not in the OB2.
First of all change ProxyMode to ON because Default Checks ON/OFF from Config Setting So By Default Usually its OFF
Second in OB2 Opposite of OB1 You Could Generally Manage Proxy Load From Settings to Load Proxy From Manager/ File / Remote in OB2 You Should Do It For Each Job You Make
So From Here You Can Choice Proxy Loads From Where Group/File/Remote
Thanks for your help, i never tried to play with those settings, thankyou for the clarification.
Now i understood how does it work in OB2, i have already tried and yes, it works if you turn that option to yes and then paste the remote url before running a configuration as show in the above screeshot.
Hi @DACS no it’s better to put ban loop between 50-100 because tocheck means that data didn’t even check so range 50-100 flag data as tocheck after 50-100 times proxy ban increase it more than 100 like 500 is not good idea too because it effects on CPM because data is stuck there to check with a valid proxy so best range as i said its 50-100
And for ban keycheck
It depends on config like if you need ban proxy even after success status you can put it in green box
As i said depends on config you use but i recommend put RETRY in green box too
