- Jan 25, 2009
- 6,378
- 3,774
long time no see loopline, let me try it too
use it for 3 hours to test new feature, found 2 bugs :
- in harvesting proxy, it will take forever to stop
- when harvesting url then press pause button, it got stuck
i take ss for it, if u allow me to beta test it and send every bug report, i'm gladly to help
You can use V2 as much as you like and please do send in the reports. Does it get stuck with less engines? You have to bear in mind all those engines you have selected all have their own arrays in memory. So when you hit pause it may take a while for everything to catch up, and also your system may not be able to handle it if it does not have enough free resources. Does it give an error at any point?
I have just bought the automator plugin. How does it activate and how long does it take to activate? I bought the plugin from one scrapebox instance while keeping another instance running and harvesting. Hope that does not create any problems and I suppose the automator would be activated for all the instances in the VPS. Thanks for the awesome support and explanations as always. And kindly release the next version to fix the proxy speeds not showing up bug.
Up to 12 hours to activate, then just go back to the plugins menu and double click it to install it. It will activate for all instances.
Well a similar thing happened, but I think its just due to how it all works. Bandit has become more popular and their pool of ips get blocked more quickly then they did in the beginning. So Scrapebox just uses them until they are all banned and then quits, if they are all banned or close to banned from the beginning it thinks they are done. Scrapebox doesn't know they are back connect proxies that rotate on the back end. So what I have done is to set them to replace every 10 minutes and place the bandit proxies in a file and select that file. Bandit will replace the ips every 10 mins and then Scrapebox knows if all ips come up as blocked, wait 10 mins and try again. Else you can just have it replace them when it runs out of proxies, but that seems slower with bandit proxies and since you know they get replaced every 10 mins it make sense. But I think overall bandit is being blocked more quickly then before. I don't know how often his pool of ips rotate exactly, but its just how it all works together when things get more popular.Anyone else having problems with the harvester? SB64b v2036
Windows server 2008, 64 bit vps, good specs, 4 core 11k mhz, 8gb ram
The bar jumps to 100% straight after starting with thousands of keywords - it shouldn't happen obviously.
This has happened to me since v2.032. I'm not using server side proxies. Just banditim proxies.
These worked fine on v2.032, however on current version 36 and 35 they've gone nuts.
I've run samples with both simple kws and with advanced operators. Same results. The result bar jumpt to 100% right off the bat and it only works for a short time.
Custom harvester is used on g123gl3.
Help, please:
I run SB on my WinVPS.
Went to SB for first time in few weeks today - saw need to upgrade to latest V - did this.
Now, SB won't start, just flshes for 1/2sec on screen but won't run.
Suggestions, please?
Thank you.
Each version gets a new MD5 hash, which means security software can see it as a completely different program. One of your programs is either holding Scrapebox and scanning it "forever" or just killing the process. Make sure you set Scrapebox as trusted/allowed in all anti-virus, malware checkers, firewalls etc..
I use private proxies to make sure they are country specific.
How do I set the proxies for the RankTracker plugin on V2?
Just load them in the main Scrapebox window and click the use proxies box. THEN launch the rank tracker, and it will pull those ips automatically.
For Google test results i get failed connection time out and the proxie leaks your ip
how can i fix this ?
Get new proxies. This just means your proxies are bad and/or they are not anonymous. So unless they are back connect proxies, you just need new proxies.