Octoparse proxy setup: use your own static IPs in local runs with an IP allowlist

For an Octoparse proxy setup with your own IPs, open the task, go to Task Settings > Anti-blocking, tick Access website via proxies, choose Use my own proxies, click Configure and enter each proxy as IP:Port. Octoparse does not support proxies that need a username and password, so switch your ProxyHive order to IP allowlist authentication first. Your own proxies apply to local runs only; cloud extraction runs on Octoparse's servers.

Steps checked against the Octoparse Help Center article Set up IP proxies (updated July 30, 2026) and Octoparse's own proxy setup post on 2026-09-30.

#How Octoparse proxies work: the three constraints

Octoparse's help center sets three limits on your own proxies, and each one shapes the setup:

This is a good fit for static ISP or datacenter IPs. Each one is an IP:Port endpoint that stays the same for the term you buy, and IP allowlisting is a per-order setting in the dashboard. Rotating residential is not what this screen is built for: there is no place for credentials, and residential has no location selection today.

For most public-data tasks, datacenter proxies are the cheaper start at $3.20/IP for one IP. If a site blocks hosting ranges, move to ISP proxies, which are registered to consumer carriers.

#Before you start

1. Buy the IPs you want Octoparse to use and open the order in the dashboard at https://app.proxyhive.io.
2. Switch the order's authentication to IP allowlist and add the public IP of the computer that runs Octoparse. You can see that IP at https://api.ipify.org.
3. Copy each IP's address and HTTP port. The dashboard's HOST:PORT copy format is the shape Octoparse wants.

If your own internet connection changes IP (a home line, a laptop that moves between networks), the allowlist breaks when it does. Password or IP allowlist covers that trade-off in full.

#Octoparse proxy settings, step by step

#1. Open the task settings

Open the task in Octoparse and go to Task Settings, then select the Anti-blocking tab.

#2. Turn on proxies

Tick Access website via proxies, then choose Use my own proxies.

#3. Enter your IPs

Click Configure and enter each proxy as the IP address and port separated by a colon:

203.0.113.10:PORT
203.0.113.11:PORT

Replace the example addresses with the IPs from your order and PORT with each one's HTTP port. Click Confirm.

#4. Save and run locally

Click Save, then run the task on your device. The proxy settings do not travel with a cloud run.

#While you build the task

When you are editing a task, a site may block you before you have built anything. The Proxy button in the upper right of the editor lets you pick a proxy for the editing browser, with an option, Use the same proxies for task runs, to carry that choice into the task.

#Rotation and the switch interval

Octoparse's help center documents a Rotate time setting for its built-in proxies. For your own proxies, the current help article does not describe a rotation interval at all. If your version of the Configure dialog shows one, it cycles through the list you entered; with a handful of static IPs, that means requests take turns across those IPs rather than getting a new address each time.

Two points follow:

• Rotation does not replace pacing. Five IPs at full speed still look like five fast bots. Slow the task down in its own settings; avoiding blocks while scraping covers what else sites watch.
• Logins need one IP. If the task signs in to an account you own, a rotating list moves the session between addresses. Give that task one IP.

#Local runs vs cloud extraction

A cloud run never touches your proxy list, and it could not pass your allowlist anyway, since Octoparse's servers are not your IP. If you need your own IPs, a specific carrier or a fixed address a partner has allowlisted, run locally.

#Verify the exit IP

1. Create a test task whose URL is https://api.ipify.org?format=json.
2. Turn on your own proxies as above and run it locally.
3. Extract the page text. The IP should be one from your order, not the IP you allowlisted.

If you see your own IP, the proxy setting did not save. If the task cannot load the page, check the allowlist before anything else.

#Troubleshooting

• The page never loads, or you get a 407. The order still expects a password, or your current public IP is not on the allowlist.
• Connection refused. Wrong port, or a SOCKS5 port entered where Octoparse expects HTTP.
• Worked yesterday, fails today. Your ISP changed your public IP. Update the allowlist on the order.
• 403 or a CAPTCHA page in the results. The proxy works; the site is refusing the request. Slow down, or try an ISP IP instead of datacenter.

Before you point Octoparse at a site, check it against our allowed-use policy. If you run tasks on ParseHub too, its setup is the mirror image: it requires a username and password. See ParseHub proxy setup.