For anyone having proxy (proxies) issues with dying (dead), low submission rates & sock errors
Hey folks,
After getting through a STEEP learning curve with Search Engine Ranker we're getting our settings dialed in.
In an effort to ADD value to the forum and bring value I wanted to share what we found in case it helps someone/anyone.
Quick Facts so you can relate our knowledge level
- We've owned SER for one week.
- New to proxies
- New to automated link building
Problems we were experiencing
1. Submission rates plummeted after updating to V9.08
2. All proxies burning out (dying) very fast, both public and private
3. Started with 10 dedicated proxies, had issues with them burning up
4. Added 100 semi dedicated, still had issues with them burning up
5. Had captcha problems solving text captcas (still remains unresolved with @BanditIM/@Sven)
Resolutions we came to after hours of reading, asking questions etc.
1. Timeout settings and time between searches is critical especially if you're internet connection isn't extremely fast (we have a 30mb connection, but are experieincing 12mb during the day and up to 50 mb at night).
2. Using public proxies will drop your submission AND search success rates substantially. Why? Often many proxies scraped from public sources have been banned on some search engines (the more engines you're using the more likely you'll have this problem) which keeps you from finding sources to submit to. Additionally many sites have a list of banned proxies so even if you're able to find them you won't be able to register/submit to them.
3. Using private proxies is far superior, but you must have the proper settings (there is NO rule here, it just takes testing because your connection speed, speed of the sites you're trying to post to and server speeds will all be a factor) so that you don't end up with a bunch of dead proxies and no submissions yet again.
4. Email checking was timing out, having all kinds of problems like +OK Pop reset, can't log in etc. What a mess!
About our campaigns
We're currently posting to PR0+ Web2.0's, Articles and Wikis.
Some of the actions we took that have brought our submission rates back to within what we feel is acceptable.
Global Options
1. Changed HTML timeout in the Global Options menu to 140 seconds
2. Lowered our threads to 15 (we feel we can go faster, but wanted to find a stable place from which to make changes)
3. Changed time between searches to 60 seconds
More about #2. We have read over and over that you "should" be able to run 10 threads for every 1 dedicated proxy you have. Well that just isn't a good baseline. We're going the other way to find a stable place to tweak from. If your internet connection just isn't up to the task or has high loads during peak times during the day you'll have poor success as everything will just be timing out (Such as a Sockerror Connection Timed Out) which is just wasting resources and time. Therefore using a reverse strategy we are using 1 thread for every 10 semi-dedicated proxy nad at present are having great success with not only searches, but submissions and verifications. While this might not be what some people running high bandwidth and VPS configurations are experiencing it is working for us as a baseline.
Proxy Settings
1. Changed Proxy Configuration NOT to search for public proxies
2. Changed threads for testing 30
3. Changed timeout to 60 seconds for testing
4. Ticked boxes for "Auto disable proxies when detected to be down" for both public and private (we still have a few public proxies which have been reliable for over a week so we'll keep using them, but aren't scraping for any more)
More about #3. We set the timeout to 60 seconds knowing a few of our proxies will likely fail. We don't remove them however. We just let them be and retest them every few hours. We know that if they pass a 60 second timeout during testing, they'll likely pass the 140 second HTML timeout we set above in the Global Options. When you have your testing timeout set too close to your Global HTML timeout you're likely to experience a higher failure rate while a project is running. If your testing is more strict and your HTML timeout is more lax you'll likely have far less issues. Point is it's better to set a reasonable margin in testing and get bad proxies out of production before SER tries to use them and can't. This will affect submission rates each time they fail. Not a lot, but you get the idea.
Emails settings (same for all projects)
1. Changed setting for Time to wait between two logins to 900 seconds and ticked the "Per Account" box.
2. Ticked Use Proxies box
3. Ticked Delete Message when verification link found box.
4. Ticked Delete message if older than 5 days
Results
1. We are currently experiencing over the last 12 hours nearly 0 blocked searches due to blocked/banned proxies whereas before we had a very low success rate with searches even though we had dedicated proxies in use alongside the publics.
2. Overnight our submissions jumped up to nearly double (96 two days ago, 183 overnight) what they were prior to making all these changes and our verifications have doubled across the board (16 two days ago, 32 overnight).
3. Our emails are no longer having login issues or showing errors thus resulting in higher verifications
4. LpM has increased from .04 to .20 or about 5x higher
5. Downloads per Minute has increased from 40 to 120 and Download Failures has dropped from 25 to 12)
I'm sure there is more I'm overlooking and some or all of this might be basic know-how for some people, but has been a huge headache for us and hopefully this helps someone.
tykesmurf
Comments
Other than that, great guide here tykes, this will definitely get beginners on the right track