Set up residential proxies in ScrapeBox: the format the Proxy Manager reads, rotating vs sticky lines for harvesting, thread counts, timeouts and data use.
ScrapeBox was built in the days of lists of datacenter IPs, each with its own address. Residential proxies work differently: you connect to one gateway, and it hands out a different home IP behind it. ScrapeBox handles that fine once the list and the connection settings are right.
Step 1: Generate your proxy lines
Sign in to the Proxare dashboard, open the product you bought and switch to Generate. For this tool, use:
- Country: the country your accounts or targets belong to. Add a city only if you really need it, because a narrow target has fewer IPs.
- IP rotation: Rotating for harvesting and keyword scraping: every connection gets a new IP. Use Sticky, 10 minutes if you want each ScrapeBox thread to keep its IP for a short while (see below).
- Protocol: HTTP(S).
- Server region: Global (nearest) unless your tool runs far from the target country. This picks the gateway you connect to, not the exit country.
- Format:
host:port:user:pass, the format the ScrapeBox Proxy Manager reads. - How many: for rotating, one line is enough. For sticky, about as many lines as you run connections.
Each line carries your login plus the targeting and session options. On a Proxare Premium plan with a sticky US session it looks like this (yours has your own login, and the host and port depend on the product):
premium.proxare.com:6011:px_alice:k7Qm2x-country-us_session-ab12cd34_lifetime-30m
The part after your password (-country-us_session-…) is how the gateway knows which country and which session you want. Always copy the whole generated line; if you type your plain dashboard password into a tool, you get a random country and a new IP on every connection.
Step 2: Load the proxies
- In the main window, find the proxy panel and click Manage to open the Proxy Manager.
- Copy your lines from the dashboard, then use Load proxies and choose to load from the clipboard (or save them as a
.txtfile first and load that). - Check that each line shows the host, port, username and password in the right columns. A rotating line looks like this:
premium.proxare.com:6011:px_alice:k7Qm2x-country-us - Save the list, and tick Use proxies in the main window so the harvester actually uses them.
One line or many?
With a datacenter list, more lines meant more IPs. With a rotating residential gateway, a single line already gives you a new IP on every connection, so a list of 100 identical rotating lines adds nothing. What matters is how ScrapeBox spreads its work:
- Rotating, one line: simplest. Each new connection gets a fresh IP. Good for harvesting search results and checking URLs.
- Sticky 10 minutes, many lines: generate 50 to 200 sticky lines. Each has its own session ID, so ScrapeBox sees a real list of different proxies, and each thread keeps its IP for a few minutes. Useful for sites that dislike an IP change between a search page and the next page.
Step 3: Test, but carefully
The Proxy Manager's test runs a request through every line. That is useful once to confirm the login works, but with residential proxies every test costs data, and a test against a search engine burns IPs on CAPTCHAs. Test a few lines, not thousands, and do not let a single timeout remove your only gateway line: on residential IPs an occasional slow answer is normal.
Step 4: Tune connections and timeouts
- Timeout: raise it to 30 to 60 seconds. Residential IPs are home connections and slower than datacenter servers (see why a proxy is slow).
- Connections: start around 20 to 50 for search engines and raise it only while the error rate stays low. More threads mostly means more CAPTCHAs, not more results.
- Delays: for search engines, a short delay between queries keeps the CAPTCHA rate down far better than more IPs do.
How much data ScrapeBox uses
ScrapeBox downloads raw HTML, no images, which keeps traffic low. A search results page is typically 100 to 300 KB, so 100,000 queries at 250 KB each come to about 25 GB, plus retries. Measure 100 queries first and multiply. See how many GB you need.
Troubleshooting
- 407 or "proxy authentication failed": the password field is missing the options part, a character was lost when copying, or the line has a space at the end. Paste the generated line again.
- Connection refused or timeout: wrong port, or the protocol in the tool does not match the line (a SOCKS5 line set as HTTP or the other way round). Generate the line again with the protocol the tool uses.
- Wrong country: geolocation databases disagree, especially at city level. Check the exit IP on ipinfo.io before you trust a checker built into a tool.
- "No IP available" / 502: the city or carrier is too narrow. Widen to country level.
- Works in curl, fails in the tool: it is almost always the format or protocol. See the guide on proxy formats.
- Every proxy fails the test: the list was loaded in the wrong column order, or a spreadsheet changed the line. Load it again from the clipboard straight from the dashboard.
- Lots of CAPTCHAs: the proxies work; the search engine is rate-limiting. Lower connections, add a delay, and avoid advanced operators in every query.
Still stuck? Run the line through curl first (see how to test a proxy with curl): if curl works, the problem is the tool's settings, and support can tell you which. Message us on Telegram with the error text, never with your password.
Setup guides for other tools
Menu names can change between ScrapeBox versions; if a label differs, look for the proxy section of the same screen. Proxare is not affiliated with ScrapeBox. All product names are trademarks of their owners.