Proxies test good in Scrapebox but bad in SER
DavidA2
I have some shared proxies from BuyProxies. They all always test fine in Scrapebox, but 15 of them always test bad in SER. Anyone have similar experience or explanations?
Comments
Its a regular problem, try a different string in the tester
Chances are your proxies are banned on bing
@LeeG - Tried several different URL/string combinations. Why would I get these results? (out of 30 proxies)
URL String # Good
http://yahoo.com/ mail 15
http://msn.com/ hotmail 8
http://msn.com/ bing 8
http://google.com/ about 12
http://google.ca/ faster 17
What exactly is this "test" doing? Why such a variance? Why do they not test good in SER? (They all still test good in Scrapebox.)
I left my proxy settings as they were after the last test (with 17 good proxies). I have been running SER now for 4-5 hours and all 17 proxies are still alive and working. If I had stopped after I ran the test and only had 8 good proxies, I would be running with only 8 this whole time.
The proxies are obviously good (because the program continues to use them and has not flagged any of the other ones that it reported as "bad" when running the other tests). So, to me, there definitely seems to be a problem with the "test proxies" function the way it is currently done.
If I put a check beside the proxies that are marked as bad (they are not currently checked), will SER use them while it is processing? If it will, will it mark them as "good" if it is successful in using them?
As it is now, I have 13 perfectly good proxies that are sitting there doing nothing because SER thinks they are bad.
google.ca faster 12/18
17/13
google.com faster 10/20
bing.com news 21/9
bing.com videos 9/21
22/8
21/9
yahoo.com mail 12/18
alexa.com global 30/30
discover 30/30
What is the purpose of even testing them if you can't really tell if they are good or not?