Thank you. Now, I can't even post on SB using fast or slow poster. Again, I'm using Private Proxies with username and password. It's always 0 success.
However, I do get some minor success when using trackbacks. I'm not sure why this is the case.
What are the settings that I should check? I've set the settings to settings for slow internet connections (even if I'm using the VPS) and the same thing is still happening.
I just ran a list and got 2 successful posts out of 5339 links. I got these errors:
FAILED, timeout
FAILED, 403
When checking the private proxies, I got these errors:
Error (IP Blocked)
Error Timeout
I'm using these proxies in NHSEO and they're working fine. I appreciate any info that you can give me.
Well firstly talking about your posting errors:
Failed, timeout means it timed out. So you have a timeout set in your timeout settings, under the settings menu. Say its 40 seconds for instance. When scrapebox tries to post, it will try to load the page and post, if it can't do it in 40 seconds then it aborts the connection.
Generally this is either going to be caused by a bad proxy or running too many connections with too low of timeouts on your internet connection. As you only have so much speed and the DNS is so fast, so when its capped you get timeout errors. On a VPS this "should" be pretty decent at least if not great in the way of internet connection and DNS, but it still could happen. What speed is the connection and are you using the hosts DNS and what are you connections and timeouts set at?
Tieing this in with the fact that you get timeouts when using the proxy checker means that your proxies aren't responding in the given timeout. So this could be that you are exceeding your proxy providers simultaneous connections limit. What is your providers simltaneous connections limit? If you don't know you should hghghg vxc out as you can't optimize your setup without this info. I have seen providers here offering private proxies with as low as 10 connections per account, which would lead your other connections to either give 403 or timeout errors.
Which leads to the 403 errors. Its either that the proxy is denying your request or that the end page is denying your request as forbidden. So this can happen with sites, they can deny your request, but this should be, on average, less then 1% of your errors. So if you are seeing this a lot then its the private proxies denying your request.
The ip blocked you are getting when proxy checking is from google, the IP is banned. The timeout means that google or the scrapebox ip test server failed to respond in the timeout - which is basically impossible, I mean its excessively unrealistic and in 2 years of using scrapebox almost daily I have never seen it happen. OR your proxies are timing out. Again this could be due to bad proxies or too many connections. You have to take into account your nhseo connections as part of total connections if its running when your running sbox.
Try doing this. go to settings >> connections - and set to 5 connecitons
settings >> timeouts - and set to 90 seconds
options >> use new proxy harvester - and check this off.
Then try testing proxies and check off the ignore google box and test your proxies. What are the results? It will only do an IP test. So if you see timeouts or 403 thats is 100% your proxies giving those.
Then try and test post, what do you get as results?
I know you say your proxies are working fine in nhseo, but since you can't manually do a proxy test in nhseo do you really know they are working fine? I mean nhseo is going to try a proxy and if it fails its going to move onto another proxy. so if 10% of your proxies are working then they will run in nhseo and it will seem good, cause its only using the working ones.
Where as with scrapebox you can do a specific proxy proxy test and see results. I have no reason or proof ever to believe that the proxy checker is not accruate as it works off of paid test servers and google which is just a good if not better. However if you wanted an 3rd party opinon you could test them in something like charon.
.
