Permanently Closed Marketplace Sales Thread

Status
Not open for further replies.
It works fine for me. I can't get it to not work.

Did you try creating a new Moz account?

Perhaps all your moz accounts are banned for api use. Perhaps its something 3rd party on your pc or network, like a firewall etc.. make sure you set the addon as trusted/allowed in all security software and you can try disabling your router firewall as a test. Also if you can use a mobile dongle or go to another internet connection or bypass the router you can use that as test to make sure its not the router.

I created and added another new Moz account today. It is now 4 Moz accounts simultaneously with 3 using proxies and one without using any. Today it started working again and the 403 errors are not there anymore. But there are 401 errors today. I also tried mix and match with the proxies stuff by using socks proxies too. But to not much avail. It just keeps on showing 401 error in between the task now say every 2-3rd url it shows 401 error. I checked the proxy and it does not seem connected to the proxy and happens randomly.

Are there any limits to the API use and how those are calculated. And can the APIs be banned from Scrapebox but the account still valid and working in OSE in Moz site?
 
I created and added another new Moz account today. It is now 4 Moz accounts simultaneously with 3 using proxies and one without using any. Today it started working again and the 403 errors are not there anymore. But there are 401 errors today. I also tried mix and match with the proxies stuff by using socks proxies too. But to not much avail. It just keeps on showing 401 error in between the task now say every 2-3rd url it shows 401 error. I checked the proxy and it does not seem connected to the proxy and happens randomly.

Are there any limits to the API use and how those are calculated. And can the APIs be banned from Scrapebox but the account still valid and working in OSE in Moz site?

It seems the problem was with the API on Moz's end, there's been no changes to how the addon works in quite some time and Moz have not published any changes to their API in the developer documents.

Yesterday the API was producing 403 errors, today it's fixed and working again without doing anything on our end. So it appears they were just having server problems.
 
Can you check your email? My VPS crashed and I need my scrapebox license reactivated. I sent the details to through the scrapebox support contact box.

Whenever you get a chance that would be great. Thanks a lot =)
 
I created and added another new Moz account today. It is now 4 Moz accounts simultaneously with 3 using proxies and one without using any. Today it started working again and the 403 errors are not there anymore. But there are 401 errors today. I also tried mix and match with the proxies stuff by using socks proxies too. But to not much avail. It just keeps on showing 401 error in between the task now say every 2-3rd url it shows 401 error. I checked the proxy and it does not seem connected to the proxy and happens randomly.

Are there any limits to the API use and how those are calculated. And can the APIs be banned from Scrapebox but the account still valid and working in OSE in Moz site?

There is a 10 second limit in between requests, but Scrapebox accounts for that automatically. The API is different then the site, so that won't really make a difference. Unless perhaps if they out and out just blacklist you.

However does the 401 happen exactly ever X urls. As the accounts run in order, so if you are using 4 accounts and there are exactly 3 urls between each 401 error then its that 1 particular account, which probably means its temp blocked, or another local issue with the api and that account etc... So just set that account asside, this kind of things happens to me.

Like I had my VA create hundreds of accounts, and he created a bunch of them from the same IP with the same email domain and when things didn't work he emails moz support and said he had to create hundreds of free accounts and they banned them all... :rolleyes: So when I mix and match those accounts with other accounts not created in that step those consistently give 401 and the others consistently work fine.

Yeah... he emailed moz support... like calling google and asking how to do black hat SEO... hehe I just write scripts to do things now and don't have a VA, my scripts don't give me issues like well intentioned VAs do, lol.

Page Autority Checker alot of "error 429"

How can I solve ?

error 429 would be an odd error, is that in the addon or a popup? Are you using proxies?
 
I sent you a PM, pls. check.

Hi Softtouch!
беларускія дыялектныя словынезвычайныя беларускія словы
беларускія народныя песні словы
адметныя беларускія словы
уласна беларускія словы
спрадвечна беларускія словы
прыгожыя беларускія словы
цікавыя беларускія словы
беларускія словы
рэдкія беларускія словы
українські слова
українські слова що увійшли до словникового складу інших мов світу
українські слова в інших мовах
українські слова латинського походження
українські слова з подвійним наголосом

Keyword Scraper working Ok

I need use hl=uk parameter.

p.s.: i can't sent PM, I need 15 message :(
 
There is a 10 second limit in between requests, but Scrapebox accounts for that automatically. The API is different then the site, so that won't really make a difference. Unless perhaps if they out and out just blacklist you.

However does the 401 happen exactly ever X urls. As the accounts run in order, so if you are using 4 accounts and there are exactly 3 urls between each 401 error then its that 1 particular account, which probably means its temp blocked, or another local issue with the api and that account etc... So just set that account asside, this kind of things happens to me.

Like I had my VA create hundreds of accounts, and he created a bunch of them from the same IP with the same email domain and when things didn't work he emails moz support and said he had to create hundreds of free accounts and they banned them all... :rolleyes: So when I mix and match those accounts with other accounts not created in that step those consistently give 401 and the others consistently work fine.

Yeah... he emailed moz support... like calling google and asking how to do black hat SEO... hehe I just write scripts to do things now and don't have a VA, my scripts don't give me issues like well intentioned VAs do, lol.



error 429 would be an odd error, is that in the addon or a popup? Are you using proxies?

Thanks for the clarification. I will probably try to create few new Moz accounts and check. I thought of creating another links list from just the backlinks. Seems it would not work. hehe. Moz can somehow detect bulk accounts it seems. Not sure how they do so as there would be probably hundreds of thousands of simultaneous users at one time. I have checked again and the API seems to work for a small task such as 10-20 urls. It only creates problems when it moves into hundreds and uses the multiple free accounts.

One thing that I have noticed recently in Scrapebox 2.0 is that when I check proxies in bulk such as say 90,000 port scanned proxies or public proxies in the proxy manager, the proxy manager gets stuck at times with some of the threads remaining active forever. I need to force close Scrapebox as a whole and this results in all the time spent in checking those proxies being wasted. The same also happens with proxy harvester at times and in normal harvester too. I am planning to purchase and use automator addon soon mainly for daylong proxy checking but if the tasks are not completed the automator would not be of much benefit I suppose. Is there no way to force kill active threads instead of force killing Scrapebox as a whole. The RAM and CPU usage is less than 30%. So, hardware is not an issue too I suppose for the threads getting stuck.

Any idea why that happens and is there any way so that Scrapebox force kills threads when the active threads are stuck for say 2-3 minutes.

I also have another cool idea for an addon. The domain availabilty checker is there in scrapebox keywords scraper. But if it is available as a normal scrapebox addon like the others then it would be more beneficial for finding expired domains etc. And instead of using only the .com, .net etc. predefined domains and adding those to the end of the words, there should be an option "I entered fully qualified domain names." as available in registrars such as dynadot.

https://www.dynadot.com/domain/bulk-search.html

The addon might import the domain names from the keyword. If it can do so from the harvester and remove the http, www, https parts, it would be even better. But a normal addon with import from clipboard would also be fine.

Many expired domains can be found in the harvested lists etc. itself and can be used in combination with the alive check, pr checker and pa checker. Just an idea. This can be massive tool for finding expired high quality domains quickly.
 
There is a terrible mistake done in the last version of scrapebox !!! Please fix this ASAP !!! My whole scraping setup is at halt because of this!

When loading a keyword list from a text file through the "Harvest urls" command in the automator, no matter what kind of keyword list I put in there, scrapebox converts it all into one big line with a LOT of random Chinese characters!

Please, this is not a joke, something is terribly wrong! Why is this happening with 2.0.0.34 ? I can't use the automator now and my scraping jobs are all at halt.

EDIT: Please can anyone send me the previous version 2.0.0.33 ?? The latest has terrible encoding issues I cannot do anything with it. @loopline are you there man?
 
Last edited:
There is a terrible mistake done in the last version of scrapebox !!! Please fix this ASAP !!! My whole scraping setup is at halt because of this!

When loading a keyword list from a text file through the "Harvest urls" command in the automator, no matter what kind of keyword list I put in there, scrapebox converts it all into one big line with a LOT of random Chinese characters!

Please, this is not a joke, something is terribly wrong! Why is this happening with 2.0.0.34 ? I can't use the automator now and my scraping jobs are all at halt.

EDIT: Please can anyone send me the previous version 2.0.0.33 ?? The latest has terrible encoding issues I cannot do anything with it. @loopline are you there man?

Click help >> restore previous version.

Thanks for the clarification. I will probably try to create few new Moz accounts and check. I thought of creating another links list from just the backlinks. Seems it would not work. hehe. Moz can somehow detect bulk accounts it seems. Not sure how they do so as there would be probably hundreds of thousands of simultaneous users at one time. I have checked again and the API seems to work for a small task such as 10-20 urls. It only creates problems when it moves into hundreds and uses the multiple free accounts.

One thing that I have noticed recently in Scrapebox 2.0 is that when I check proxies in bulk such as say 90,000 port scanned proxies or public proxies in the proxy manager, the proxy manager gets stuck at times with some of the threads remaining active forever. I need to force close Scrapebox as a whole and this results in all the time spent in checking those proxies being wasted. The same also happens with proxy harvester at times and in normal harvester too. I am planning to purchase and use automator addon soon mainly for daylong proxy checking but if the tasks are not completed the automator would not be of much benefit I suppose. Is there no way to force kill active threads instead of force killing Scrapebox as a whole. The RAM and CPU usage is less than 30%. So, hardware is not an issue too I suppose for the threads getting stuck.

Any idea why that happens and is there any way so that Scrapebox force kills threads when the active threads are stuck for say 2-3 minutes.

I also have another cool idea for an addon. The domain availabilty checker is there in scrapebox keywords scraper. But if it is available as a normal scrapebox addon like the others then it would be more beneficial for finding expired domains etc. And instead of using only the .com, .net etc. predefined domains and adding those to the end of the words, there should be an option "I entered fully qualified domain names." as available in registrars such as dynadot.

https://www.dynadot.com/domain/bulk-search.html

The addon might import the domain names from the keyword. If it can do so from the harvester and remove the http, www, https parts, it would be even better. But a normal addon with import from clipboard would also be fine.

Many expired domains can be found in the harvested lists etc. itself and can be used in combination with the alive check, pr checker and pa checker. Just an idea. This can be massive tool for finding expired high quality domains quickly.

When threads get stuck like that its typically 3rd party software that is interfereing. So make sure you set Scrapebox as trusted/allowed in all security software/malware checkers, firewalls etc... Also you can try closing down any unneded programs, as 3rd party software like skype, utorrent etc... can all interfere and cause threads to be locked.
 
Last edited:
Click help >> restore previous version.

Thanks! This solved it for me! Works like charm now!!

It was a fresh install and I wasn't sure if the previous version will be loaded. I thought I should have the previous version installed before in order to restore it.

Thank you loopline! I'll be waiting until this gets resolved in the next version and I will update. There were some other encoding issues with the most recent version as well. Like when importing keyword lists the ordinary way(not through automator) it seemed like it is displaying them scrambled like in scrapebox 1.
 
Last edited:
Thanks! This solved it for me! Works like charm now!!

It was a fresh install and I wasn't sure if the previous version will be loaded. I thought I should have the previous version installed before in order to restore it.

Thank you loopline! I'll be waiting until this gets resolved in the next version and I will update. There were some other encoding issues with the most recent version as well. Like when importing keyword lists the ordinary way(not through automator) it seemed like it is displaying them scrambled like in scrapebox 1.

Then you should check your source files. Nothing is scrambled for me. Or provide a source file to support.
 
Then you should check your source files. Nothing is scrambled for me. Or provide a source file to support.

softtouch2009, let me explain, I think I didn't explain myself very well, I was in a hurry, sorry.

I was using 2.0.0.33 on my other dedicated a few weeks ago without this encoding issue in the automator that I reported earlier. I moved to a new server today and installed scrapebox 2.0.0.34. The encoding issue was there. I thought it might be me, but I tried replacing every kind of value. I even tried feeding one txt file with one english keyword in it to the automator harvester. It resulted into converting it in random Chinese characters again. So I'm pretty sure it's a bug and it's a nasty one. Loopline confirmed this. He said he replicated what I explained and same thing happened to him.

So I rolled back to 2.0.0.33 now on this new server and it's working flawless. No converting to Chinese characters. All systems working very well.

I already emailed support the second I found this bug. But I don't think I should send any samples as it's clearly a bug inside the software. If there is any other way I could help to resolve this, please tell me.

EDIT: Oh man, I'm very sleepy sorry. You were talking about this second encoding issue I mentioned. Yes I will definitely send the source files. I think it happened with Romanian keywords, but I will check better with others as well and send my source files to support.
 
Last edited:
I am having some issues with vanity name checker. It starts running, checks several urls, some are complete, available or 404 but majority dont show any status update. . When I try to stop it, it freezes and I have to use task manager to shut it down. also it would be great to have a counter so we know how many did it check. Earlier versions had this option. Thanks
 
softtouch2009, let me explain, I think I didn't explain myself very well, I was in a hurry, sorry.

I was using 2.0.0.33 on my other dedicated a few weeks ago without this encoding issue in the automator that I reported earlier. I moved to a new server today and installed scrapebox 2.0.0.34. The encoding issue was there. I thought it might be me, but I tried replacing every kind of value. I even tried feeding one txt file with one english keyword in it to the automator harvester. It resulted into converting it in random Chinese characters again. So I'm pretty sure it's a bug and it's a nasty one. Loopline confirmed this. He said he replicated what I explained and same thing happened to him.

So I rolled back to 2.0.0.33 now on this new server and it's working flawless. No converting to Chinese characters. All systems working very well.

I already emailed support the second I found this bug. But I don't think I should send any samples as it's clearly a bug inside the software. If there is any other way I could help to resolve this, please tell me.

EDIT: Oh man, I'm very sleepy sorry. You were talking about this second encoding issue I mentioned. Yes I will definitely send the source files. I think it happened with Romanian keywords, but I will check better with others as well and send my source files to support.

There will be an update coming out later, which might fix also your issues.
 
ScrapeBox v2.0.0.35 Beta Released

  • Added: "Export Urls with Errors" and "Export Urls not done" to Grab/Check->Check for unregistered domains
  • Fix: In Automator interface
  • Fix: Encoding issues when mixing footprints with keywords
  • Fix: Google Image Grabber
  • Fix: Google Competition Finder
 
ScrapeBox v2.0.0.35 Beta Released

  • Added: "Export Urls with Errors" and "Export Urls not done" to Grab/Check->Check for unregistered domains
  • Fix: In Automator interface
  • Fix: Encoding issues when mixing footprints with keywords
  • Fix: Google Image Grabber
  • Fix: Google Competition Finder

WOW! Now that was a quick resolution! This version seems to be working really well now!

Scrapebox team has come to the rescue once again! Thanks guys, appreciate how you handled this!

Scrapebox v2 is becoming my favorite tool! Even many pros aren't aware how good this last version actually is for building lists, especially with that automator plugin, pure gold!!!
 
Hi there,

Slight issue with how Scrapebox v2 checks PR compared to V1

in V1 when doing PR check for say

http://www.mynewsite.wordpress.com

PR comes back as PR 9 or the PR of the main hosting domain

in V2, now PR comes back as NA

because it is checking PR of the subdomain.

It would be useful to be able to choose the check to be on either the subdomain or domain level.

For link builders, I think we would prefer to get the PR of the main domain; there is no denying that mysite.wordpress.com are valuable links, and when referring to those properties they are referred to as PR 9 based properties, not PR NA (well there's no more PR updates anyway).

Would be great to have the options of selecting domain or subdomain for the PR check.

thanks for your consideration.
 
Status
Not open for further replies.
Back
Top