Octoparse Proxies

Rotating Proxies for Octoparse

Point your Octoparse tasks at one Proxy Rotator gateway and get a fresh IP on every request from a 100M+ pool of residential, datacenter, mobile and IPv6 proxies. No proxy list to rotate by hand. Whitelist your IP, add one gateway address, and scrape without blocks.

Plans from $24.95/mo   IP-whitelist auth   New IP per request

Rotating & sticky Residential, datacenter, mobile, IPv6 HTTPS & SOCKS5 City & country targeting IP whitelist, no-code friendly
Why Proxy Rotator

Why Proxy Rotator for Octoparse

Octoparse is a no-code scraper, so the proxy work belongs at the gateway, not in a script you maintain.

New IP per request

The gateway hands every Octoparse request a different exit IP. No proxy lists to paste, no dead-IP cleanup, no rotation rules to configure.

IP-whitelist, no-code friendly

Whitelist your machine's IP once and Octoparse only needs a single gateway address. No username or password to manage in a visual workflow.

All proxy types

Residential, datacenter, mobile and IPv6 in one pool. Switch types from your dashboard without touching your Octoparse task.

Residential for tough sites

When a site filters datacenter ranges, residential IPs look like ordinary home connections and pass where others get blocked.

City & country targeting

Target by country, and by city on residential, to scrape localized listings, prices and search results from inside each market.

Built to scale

Thread-based plans handle Octoparse's concurrent and cloud runs, from a small task to a heavy scheduled crawl.

Before you start

Prerequisites

  • An active Proxy Rotator plan (from $24.95/mo).
  • Your gateway host and port: gateway.proxyrotator.com:8080.
  • The public IP of the machine running Octoparse, so you can whitelist it. See the rotating proxy API for endpoint details.
  • Octoparse installed (desktop app) or a Cloud task ready to configure.

Octoparse is a no-code tool that works best with IP-whitelist authentication, so this guide uses that as the primary method and notes username and password where supported.

Setup

Add Proxy Rotator to Octoparse

Our gateway already rotates, so you only add one proxy address. No proxy list to manage in Octoparse.

Whitelist your IP (primary method)

In your Proxy Rotator dashboard, add the public IP of the machine running Octoparse to the IP whitelist. Once authorized, the gateway accepts your traffic with no username or password, which is the cleanest fit for a no-code tool. Your gateway address is simply the host and port.

Octoparse proxy (whitelist)
gateway.proxyrotator.com:8080

Add the proxy in Octoparse

Open your task, go to the task settings and find the Proxy or Anti-blocking section. Choose to use your own custom proxy and paste the gateway address. Octoparse will route requests through it. The proxy panel will look like this.

Octoparse - Proxy settings
HTTP / HTTPS or SOCKS5
gateway.proxyrotator.com
8080
leave blank when whitelisted
leave blank when whitelisted

Octoparse custom proxy with your Proxy Rotator gateway. Leave username and password blank when your IP is whitelisted.

Username and password (where supported)

If you run Octoparse from a network with a changing IP, or you prefer not to whitelist, fill in the username and password fields with your gateway credentials instead. The gateway then authenticates by login rather than by IP.

Octoparse proxy (user:pass)
Host:     gateway.proxyrotator.com
Port:     8080
Username: USER
Password: PASS

Run the task

Start the task locally or in the Octoparse Cloud. Each request exits a fresh IP from the gateway, so the target site sees many visitors instead of one. Switch proxy types or targeting from your dashboard without editing the task.

Verify

Verify it works

Before running a full task, confirm the gateway is reachable and rotating from the command line.

cURL verify
# whitelisted IP, no credentials needed
curl -x http://gateway.proxyrotator.com:8080 https://api.ipify.org

# or with username and password
curl -x http://USER:PASS@gateway.proxyrotator.com:8080 https://api.ipify.org
# run it again, you get a different IP

A different IP on each run confirms the gateway is reachable and rotating. The first form works once your IP is whitelisted; the second works from any network.

Rotating vs sticky for Octoparse

Use rotating proxies for most Octoparse tasks: every request exits a fresh IP, which is ideal for high-volume listing and search scraping where you do not need to hold a session. Choose sticky proxies when a target requires the same IP across several steps, such as a login followed by paginated pages. You can switch between them from your dashboard without changing the task.

FAQ

Octoparse proxy FAQ

How do I authenticate Octoparse with Proxy Rotator?
The cleanest method is IP whitelisting. Add the public IP of the machine running Octoparse to the whitelist in your dashboard, then point Octoparse at the gateway address with no username or password. You can also use username and password in the proxy fields where you prefer login-based auth.
Do I need a proxy list for Octoparse?
No. Our gateway rotates IPs for you, so you add a single gateway address instead of a list. There is no proxy list to paste and no rotation rules to maintain in the task.
Which plan do I need for Octoparse?
Any Proxy Rotator plan works with Octoparse. Plans start at $24.95/mo and scale with the concurrency your local and cloud runs need. See pricing to match a plan to your thread count.
Do you support SOCKS5 with Octoparse?
Yes. The gateway supports HTTPS and SOCKS5. Choose the proxy type in the Octoparse proxy settings and use the same gateway host and port.
Can I target a specific country or city?
Yes. You can target by country, and by city on residential IPs, for localized scraping. See the rotating proxy API for targeting options.
Can I use my own proxies with Octoparse Cloud Extraction?
No. Octoparse Cloud Extraction routes tasks through Octoparse's own built-in IPs, so a custom proxy like ours applies only to local desktop runs. To use our gateway, run the task locally and set the proxy under Octoparse's IP proxy settings.
Why does Octoparse reject my username and password proxy?
Octoparse's proxy input does not reliably pass user:pass credentials, so login-based proxies can fail. Use IP-whitelist auth instead: add your machine's public IP to your dashboard whitelist, then enter gateway.proxyrotator.com:8080 with no credentials.
How do I rotate IPs in Octoparse so I do not get blocked?
Our gateway already issues a new IP per request automatically, and Octoparse also has its own rotation interval setting. Add the gateway in IP:PORT form and enable rotation; the two layers combine so each scrape exits from a fresh residential, datacenter, mobile or IPv6 IP.

Run your Octoparse tasks on rotating proxies

Create an account, whitelist your IP, and get a new IP per request from a 100M+ pool. Plans from $24.95/mo.

Copied!