Proxy setup in Octoparse

A step-by-step guide to connecting Prokso proxies in Octoparse. 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. Add your IP to the IP whitelist

Octoparse doesn't support proxies with a username and password, so access works by IP. In the Prokso dashboard open your plan page and, in the IP whitelist (no password) block, add the public IP of the computer that runs Octoparse.

Step 3. Open the task settings

Open the task, go to Task Settings → Anti-blocking, tick Access websites via proxies, choose Use my own proxies and click Configure.

Step 4. Paste the proxies

Octoparse only accepts HTTP proxies as host:port, one per line. For a new IP on every request one line is enough: gw.prokso.com:823. To change the IP on a timer, add several sticky ports such as gw.prokso.com:10001, gw.prokso.com:10002 and set the Switch interval.

Step 5. Run locally

Your own proxies only work when the task runs on your device. Cloud runs use Octoparse's servers and ignore your proxies.

Step 6. Check with a test task

Create a task for https://api.ipify.org, extract the page text and run the task locally with proxies on. The scraped data should show the proxy's IP, not yours.

How many proxy strings to add

One string with port 823 is enough for every request to go out from a new IP: the proxy does the rotation itself. Several strings with sticky ports are needed in a different case: when a task goes through several pages in a row and it matters to the site that they come from one address.

In that case, set the proxy switch interval in Octoparse to no less than the time it takes the task to go through one chain of pages.

If a task gets no data

• Your external IP has changed. The most common cause: access by IP has stopped letting you in. Update the address on the plan page.
• The task is running in the cloud. Your own proxies work only when the task is run locally.
• The string contains a username and password. Octoparse expects only host:port.
• The site responds with 403 or 429. This is the site's response: lower the speed and add pauses between actions.

Traffic usage

Octoparse opens pages in a built-in browser and loads them in full, with images and scripts. Turn off image loading in the task settings if you do not need the images: this is the biggest saving. The traffic calculator will help you estimate the volume in advance.