No-code web scraping tool with visual workflow builder. Add KnoxProxy as an external proxy source in Octoparse for geo-targeted extraction.
Go to Settings > Proxy Settings in Octoparse.
Click "Add Proxy" and enter KnoxProxy details.
Server: gw.knoxproxy.com
Port: 7000
Username: your_username
Password: your_passwordToggle proxy on for your task.
Add country to username.
Username: your_username-country-usExecute your scraping task with the proxy enabled.
Check extracted data for correct geo-targeting.
{
"proxy": {
"server": "gw.knoxproxy.com",
"port": 7000,
"username": "your_username-country-us",
"password": "your_password"
}
}Octoparse handles request scheduling. KnoxProxy rotates IPs per connection automatically.
| Problem | Fix |
|---|---|
| Proxy connection failed | Verify host, port, credentials. |
| Task returns no data | Test proxy with a simple URL first. Update selectors if target structure changed. |
USER-country-de-city-berlin-session-profile07Order matters -- geo flags before the session flag. The session name is free text; use the profile ID so the mapping is self-documenting. Password stays as issued; no flags belong there. HTTP on :7000, SOCKS5 on :7001, same credentials.
KnoxProxy offers lower per-GB pricing, more granular geo-targeting (city/ASN level), and 2xx-only billing.
Yes. Set the proxy in task settings and it applies to both local and cloud execution.
KnoxProxy has no connection limit. Your limit is your Octoparse plan and machine resources.
Check Octoparse documentation for current SOCKS5 support. HTTP proxy (port 7000) is universally supported.
Free trial on rotating residential -- 3 minutes setup, no credit card.