English
РусскийHow to set a proxy in Octoparse
Octoparse is a no-code scraper, and its proxy setup is no-code too: you paste a list of addresses into the task settings and pick a rotation interval. There are two things to know before you start, both from the official help center: custom proxies work for local runs only (cloud runs use Octoparse's built-in proxy pool), and the app is built around HTTP proxies in the IP:port format — which makes IP whitelisting the reliable way to authenticate.
Before you start: proxy details and ports
You'll need your proxy list from the Dashboard — open your active subscription to see the full connection details. For Octoparse, use the HTTP ports:
| Authentication | HTTP port | List line format |
|---|---|---|
| IP whitelisting no login required — recommended |
8085 |
123.45.67.89:8085 |
| Username / password officially not supported, see the note below |
8080 |
123.45.67.89:8080:login:password |
With IP whitelisting, you first add your machine's IP address to the whitelist in the Dashboard. After that, the proxy accepts requests from that machine with no credentials — exactly the plain IP:port lines Octoparse documents.
The official Octoparse help center states that proxies requiring a username and password are not supported. At the same time, several proxy providers document the four-part IP:port:login:password line format working in the same configuration box. Our recommendation: don't build your workflow on an undocumented behavior — whitelist your IP and use port 8085. If your machine's IP changes often, you can try the four-part format as a fallback.
Step 1. Enable proxies in the task settings
Open your scraping task, then:
1. Go to Task Settings and select the Anti-blocking section.
2. Check Access websites via proxies.
3. Tick Use my own proxies and click Configure.
The alternative here — Use Octoparse proxies — is the built-in pool: it's the only option for cloud runs and lets you pick a country and rotation time, but it's billed by Octoparse and the IPs are shared with other users. With your own package you control the IPs, the locations, and who else uses them (nobody).
Step 2. Paste the list and set the rotation interval
In the configuration window, paste your proxies — one per line, separated by a colon. Export the list from the Dashboard: the field order and delimiter are configurable at export, so the file comes out ready to paste:
Set the switch interval — how often Octoparse rotates to the next proxy in the list. For most scraping, somewhere around 60 seconds is a sensible starting point: short enough to spread requests across the pool, long enough not to break multi-page sessions. Click Confirm, then save the task.
Our packages start at 100 IPs, so the rotation pool itself isn't the bottleneck — and when a target starts rate-limiting, refresh the list on request, re-export the file, and paste it over the old one. Which of our proxy types fits Octoparse tasks best, with pricing and specs, is broken down on the proxies for Octoparse page.
Step 3. Verify the connection
Run the task locally (Standard Mode → local run) and watch the built-in browser load pages. For a direct check, point a quick test task at https://api.ipify.org — the page shows a single line with the IP the target site sees; it should be an address from your list, not your own. Remember that a cloud run is not a valid test: it ignores your proxies by design.
If something doesn't work
The most common causes: proxies that seem ignored usually mean the task ran in the cloud, where custom proxies don't apply — run locally; pages failing to load on port 8085 means the machine's IP isn't whitelisted in the Dashboard (re-check it after your ISP changes your address); lines with credentials failing is the expected behavior per the official docs — switch to whitelisting; and if pages load but slowly, try a longer switch interval so sessions aren't cut mid-page. If none of these is it, message us in live chat right on this page — we'll help you get connected.