Proxy setup in ScrapeBox

Proxies in ScrapeBox: host:port:username:password lines, Proxy Manager and Load from ClipBoard, the Google passed test, Use Proxies and connections.

Updated · Prokso editorial team

Connection details
Host
gw.prokso.com
Port
823 HTTP · 824 SOCKS5 — new IP per request · 10000–20000 sticky session, HTTP(S) and SOCKS5
Username and password
in your dashboard, on the plan page

Your dashboard generates ready-made lines in the format you need: choose the country, IP type and protocol.

Key takeaways
  • Host gw.prokso.com, ports 823 (HTTP), 824 (SOCKS5), 10000–20000 (sticky sessions, HTTP or SOCKS5)
  • The username and password are in your dashboard on the plan page
  • After setup, check your IP on the My IP page

A step-by-step guide to connecting Prokso proxies in ScrapeBox. It takes a few minutes.

Step 1. Get the proxy details from your dashboard

Open your plan and copy the host gw.prokso.com, port, username and password. Port 823 is HTTP and 824 is SOCKS5 (both give a new IP for every request); ports 10000–20000 keep one IP (sticky session) for up to 120 minutes and work as both HTTP and SOCKS5 (each port is a separate address). Set the country in the username: username__cr.ua.

Step 2. Generate proxy lines

In the dashboard generator choose the HTTP protocol and the host:port:username:password format. Port 823 suits search harvesting: every request goes out from a new IP. For tasks that need one address for a series of requests, generate several sticky ports from 10000-20000, one line per port.

Step 3. Load the proxies into Proxy Manager

Copy the lines and open Proxy Manager with the proxy management button below the proxy list in the main window. Click Load from ClipBoard or load the lines from a text file. ScrapeBox accepts a hostname such as gw.prokso.com, not only a numeric IP.

Step 4. Test the proxies

Run the test in Proxy Manager. Working lines get marked, failing ones don't. If you harvest Google results, look at the Google passed mark. For any other website there's Custom Test: enter a page URL and text that should appear on it. Keep in mind that on port 823 the test result applies to one random address, not the whole pool.

Step 5. Turn the proxies on

In the main window tick Use Proxies: the harvester and add-ons now go through the loaded lines. Under Connections and Timeouts set the number of connections, the timeout and retries. Start with a small number of threads and raise it only while there are no errors.

Step 6. If the proxies don't work

Check the line format: host, port, username and password separated by colons, with no spaces. An authentication error means a wrong username or password, or the plan has run out of traffic: check the balance on the plan page in your dashboard. If the proxies pass the test but Google answers with a captcha, lower the number of connections and add pauses: the pace is the problem, not the lines. For the IP whitelist, add the external address of the computer running ScrapeBox to the plan and load the lines without a username and password.

Step 7. Run a test harvest

Harvest results for 10-20 queries and look at the output. If links are collected without errors, scale up gradually. The traffic used is shown on the plan page in your dashboard.

FAQ

Does ScrapeBox support SOCKS5?

Yes, SOCKS5 is supported, and Proxy Manager detects the proxy type during the test. HTTP is the simplest option though: port 823 or sticky ports 10000-20000.

Which systems does ScrapeBox run on?

Windows. According to the ScrapeBox FAQ, on macOS it works up to version 13 Ventura and not on newer releases.

Why do proxies pass the test while Google shows a captcha?

The test sends one or two requests, while harvesting sends thousands. Google limits the pace, so lower the number of connections, add pauses and don't run dozens of threads on one address.