Scrapebox gone bust?

by Vibrant Warrior

Posted: 14 years ago 6 replies

Hi

My copy of Scrapebox suddenly went numb. I can't seem to post to any of the harvested blogs anymore. I can't even harvest a single blog from any platform anymore whatever the criteria. Does anyone have any suggestions for me?

Thanks.

#bust #scrapebox

Mike Hlatky 14 years ago

I have had the same problem lately. My normal fail to success rate was about 5:1.

The last few times that I tried it out it was about 300:1

Hopefully there is an easy solution.
- [ 1 ] Thanks
- 1 reply
{{ DiscussionBoard.errors[2746174].message }}
- doop 14 years ago
  
  If it is indeed down - I doubt it will be down for long - while i don't have a copy myself (I prefer web-based apps From what I've heard the developers are hardcore when it comes to customer service and support. You'll probably find they'll have an update for you soon...
  
  That is if you've got a legitimate copy
  
  [ 1 ] Thanks
  
  {{ DiscussionBoard.errors[2746272].message }}
Vibrant Warrior 14 years ago

Not very good news at the moment but the tech team did reply but since my comm consisted of a few inquiries, the 'bug' just got left aside. Tried emailing them again but no reply for now, but that could just be the time difference thing. Will try again tomorrow.
- Thanks
{{ DiscussionBoard.errors[2746530].message }}
Samuel Hawthorne 14 years ago

I ran a small scrape yesterday and everything was fine. Usually there is the problems with the poor quality proxies we get from scraping them. If you have some quality (non-scraped) proxies everything runs very smoothly.
- [ 1 ] Thanks
{{ DiscussionBoard.errors[2746540].message }}
Vibrant Warrior 14 years ago

Tried good quality proxies and scraped ones. Same result.
- Thanks
{{ DiscussionBoard.errors[2746873].message }}
abnation 13 years ago

Just remove and "reinstall" again. If all else fails, contact SweetFunny directly, they'll be able to help you out!
- Thanks
Signature
The Automator - PRE LAUNCH - Automation Everywhere!
{{ DiscussionBoard.errors[2766459].message }}