Can an ipv6 private proxy be used in Scrapebox?

shaggy99

Junior Member
Joined
Jan 12, 2014
Messages
110
Reaction score
25
I bought an ipv6 proxy to use it in Chrome for a new Facebook account, and I test it in Scrapebox, but it gives error 502, bad gateway. Is the proxy bad, or is not supported in Scrapebox?
 
I do not know much about this and not sure I fully understand the beginning of your question, but I can tell you that IPv6 is -not- backwards compatible. IPv6 uses 128-bit addresses (compared to the 32-bit addresses of IPv4). Ipv4 and Ipv6 working normal don’t need swift to ipv6 but Ipv6 cheap than ipv4.
 
It could be Scrapebox.

Some tools do not support IPv6 yet (or they will never will).

Also, what authentication method are you using to connect to your proxy?
 
I'm using the proxy with Swichy Omega extension in Google Chrome.
 
I do not know much about this and not sure I fully understand the beginning of your question, but I can tell you that IPv6 is -not- backwards compatible. IPv6 uses 128-bit addresses (compared to the 32-bit addresses of IPv4). Ipv4 and Ipv6 working normal don’t need swift to ipv6 but Ipv6 cheap than ipv4.

Your opinion is so helpful buddy, your and my opinion is same, Actually your opinion is authentic and perfect.
 
I bought an ipv6 proxy to use it in Chrome for a new Facebook account, and I test it in Scrapebox, but it gives error 502, bad gateway. Is the proxy bad, or is not supported in Scrapebox?
Scrapebox does not currently support IPV6 proxies. There has been no point. Most people use proxies to scrape google for example and google bans such massive ranges of IPV6 ranges - as soon as 1 IP is blocked, they don't just block it, they block the entire range. So much so that some proxy providers were going to sell them, but upon testing they decided not to even sell them because its not worth it, IVP4 is better by far at this point.
 
Scrapebox does not currently support IPV6 proxies. There has been no point. Most people use proxies to scrape google for example and google bans such massive ranges of IPV6 ranges - as soon as 1 IP is blocked, they don't just block it, they block the entire range. So much so that some proxy providers were going to sell them, but upon testing they decided not to even sell them because its not worth it, IVP4 is better by far at this point.
Agreed with him totally.

Even it seems Ipv6 far easy for them to block.
 
This enables scrpaebox to use IPV6 of your own proxy from your own ISP. So if you have a IPV6 ip from your ISP and you want to use that instead of your IPV4 ip, then this option allows it. However this option has no effect on proxies, IPV4 proxies are still the only proxy format supported.
 
This enables scrpaebox to use IPV6 of your own proxy from your own ISP. So if you have a IPV6 ip from your ISP and you want to use that instead of your IPV4 ip, then this option allows it. However this option has no effect on proxies, IPV4 proxies are still the only proxy format supported.

Tanks Loopline to this information.
It is exactly what Im looking for.

Another question:
Is there a way to do Scrapebox Proxy Manager test V6 proxies?
If not, do you have an ETA to deliver it?

Thanks Loopline, you are always helping me with Scrapebox over years :D
 
Tanks Loopline to this information.
It is exactly what Im looking for.

Another question:
Is there a way to do Scrapebox Proxy Manager test V6 proxies?
If not, do you have an ETA to deliver it?

Thanks Loopline, you are always helping me with Scrapebox over years :D
There is no immediate ETA, as its been pointless up to now.

Google would be the primary driver of using IPV6 proxies, and they block entire ranges so fast, that I have talked to several proxy providers and after testing they decided not to even sell IPV6 proxies because they get blocked faster and are worse then IPV4 proxies.

Plus the proxy manager would have to be completely rewritten, servers redone etc... So it would be a massive over haul and without there being any large benefit to a lot of users, there are a lot more other more important things.

Anyway, thats what support told me, more or less, thats my own summary anyway.
 
2 1/2 years passed since but it seems as Scrapebox does still not support IPv6 proxies, right?
No there is still no point. Multiple proxy providers have done tests and google bans entire ranges so fast and so wide that as a general rule your going to spend more money buying ipv6 proxies then you will buying ipv4 to accomplish the same end result. No one wants to spend more money so no point to introduce the feature, thats my understanding anyway.
 
In Scrapebox I noticed it says in the settings > other:
"Enable IPV6 Support"

I use rotating proxies for scraping and so never needed IPV6.
 
In Scrapebox I noticed it says in the settings > other:
"Enable IPV6 Support"

I use rotating proxies for scraping and so never needed IPV6.
Thats for if you have an ipv6 ip of your own, like your ISP gives you an IPV6 ip and you want to use that instead of the ipv4 ip. It has nothing to do with ipv6 proxies.
 
Thats for if you have an ipv6 ip of your own, like your ISP gives you an IPV6 ip and you want to use that instead of the ipv4 ip. It has nothing to do with ipv6 proxies.

Ah right - as I say, doesn't affect me anyway, was purely posting it in case it benefited someone.
 
I bought an ipv6 proxy to use it in Chrome for a new Facebook account, and I test it in Scrapebox, but it gives error 502, bad gateway. Is the proxy bad, or is not supported in Scrapebox?
I encountered the same problem when I was using proxies for marketing purposes. You can remove the issue by changing some settings in the Scrapebox.
 
Back
Top