# ParseHub Proxy: Custom Proxies and IP Rotation

> ParseHub proxy setup step by step: get custom proxies enabled, tick Rotate IP Addresses, paste one host:port:username:password per line, run and fix errors.

[Home](https://quanticdata.io/) / [Blog](https://quanticdata.io/blog/) / ParseHub Proxy: Custom Proxies and IP Rotation

# How to use a proxy in ParseHub: custom proxies, IP rotation and the errors

Proxies · Oct 24, 2026 · 10 min read · By [Aldo Morese](https://quanticdata.io/about/), founder of QuanticData

![Setting up custom proxies in a ParseHub project in four steps: generate sticky lines in the QuanticData endpoint generator, tick Rotate IP Addresses in the project Settings, paste one host:port:username:password line per proxy in Custom Proxies with HTTP on port 8080, then save and click Run; the card lists the three things to check when a run fails.](https://quanticdata.io/blog/parsehub-proxy-setup/hero.webp?v=20261023h)

On this page

- [What you need before you start](https://quanticdata.io/blog/parsehub-proxy-setup/#what-you-need-before-you-start)
- [The proxy format ParseHub accepts](https://quanticdata.io/blog/parsehub-proxy-setup/#the-proxy-format-parsehub-accepts)
- [Step by step: add custom proxies to a ParseHub project](https://quanticdata.io/blog/parsehub-proxy-setup/#step-by-step-add-custom-proxies-to-a-parsehub-project)
- [Which run uses which IP](https://quanticdata.io/blog/parsehub-proxy-setup/#which-run-uses-which-ip)
- [Residential Premium in ParseHub](https://quanticdata.io/blog/parsehub-proxy-setup/#residential-premium-in-parsehub)
- [ISP proxies in ParseHub](https://quanticdata.io/blog/parsehub-proxy-setup/#isp-proxies-in-parsehub)
- [Mobile proxies in ParseHub](https://quanticdata.io/blog/parsehub-proxy-setup/#mobile-proxies-in-parsehub)
- [Which proxy type for which ParseHub project](https://quanticdata.io/blog/parsehub-proxy-setup/#which-proxy-type-for-which-parsehub-project)
- [ParseHub proxy not working: errors and fixes](https://quanticdata.io/blog/parsehub-proxy-setup/#parsehub-proxy-not-working-errors-and-fixes)
- [When to turn IP rotation on](https://quanticdata.io/blog/parsehub-proxy-setup/#when-to-turn-ip-rotation-on)

To use your own proxies in ParseHub, have ParseHub support enable custom proxies on your paid account, open the project's Settings, tick Rotate IP Addresses and paste one proxy per line in the Custom Proxies box as host:port:username:password. Save the project and click Run: the proxies apply to runs on ParseHub's servers, not to Test Run.

ParseHub runs a project in two places. A Test Run happens on your computer, with your own IP address. A Run happens on ParseHub's servers, which by default use addresses in North America, mostly in the United States and some in Canada, according to ParseHub's help center. Custom proxies change only the second: where the server run comes from, which country a site sees and how many IPs the work is spread across. The field names below are the ones in ParseHub's own help center; the values come from the QuanticData endpoint generator.

## What you need before you start

- **A paid ParseHub plan.** ParseHub lists IP Rotation on its Standard and Professional plans, and custom proxies are part of IP Rotation. The free plan (200 pages per run, 5 public projects) has neither.
- **Custom proxies switched on for your account.** ParseHub enables the feature on request: write to ParseHub support, whose address is in its help article on custom proxies. Give them the host and port of your lines so they can confirm them on their side.
- **Proxies with a username and a password.** ParseHub asks for both. An IP whitelist does not help here: the connection to the proxy comes from ParseHub's servers, not from your computer.
- **A QuanticData plan.** Residential Premium, ISP or mobile. The lines are in the dashboard under My proxies, on the plan's page.

**Try it on your own targets.** Every QuanticData account gets $2 of free API usage per month.

[Start free — $2/month included](https://quanticdata.io/signup/?utm_source=blog&utm_medium=website&utm_campaign=blog-inline&utm_content=parsehub-proxy-setup) · [Explore Residential Proxies from $0.80/GB](https://quanticdata.io/residential-proxies/)

## The proxy format ParseHub accepts

ParseHub reads one proxy per line in the Custom Proxies box, as four values separated by colons: address, port, username, password. Its help writes the first field as an IP address. ISP proxies are IP addresses and match it exactly; for Residential Premium and mobile the gateway host goes in the same place. There is no protocol field, and ParseHub's help speaks of HTTP proxies, so use the HTTP port.

```
# Residential Premium, Romania, one sticky session
residentialpremium.quantumproxies.io:8080:USER-country-ro-sid-p01-ttl-60m:PASS

# ISP, one fixed IP as Assigned IPs lists it
185.•••.•••.129:50100:USER:PASS

# Mobile, Romania, one sticky session
mobile.quantumproxies.io:8080:USER-country-ro-type-mobile-sid-m01-ttl-60m:PASS
```

USER and PASS stand for your own credentials. The username is the whole string, with everything after the first dash: `-country-ro` picks the exit country, `-sid-p01` names the session and `-ttl-60m` keeps it for 60 minutes. Copy it whole: a username cut at the first dash still logs in, but the run then leaves from a random country.

## Step by step: add custom proxies to a ParseHub project

![The QuanticData Endpoint generator for a Residential Premium plan: Romania selected, Session set to Sticky with a 30-minute TTL, HTTP protocol, quantity 10, output format host:port:user:pass and the preview line, with the username and password blurred](https://quanticdata.io/blog/parsehub-proxy-setup/quanticdata-generator-romania-sticky.webp)

*Step 1 in the QuanticData dashboard: country, sticky session, HTTP and the host:port:user:pass format.*

1. **Generate the lines.** In the QuanticData dashboard open My proxies, then your plan. In the Endpoint generator choose the Country (Romania in this guide), set Session to Sticky, set Session TTL (minutes) to at least the length of a run, choose HTTP, keep Output format on host:port:user:pass and set Quantity to the number of lines you want. Click Generate, then Copy all.
2. **Open the project in the ParseHub desktop app** and click the gear icon beside the magnifying glass, at the top left of the commands panel. Choose Settings.
3. **Tick Rotate IP Addresses.** On an account with custom proxies enabled, the Custom Proxies box appears at the bottom of the Settings.
4. **Paste the lines** into Custom Proxies, one proxy per line, nothing after the password.
5. **Save the project** with the save icon or Save in the gear menu.
6. **Click Get Data, then Run.** Not Test Run: a Test Run stays on your computer and your IP.

![ParseHub project with the gear menu open at the top of the commands panel: numbered markers on 1 the gear icon beside the magnifying glass and 2 the Settings item; the menu also lists Get Data, Save, Undo, Redo, New Template, Export, Delete Project and Exit](https://quanticdata.io/blog/parsehub-proxy-setup/parsehub-project-settings-menu.webp)

*Step 2: the gear menu of the project. Redrawn screen.*

![ParseHub project Settings with Rotate IP Addresses ticked and three QuanticData Residential Premium sticky lines for Romania in the Custom Proxies box, residentialpremium.quantumproxies.io port 8080 with USER-country-ro-sid-p01, p02 and p03 and ttl-60m; beside it the steps and a real check of the p01 line: Suceava, Suceava, Europe/Bucharest](https://quanticdata.io/blog/parsehub-proxy-setup/parsehub-custom-proxies-residential-romania.webp)

*Steps 3 to 5, redrawn with our values. The check is real: a QuanticData Romania line on 23 October 2026.*

![ParseHub Get Data buttons Test Run, Run and Schedule, with numbered markers: 1 Run goes through the custom proxies on ParseHub servers, 2 Test Run runs on your computer with your own IP](https://quanticdata.io/blog/parsehub-proxy-setup/parsehub-get-data-run.webp)

*Step 6: Run uses the custom proxies, Test Run does not. Redrawn screen.*

## Which run uses which IP

Most "my proxy is ignored" reports come from this table. It follows ParseHub's help articles on where projects run and where its proxies are located.

| How you start it | Where it runs | IP the site sees |
| --- | --- | --- |
| Test Run | Your computer | Your own IP |
| Run, Rotate IP Addresses off | ParseHub servers | ParseHub's IPs in North America |
| Run, Rotate IP Addresses on, Custom Proxies empty | ParseHub servers | ParseHub's rotating IPs, many countries, at random |
| Run, Rotate IP Addresses on, your lines in Custom Proxies | ParseHub servers | The IPs of your lines, in the country you chose |

With IP rotation on, ParseHub also rotates the browser user agent of the run. Schedule repeats a Run, so scheduled runs use the same Settings.

## Residential Premium in ParseHub

Residential Premium gives home IPs in the country, region or city you put in the username. For ParseHub the useful pattern is a short list of sticky sessions: each line keeps one IP for its lifetime, and ParseHub rotates through the lines.

```
# three sticky sessions in Romania, one hour each
residentialpremium.quantumproxies.io:8080:USER-country-ro-sid-p01-ttl-60m:PASS
residentialpremium.quantumproxies.io:8080:USER-country-ro-sid-p02-ttl-60m:PASS
residentialpremium.quantumproxies.io:8080:USER-country-ro-sid-p03-ttl-60m:PASS
```

- **A different session ID on every line.** Two lines with the same `-sid-` are the same IP.
- **A lifetime longer than the run.** The generator accepts up to 1440 minutes, a full day. When a session ends, the next request gets a new IP.
- **The country in the username.** Prices, currency and language often follow the visitor's country, which is why ParseHub's own help suggests custom proxies for location-dependent pages.

The generator makes as many sticky lines as the Quantity field says, ten by default, each with its own session ID; Copy all and Download take them out in the same format. Without a session ID a line is rotating and changes IP at every request, the right choice only when every page can be fetched on its own; more on that on the page about [rotating proxies](https://quanticdata.io/rotating-proxies/). For a new IP on a sticky line, change the session ID, for example `-sid-p04` instead of `-sid-p01`.

![The Generate 10 sessions button in the QuanticData Endpoint generator with Copy all and Download, and the list of sticky lines ready to paste, credentials blurred](https://quanticdata.io/blog/parsehub-proxy-setup/quanticdata-generator-sessions.webp)

*Ten sticky lines, ready for the Custom Proxies box.*

## ISP proxies in ParseHub

ISP proxies are fixed IP addresses that stay the same for the life of the plan. They fit ParseHub's format exactly, because the dashboard lists them as IP:Port:Username:Password.

1. In My proxies open the ISP plan and go to Assigned IPs.
2. Keep the Protocol on HTTP / HTTPS and the Output format on IP:Port:Username:Password.
3. Select the IPs for the project and click Copy selected, or Export .txt.
4. Paste the lines in Custom Proxies with Rotate IP Addresses ticked, save, then Run.

![The Assigned IPs panel of a QuanticData ISP plan: protocol HTTP / HTTPS, output format IP:Port:Username:Password, five IPs with masked addresses on port 50100, Copy selected and Export .txt, and the formatted output ready to paste](https://quanticdata.io/blog/parsehub-proxy-setup/quanticdata-isp-assigned-ips.webp)

*Assigned IPs in the dashboard: the lines are already in the format ParseHub asks for. Sample IPs, masked.*

![ParseHub project Settings with Rotate IP Addresses ticked and three QuanticData ISP lines in the Custom Proxies box in the IP:Port:Username:Password format, IPs masked, port 50100, USER and PASS in place of the credentials](https://quanticdata.io/blog/parsehub-proxy-setup/parsehub-custom-proxies-isp.webp)

*ISP lines in the Custom Proxies box. Redrawn screen with our values.*

With three ISP lines, a run is spread over three fixed IPs. That suits sites that should see the same few addresses every day, such as an account your project logs in to. More on the product on the page for [ISP proxies](https://quanticdata.io/isp-proxies/).

## Mobile proxies in ParseHub

Mobile lines go in the same box, the same way. In the mobile plan's Endpoint generator choose the country, the gateway (Global, USA, EU or Asia), Session Sticky and Protocol HTTP · 8080; the username carries `-type-mobile`:

```
mobile.quantumproxies.io:8080:USER-country-ro-type-mobile-sid-m01-ttl-60m:PASS
mobile.quantumproxies.io:8080:USER-country-ro-type-mobile-sid-m02-ttl-60m:PASS
```

Mobile plans also offer IP whitelist authentication, but ParseHub needs the username and password lines, so use those. Mobile IPs suit sites that serve phones first or treat mobile networks more gently; see [mobile proxies](https://quanticdata.io/mobile-proxies/).

## Which proxy type for which ParseHub project

| Proxy type | Line in Custom Proxies | Good for |
| --- | --- | --- |
| Residential Premium | Host residentialpremium.quantumproxies.io, port 8080, one sticky session per line, country, region or city in the username | Most projects: home IPs in the country whose prices or language you need |
| ISP | IP:Port:Username:Password from Assigned IPs, one fixed IP per line | Logged-in projects and daily runs that should keep the same addresses |
| Mobile | Host mobile.quantumproxies.io, port 8080, -type-mobile and a sticky session in the username | Phone-first sites and pages that block other IP types |

For a country page with coverage and cities, see [Romanian residential proxies](https://quanticdata.io/proxies/romania/); the plans are on the pages for [QuanticData residential proxies](https://quanticdata.io/residential-proxies/), [ISP proxies](https://quanticdata.io/isp-proxies/) and [mobile proxies](https://quanticdata.io/mobile-proxies/).

## ParseHub proxy not working: errors and fixes

ParseHub shows what went wrong on the Run page. Add a Server Snapshot command where the project loads a page, or look at the snapshots ParseHub takes when a page fails: Select all, then See snapshots in Project shows each page as the server saw it.

![ParseHub Run page, Snapshots box listing page load failed in template main_template and product_detail, with Select all and See snapshots in Project, and notes on what each snapshot means: Proxy Server Refused Connection or Failed to Connect means the proxy did not answer, Access Denied, Blocked IP Address or a captcha means the site blocked the IP](https://quanticdata.io/blog/parsehub-proxy-setup/parsehub-snapshots-page-load-failed.webp)

*The Snapshots box of the Run page and how to read it. Redrawn screen.*

| What you see | Usual cause | Fix |
| --- | --- | --- |
| No Custom Proxies box in Settings | Rotate IP Addresses not ticked, the feature not enabled on the account, or a free plan | Tick the box; ask ParseHub support to enable custom proxies on a paid plan |
| page load failed, snapshot says Proxy Server Refused Connection or Failed to Connect | The line is wrong: SOCKS5 port, a cut username, a missing colon, a space | Copy the line again from the generator, HTTP port 8080 (ISP: the port in Assigned IPs) |
| The same error on runs that worked before | The plan expired or its traffic is used up | Check the plan in My proxies: status, remaining traffic, expiry date |
| Snapshot shows Access Denied, Blocked IP Address or a captcha | The site blocked that IP or the pace of the run | New session IDs in the lines, waits between click, hover and scroll commands, or a mobile line |
| Data in the wrong currency or language | No `-country-` in the username, or you are looking at a Test Run | Generate the lines with a country; judge the result on a Run |
| Test Run fine, Run empty | The servers see a different page from your computer | Server Snapshot on the first page; ParseHub suggests IP rotation when the site blocks its servers |

One test outside ParseHub settles whether the line itself works. If this returns an address in the right country, the proxy is fine and the problem is in the project or the account:

```bash
curl -x http://residentialpremium.quantumproxies.io:8080 \
  -U "USER-country-ro-sid-test-ttl-10m:PASS" https://ipinfo.io/json
```

On 23 October 2026 this request through a QuanticData Romania sticky line answered from Suceava, Suceava, with the time zone Europe/Bucharest. More on the command in the guide to [using a proxy with curl](https://quanticdata.io/blog/how-to-use-a-proxy-with-curl/), and a general [proxy not working checklist](https://quanticdata.io/blog/proxy-not-working-checklist/).

## When to turn IP rotation on

ParseHub's help advises against leaving Rotate IP Addresses on without a reason, because rotation can slow a run. Custom proxies need the box ticked, so the reasons to use them are concrete: the site blocks ParseHub's own servers, the content depends on the country, or the run must come from addresses you control. A proxy changes where a run comes from, not what the project may collect: keep to each site's terms and to the law where you work.

### Sources & further reading

- ParseHub help: Adding Custom Proxies to ParseHub (for all Paid Plans)
- ParseHub help: Using IP Rotation (for all Paid plans)
- ParseHub help: Where do my projects run?
- ParseHub help: Where are ParseHub's proxies located?
- ParseHub help: Server Snapshot
- ParseHub pricing

## FAQ

Quick answers on parsehub proxy.

[Something else? Ask us](mailto:hello@quanticdata.io)

### How do I add a proxy to ParseHub?

Ask ParseHub support to enable custom proxies on your paid account. Then open the project, click the gear icon beside the magnifying glass, choose Settings, tick Rotate IP Addresses and paste one proxy per line in the Custom Proxies box as host:port:username:password. Save the project, click Get Data and choose Run.

### What proxy format does ParseHub use?

One proxy per line, four values separated by colons: address, port, username, password. ISP proxies from the QuanticData dashboard are already in this format (IP:Port:Username:Password). For Residential Premium and mobile, keep the generator's output format on host:port:user:pass, use the HTTP port 8080 and copy the username whole.

### Does ParseHub support proxies with a username and password?

Yes, and it requires them: ParseHub's help asks for custom proxies that have a username and a password. IP whitelist authentication alone does not work, because the connection to the proxy comes from ParseHub's servers, not from your computer.

### Does Test Run use my custom proxies?

No. A Test Run runs on your computer with your own IP address. Custom proxies apply when you click Run (or a scheduled run starts) and the project runs on ParseHub's servers. Judge prices, currency and language on a Run.

### Why does ParseHub show "page load failed"?

The page did not load on ParseHub's server. Open the snapshot with See snapshots in Project: "Proxy Server Refused Connection" or "Failed to Connect" points to the proxy line or the plan, while "Access Denied", "Blocked IP Address" or a captcha means the site blocked the IP. Fix the line, check the plan's traffic, or use new session IDs and add waits between commands.

### Is IP rotation available on the ParseHub free plan?

No. ParseHub's free plan offers 200 pages per run and 5 public projects; IP Rotation, and with it custom proxies, is listed on the paid plans. Current limits are on ParseHub's pricing page. The proxies themselves come from your proxy provider.

## Proxies in the country your ParseHub runs need

Residential Premium, ISP and mobile proxies with username and password, country targeting and sticky sessions up to 1440 minutes, copied from the endpoint generator straight into ParseHub's Custom Proxies box.

[Start free — $2/month included](https://quanticdata.io/signup/?utm_source=blog&utm_medium=website&utm_campaign=blog-end&utm_content=parsehub-proxy-setup) · [Explore Residential Proxies from $0.80/GB](https://quanticdata.io/residential-proxies/)

## Related reading

- [Antik Browser Proxy Setup: Add, Check and Fix](https://quanticdata.io/blog/antik-browser-proxy-setup/): Proxies · In Create Profile choose New Proxy, pick Http/Https or Socks5 to match the port, paste host:port:login:password and read the check under the field. Below: every step with the exact field names, one sticky session per profile, Residential Premium, ISP and mobile lines, the Proxy list for many profiles and a fix for each error.
- [Wget Proxy: -e, Env Vars, .wgetrc and Fixes](https://quanticdata.io/blog/wget-proxy-setup/): Proxies · Pass the proxy on the command line with -e https_proxy and --proxy-user, export https_proxy for a whole shell, or write it in ~/.wgetrc for every run. Below: each method with real wget output, which one wins, Residential Premium, mobile and ISP lines, no_proxy rules, why wget has no SOCKS5 and the fix for each error it prints.
- [MBBrowser Proxy Setup: Add, Test and Fix](https://quanticdata.io/blog/mbbrowser-proxy-setup/): Proxies · Open Create New Session, choose HTTP or SOCKS5 under Proxy Server to match the port, fill in address, port, Account and Password, click Test until it says Success and create the session. Below: every field, why Test sets the time zone, Residential Premium, ISP and mobile lines, bulk import with the Proxy Server Manager and a fix for each error.

---

Source: https://quanticdata.io/blog/parsehub-proxy-setup/ · Site index for AI: https://quanticdata.io/llms.txt