Scrapebox "Error - Stopped" when checkin indexed urls

It is a long time ago I get this error. I have tried with proxies and without proxies.
Any ideas about what is going on?

I believe that’s from IP bans. You need to test your proxies against Google.

This video should help you out:

Try to use scrapebox on RDP.

marios_521 said:

It is a long time ago I get this error. I have tried with proxies and without proxies.
Any ideas about what is going on?

Click to expand...

Have you tried just using your residential ip, as well?
It's probably just an issue with your proxies.
It takes very high quality proxies to be successful with Google.
It's mostly a waste.

Bing is better, for a number of things, and Yahoo is the best overall.

PHPInjected said:

I believe that’s from IP bans. You need to test your proxies against Google.

This video should help you out:

Click to expand...

I am testing my proxies, based on that video. To be honest, this time all proxies are red.. But I think I had the same problem with... the greens.

hamzashaik said:

Try to use scrapebox on RDP.

Click to expand...

I am using a VPS.

getivan said:

Have you tried just using your residential ip, as well?
It's probably just an issue with your proxies.

Click to expand...

Yes. have tried withouth proxies. SB is installed on VPS together with RankerX and other tools..

marios_521 said:

Yes. have tried withouth proxies. SB is installed on VPS together with RankerX and other tools..

Click to expand...

Does it return the same error without proxies activated?
Do you have any other errors when running other addon modules or harvester sessions?

Most likely proxy bans from Google, you'll want to use rotating proxies

@loopline paging mat loopline for help .

marios_521 said:

It is a long time ago I get this error. I have tried with proxies and without proxies.
Any ideas about what is going on?

View attachment 200611

Click to expand...

First make sure you are using the latest version of scrapebox, as if its an old version that could be why.

the "error" suggests blocked ips, as others have noted above. The "stopped" suggests you clicked the stop button, which if that is the case it could have resulted in the error.

Lastly, if you go to help >> show error log >> index checker

what are the errors?

loopline said:

First make sure you are using the latest version of scrapebox, as if its an old version that could be why.

the "error" suggests blocked ips, as others have noted above. The "stopped" suggests you clicked the stop button, which if that is the case it could have resulted in the error.

Lastly, if you go to help >> show error log >> index checker

what are the errors?

Click to expand...

I tried without proxies (latest version of SB).

From the log files:

MY TEST URL
https://abcnews.go.com/Health/Coronavirus
GOOGLE
2/1/2022 11:51:11 PM: HTTP: -1 Aborted, URL: https://www.google.com/search?hl=en...go.com/Health/Coronavirus&aq=f&aqi=&oq=&cad=h

YAHOO
2/1/2022 11:52:37 PM: HTTP: -1 Aborted, URL: https://search.yahoo.com/search?p=.&vs=abcnews.go.com&ei=UTF-8&nojs=1

BING
Just shows "NO" in indexed tab and there is no error logged.

Note: If I copy paste the urls to my browser (same ip), it returns searh results. No bans or blocks there.
Note also: SB and browser are on a VPS.

thanks for dropping in the thread mat and gratz on the exec

marios_521 said:

I tried without proxies (latest version of SB).

From the log files:

MY TEST URL
https://abcnews.go.com/Health/Coronavirus
GOOGLE
2/1/2022 11:51:11 PM: HTTP: -1 Aborted, URL: https://www.google.com/search?hl=en&source=hp&q=site:https://abcnews.go.com/Health/Coronavirus&aq=f&aqi=&oq=&cad=h

YAHOO
2/1/2022 11:52:37 PM: HTTP: -1 Aborted, URL: https://search.yahoo.com/search?p=.&vs=abcnews.go.com&ei=UTF-8&nojs=1

BING
Just shows "NO" in indexed tab and there is no error logged.

Note: If I copy paste the urls to my browser (same ip), it returns searh results. No bans or blocks there.
Note also: SB and browser are on a VPS.

Click to expand...

-1 means there is an error and scrapebox knows there is an error, but windows did not tell scrapebox any specific error code. Aborted is self explanatory.

That said, all this combined, something is causing an error and forcing the threads to abort.

So first, lets cover the obvious, go to settings >> timeout >> index checker

and max out the timeout. It should not be this, because it would say timeout not aborted. None the less lets cover that basis.

Then add an exception for scrapebox in all security software, such as malware checkers, anti virus, firewall etc..

Because the most likely cause is security software killing the connections

lastly you can try closing down any non crucial software as any 3rd party software that connects to the internet can interfere.

Also try disabling any pc optimization software.

proxygo said:

thanks for dropping in the thread mat and gratz on the exec

Click to expand...

Happy to help and thanks for the recommendation for exec as well!