hi all,
I got a consistent problem with scrapebox, I dunno whether it's the setting problems, but I always run through scrapebox fast poster and after 5 mins, the fast poster just stop posting and all become failed comments.
Initially, success rate was quite high, about 50% and after 5 mins become 0%. Something is very wrong. I will usually abort the operation and check server connection, Ping test was green, access test and authentication test was red, no connection at all.
I figured out it must be the connection to scrapebox server that was lost, because prior to this, all was green when I started scrapebox.
The problem can only be solved when I restart scrapebox, but this way, I cannot finished my full auto approve list commenting.
How to ensure the connection for access and authentication remain green all the time? I am sure if this is solved, I can continue my fast poster without any problems. Please help.
p/s: I am running through private proxies, so it could'nt be proxy problem.
Please help.
This sounds like a connections problem. There hasn't been any problems with the scrapebox servers, short of a few hours a couple days this month. The issue is all of your ports are open and waiting and can't do anything, which is also why you cant reach the scrapebox servers for a test either.
If windows isn't closing down your ports, then you can wind up opening all ports and all being open and waiting, which effectively means you can't open any ports to connect to the internet. This is especially true if your running Windows XP or Vista prior to service pack 2. You can only open max 3900 ports, if your running fast poster on 200 connections between multiple instances and you average connection is 5 seconds you can open 3900 ports in a couple mins. It will be 4 minutes for for TIME WAIT will auto close them down. So you will basically feel like you have no internet connection. In your instance if its taking like 5 minutes, thats just how long its taking windows to fall behind closing ports and then your out of business. Until you close it all down, which just buys time and TCP winds up closing things down in the mean time and then it all works.
This isn't a problem with scrapebox at all, this is a problem with your windows.
It could also be your half-open connections. If it?s a half-open connections problem, Windows Event Viewer will show an event saying "TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts".
Again you can work thur my guide on dealing with fast poster issues. Which Ironically was just posted a few posts above yours.
Pay particular attention to the parts about TCP.
There are many reasons why scrapebox can freeze or hang.
Before figuring out what is causing Scrapebox to freeze, you need to identify what type of freeze is happening.
Black Window - If your Scrapebox window has gone completely black, then generally it means that it froze up because of a lack of resources. You ran out of available processor power or you ran out of Ram.
You can also see a black window if you are using RDP to connect to a remote server such as a VPS or Dedicated server. This happens because your pc and the server just aren't exchanging data fast enough. Generally if you leave this alone it will fix its self, or you can log out of your RDP session and log back in. If you are constantly getting black windows using RDP, then its either your pc or the server just doesn't have enough resources, or the internet connection is too slow or too busy.
If your constantly getting black windows on your local machine then you probably need a better processor or more Ram or you need to not run so many things on the pc at once.
Sockets/Ports waiting - As you run scrapebox, windows opens up connections and closes them. The is true for almost every part of scrapebox, its how windows works. If you have too many connections going and windows doesn't correctly close down the open connections they can stay open until the TCP timer shuts them down. If this happens, windows will open all of the available ports that it can allocate. Meaning all ports are open, not being used and you can't do anything.
When this happens the ScrapeBox window can be moved around and everything appears normal, but the numbers of posting/scraping etc... don't go up, they just stay at what they are. This behavior is especially true with free proxies and more prevelant in machines running versions of windows prior to Vista Service Pack 2, including XP. Although Vista and 7 are still susceptible to this.
The fix here is to turn your connections down and your timeouts up, or if it never kicks in, then restart your pc.
White Ghost Window/Not Responding - There is a white ghost window over top of the scrapebox window and it says (Not Responding) at the top. This generally means that scrapebox is just busy and is not currently able to display the window. Most of the time if you leave it alone and give it some time, it will come back and everything will be fine.
If leaving it alone isn't fixing the problem then you can check out the following reasons that its freezing. Here are the most common ones:
- Malformed data
- Antivirus / Firewall Software
- TCP stack
- Resources
Malformed data
This includes anyfiles you load into scrapebox. If you have malformed urls, such as:
http:/ww.go/bad-data
or if you have poorly spun text.
{anchor1||anchor2|{
This could be in any of the fields.
Checking for Malformed data
Back to basics - Create a new names file, new emails file, new comments file, and new websites file. Put only one line of text in each file. Do not use any spun text. If you are able to comment to the same list that was freezing before then its likely it was somewhere in your names/emails/websites/comments files. If scrapebox still hangs then its likely that the issue is in the blog list you are trying to comment to and you need to check for bad urls.
URLs- Uncheck the "Randomize comment poster blogs list" under settings. Then post with scrapebox. When it freezes note the position where it froze. Like list status 500/4563. Then also note your connections settings, for instance if you had 50 connections going at once.
Then import your list into the blog commenter section and hit the E. Then look for line 500 or wherever the list stopped at. Then look at 50 ulrs before and after that line (or whatever your connections were set to). If you find any malformed urls fix or delete them.
Malformed urls can be anything that is not formatted right. Like: http:/ww.go/bad-data
Spin Syntax - Load your files in the commenter section. Hit test comments. Hit the spin again button 20-30 times rapidly. If scrapebox locks up you likely have bad spin syntax coding. Note that just because it doesn't lock up in this step doesn't mean that your spin syntax isn't the cause of scrapebox freezing and you should manually double check it.
AntiVirus / Firewall Software
Antivirus and Firewall software can shut down scrapeboxes access to the internet and cause all sorts of issues. The simple solution here is temporarily disable all Antivirus and Firewall software including windows firewall and see if solves your problem.
TCP Stack
Half-open connections limit can cause an issue. Generally this is only true if you are running Windows Vista SP1 or older, including XP. The default half-open connections limit was removed by Microsoft in Windows Vista SP2 and newer, including Windows 7. If it?s a half-open connections problem, Windows Event Viewer will show an event saying "TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts". If this is the case you just ran out of available connections. The quickest fix is to restart your pc. If you keep having this issue, then try running less simultaneous instances of scrapebox or turning your connections down and your timeouts up. Upgrading to Vista SP 2 or newer will ultimately fix this problem.
Resources
Lack of resources can also cause this. Not a fast enough processor, not enough RAM. Quick fixes here are to not run as many instances of scrapebox at once, not run as many other things in the background while you are running scrapebox. Turn your connections down, and your timeouts up. Don't work with as large of a list. Most of what scrapebox does is stored in memory(RAM) and the larger the list you work with the more space this is going to take. If the memory fills up, things can go bad.
You can of course always upgrade your processor/RAM.
Back to Basics
In general its important to remember the basics, especially when none of the above works.
I am interested to buy scrapebox with this concession rate but afraid seeing so complaints, it seems buggy. Is there any difference between $97 and this $57 version? Is it safe buying from this thread?
I am asking this because I have very limited money in my hand, if it misses I will be just a pauper for IM.
Scrapebox is very solid, I definitely say it is NOT buggy. 90% of the issues you read about are caused by Windows, internet connections or user error. 9% are just ignorance. Probably only about 1% of the actual problems you read about are real errors with scrapebox and those get fixed pretty fast.
1: anyone knows what does this means while doing wonder wheel scraping (with 20 private proxies): we received error code 302 and aborted scraping ?
i think this happened to me 1st time
2: i heard a few times its better to harvest with public proxies, is this right ? becouse i dont get, public proxies are used a looooot, so i would expect them to be banned more or less by google
i am asking this becouse i spoted that now i find a lot less results when harvesting then half year ago.
302 means Google blocked your IP(s) (proxies). You just need different proxies, or to wait until your proxies become unblocked.
