# Residential Proxies for OpenClash

> Residential proxies for OpenClash: home-ISP IPs, sticky sessions, USA and UK most requested. From $1.00/GB down to $0.80/GB, free 100 MB trial, no card.

[Home](https://quanticdata.io/)/[Residential Proxies](https://quanticdata.io/residential-proxies/)/[Use cases](https://quanticdata.io/residential-proxies/use-cases/)/*OpenClash*

# Residential Proxies for OpenClash

The Clash client for OpenWrt routers — and the Clash apps for Android and desktop — that route a whole network or device through HTTP and SOCKS5 proxy nodes. QuanticData residential proxies give every device behind your OpenClash router a real home-ISP IP in 200+ countries, rotating or sticky, with country, state and city targeting in the username — from $1.00/GB, with a free 100 MB trial.

By [Aldo Morese](https://quanticdata.io/about/), founder of QuanticData · Published Sep 14, 2026

[Buy residential bandwidth](https://app.quanticdata.io/login?next=%2Fplans%3Fnetwork%3DRESIDENTIAL) [How to set it up](/residential-proxies/for/openclash/#setup)

Home-ISP IPs in 200+ countries · Rotating or sticky · HTTP and SOCKS5

**OpenClash** Apps, tools and travel · github.com/vernesong/OpenClash

- Network: **Home-ISP IPs, 200+ countries**

- Session: **Sticky (one IP per account)**

- Markets: **USA, UK and Germany**

- Price: **$1.00/GB on 5 GB · $0.80/GB on 1,000 GB**

![Residential proxies for OpenClash: apps, tools and travel, sticky (one ip per account), $1.00/GB on the $5 starter, home-ISP IPs.](https://quanticdata.io/residential-proxies/for/openclash/hero.svg?v=20260914d)

**Home-ISP IPs** real households in 200+ countries

**Rotating or sticky** up to 120 min on Basic, 24 h on Premium

**From $0.80/GB** $1.00/GB on the $5 starter

**Country · state · city** targeting in the username, no extra cost

## What is OpenClash, and why put a proxy node in it?

OpenClash is a LuCI plugin that runs a Clash (Mihomo) core on an OpenWrt router: every device on the LAN — phones, TVs, consoles, a PC without any proxy setting of its own — leaves through whatever node the router selects, and rules decide which device or domain goes through which node. The same YAML runs in the Clash apps for Android and desktop. What people ask us is whether a QuanticData proxy can be one of those nodes: it can, because the proxy is a standard HTTP and SOCKS5 endpoint with a host, a port, a username and a password, which are exactly the four fields of an http or socks5 node in Clash. Marketers use it to keep a phone or a workstation on one carrier IP in the account's country without touching the device; QA teams route a test bench through a home IP abroad; households abroad keep a set of devices on an exit at home. This page is the setup guide, step by step, for a router and for the phone and desktop apps.

## What people use residential proxies for with OpenClash

Four workflows we see with OpenClash. None of them needs a proxy to break the platforms' rules; all of them need a network location and a reputation the platform treats as ordinary.

### One exit for a whole device without touching it

A phone, a console or a smart TV that has no proxy setting of its own gets the exit from the router: the device sees nothing, every packet leaves through the node.

### Per-device exits with rules

Give each device on the LAN its own node with SRC-IP-CIDR rules: one account per phone, each phone on its own sticky carrier session.

### App QA behind a router

Put a test bench of real devices behind an exit in the market you test, switch the node to switch market.

### A stable exit for the phone and desktop apps

Clash on Android runs as a VPN, so apps that ignore the system proxy still go through the node; Clash Verge and ClashX do the same on desktop.

## Why residential proxies for OpenClash

When the router serves a test bench, a family abroad or a workstation that just needs a stable home address in another country, a residential exit does it at a lower price per GB: home-ISP IPs in 200+ countries with state and city targeting, from $1.00/GB, with sessions of up to 120 minutes on Basic and 24 hours on Premium. Rotating is possible too — leave the session out of the username and every new connection from the LAN leaves from a different home IP — which suits collection jobs behind the router, not logins.

**What a proxy does not do.** A proxy node changes the network the traffic leaves from; it does not change what the devices behind it are, their accounts, the SIM's country or the app-store region, and it does not replace the rules you write in Clash — a domain sent DIRECT by a rule never touches the node. The platforms' terms apply to what the devices do through it. Carrier IPs for the same job are on the [mobile proxies for OpenClash](https://quanticdata.io/mobile-proxies/for/openclash/) page.

## Best residential proxies for OpenClash

A router node serves every device behind it, so the node carries one sticky session with a long lifetime; a second node with its own session ID is the way to give a second device its own exit. The exit country is the country the devices behind the router are meant to appear from — usually the account's country. With QuanticData the exits asked for most are the United States, the United Kingdom and Germany, with state and city targeting in the username at no extra cost.

Everything routed through the node counts: light for messaging and dashboards, heavy for video and app updates, so rules that send updates DIRECT save bandwidth. On the residential network that means Residential Basic for rotating exits and sessions of up to 120 minutes, Premium for sessions of up to 24 hours, from $1.00/GB with a free 100 MB trial. For OpenClash the split is by job: accounts on the mobile network, data collection on residential — this page covers residential, and the mobile page covers the other half.

## Which session to use for OpenClash: sticky or rotating

**Sticky (one IP per account).** A node is shared by every device that Clash routes to it, so it should hold one IP for as long as those devices work: a session ID and a lifetime of up to 24 hours in the node's username. Create a second node, with its own session ID, for a device that must have a different IP; leave the session out only for a collection job that wants a new IP per connection. Country, session and targeting go in the username; credentials are in your dashboard after purchase.

```
# PROXY_HOST = host:port shown in your dashboard
# rotating: a new home IP on every request
curl -x "$PROXY_HOST" -U "USER-country-us:PASS" https://ipinfo.io/json

# sticky: keep one IP for a session (session ID and lifetime are set in the generator;
# up to 120 minutes on Basic, up to 24 hours on Premium)
curl -x "$PROXY_HOST" -U "USER-country-us-sid-opencl-ttl-30m:PASS" https://ipinfo.io/json

# state and city targeting
curl -x "$PROXY_HOST" -U "USER-country-us-region-REGION-city-CITY:PASS" https://ipinfo.io/json
```

![Anatomy of a QuanticData residential proxy username with a sticky session: USER, -country-us for the exit country, -sid- for the session ID and -ttl- for the lifetime.](https://quanticdata.io/residential-proxies/for/session-sticky.svg?v=20260914d)**What a request looks like.** The whole configuration travels in the username — one session ID per OpenClash account, with the lifetime you set, keeps the same exit for the whole login; host, port and password never change. USER and PASS stand for the credentials in your dashboard.

## Best countries for OpenClash residential proxies

The exits most often asked for with OpenClash, and why. Every country page lists the networks available and the username codes.

[United States The exit most often asked for behind a router: US accounts on non-US devices. home-ISP IPs · -country-us](https://quanticdata.io/proxies/united-states/) [United Kingdom UK accounts and app QA from an English-language market. home-ISP IPs · -country-gb](https://quanticdata.io/proxies/united-kingdom/) [Germany The most requested EU exit for test benches and households abroad. home-ISP IPs · -country-de](https://quanticdata.io/proxies/germany/)

## Residential Proxies pricing for OpenClash

Residential Basic, per GB, bandwidth valid for the whole plan term. Intermediate bundles and the Premium line (from $2.20/GB, city and ISP catalog) are on the plans page. Free trial: 100 MB on Basic for 5 days, no card.

[$5 5 GB $1.00 / GB · 30 days](https://app.quanticdata.io/login?next=%2Fplans%3Fnetwork%3DRESIDENTIAL) [$800 1,000 GB $0.80 / GB · 360 days](https://app.quanticdata.io/login?next=%2Fplans%3Fnetwork%3DRESIDENTIAL)

The same pool at every tier — a small test costs exactly $1.00/GB. Full ladder and terms on the [pricing page](https://quanticdata.io/pricing/).

## How to start with OpenClash in minutes

1. Create a free QuanticData account and open [Plans → Residential](https://app.quanticdata.io/login?next=/plans?network=RESIDENTIAL); pick a bundle — $1.00/GB is enough to test OpenClash on your real workflow.

2. Copy host, port, username and password from the dashboard. Put the country in the username (`-country-us`), and state or city if the job is local (`-region-…-city-…`), and a session ID with a lifetime when the OpenClash flow must keep one IP.

3. In OpenClash open Servers and Groups, add a server of type http or socks5 with the QuanticData host, port, username (country, session ID, lifetime) and password, put it in the Proxy group, apply, and check the exit from a device behind the router; the same node as YAML imports into Clash for Android and Clash Verge.

4. Run a small sample first and watch how OpenClash responds; a residential IP is not a promise of access, acceptance or a particular success rate, and the platforms' terms and the law apply to what you do through it.

## Set it up for OpenClash

QuanticData residential proxies are standard HTTP and SOCKS5 endpoints: a host, a port, a username and a password, shown in your dashboard the moment a plan is active. The username carries the country, the state and the city, and the session; host, port and password never change. OpenClash on an OpenWrt router, then the Clash apps on Android and desktop. The node is the same in both: a standard http or socks5 node with the four values from your dashboard.

```
host      PROXY_HOST                     # from your dashboard
port      PORT                           # the HTTP port, or the SOCKS5 port for a SOCKS5 node
username  USER-country-us-sid-opencl-ttl-120m
password  PASS
```

1. **Get the four values.** Open your QuanticData dashboard, pick the plan and use the endpoint generator: it prints the host, the HTTP port and the SOCKS5 port, your username with the country (and, if you want one IP for the whole session, a session ID and a lifetime), and your password. Copy them; nothing else is needed.

2. **Add the node in OpenClash.** In LuCI go to Services → OpenClash → Servers and Groups → Servers → Add. Type: http (or socks5 for the SOCKS5 port), Name: anything, Server: the host, Port: the port of that type, Username and Password: from the dashboard. Save and put the node in a group — the Proxy select group is enough — then Apply. If you prefer the file, Config Manage → edit and paste the node under proxies:.

3. **The same node as YAML.** This is the node as Clash reads it, for the config file and for the Android and desktop apps. Replace PROXY_HOST, PORT, USER and PASS with the four values; keep the quotes around the username, it contains hyphens.

```
proxies:
  - name: "QuanticData US sticky"
    type: http            # or socks5, with the SOCKS5 port
    server: PROXY_HOST    # host from your dashboard
    port: PORT            # port of that protocol, from your dashboard
    username: "USER-country-us-sid-a1b2c3-ttl-120m"
    password: "PASS"

proxy-groups:
  - name: "Proxy"
    type: select
    proxies: ["QuanticData US sticky", "DIRECT"]

rules:
  - MATCH,Proxy
```

4. **Clash on Android and desktop.** Clash Meta for Android, Clash Verge and ClashX import the same YAML as a local profile: Profiles → New → File, paste, save, select the profile, choose the node in the Proxy group and connect. On Android the app runs as a VPN, so apps that ignore the system proxy still go through the node; on desktop enable the system proxy in the app or point the browser at the app's mixed port.

5. **Sticky or rotating.** The username decides. With -sid-<id>-ttl-<minutes> every device sent to the node keeps one IP for that many minutes (up to 1440 on mobile and Residential Premium, 120 on Residential Basic) and a new IP when it expires; without a session ID every new connection leaves from a different exit, which breaks logins and suits collection only. One account per exit means one node per session ID, and a rule such as SRC-IP-CIDR,192.168.1.20/32,Phone-A sends one device to one node.

6. **DNS through the proxy.** Keep the DNS in fake-ip enhanced mode: Clash then passes the hostname to the node and the site is resolved at the exit, in the exit's country. In redir-host mode the router resolves names locally, and a site that looks at where your DNS comes from sees your real region. Check the rules that came with any template: GEOIP or domain rules that say DIRECT bypass the node for those destinations.

7. **Test the exit.** From a device behind the router open https://ipinfo.io/json: the org should be a carrier (mobile) or a home ISP (residential) and the country the one in the username, not your WAN. From the router itself: curl -x http://127.0.0.1:7890 https://ipinfo.io/json (7890 is OpenClash's default HTTP port). Run the delay test on the node in the OpenClash overview; a number means the node answers.

8. **Typical errors.** "Proxy node timeout" on the delay test: the port belongs to the other protocol (HTTP port on a socks5 node or the reverse), the host is misspelled, or the router's WAN cannot reach the gateway. Authentication failed or HTTP 407: a typo in the username string, quotes lost when pasting, a password changed after regenerating the endpoint, or a plan with no bandwidth left. Node works but sites see your real country: DNS in redir-host mode or a DIRECT rule for that domain. Sessions drop every N minutes: the ttl expired, raise it.

## FAQ

Residential Proxies for OpenClash: does it work, which session, how to set it up, proxy clients, mobile or residential.

[Something else? Ask us →](/residential-proxies/for/openclash/#ask)

### Do residential proxies work with OpenClash?

QuanticData residential proxies work with OpenClash the way any proxy does: they change the network your traffic leaves from, to real home-ISP IPs in 200+ countries. A proxy node changes the network the traffic leaves from; it does not change what the devices behind it are, their accounts, the SIM's country or the app-store region, and it does not replace the rules you write in Clash — a domain sent DIRECT by a rule never touches the node. The platforms' terms apply to what the devices do through it.

### Which proxy session should I use for OpenClash: sticky or rotating?

QuanticData recommends a sticky session for OpenClash. A node is shared by every device that Clash routes to it, so it should hold one IP for as long as those devices work: a session ID and a lifetime of up to 24 hours in the node's username. Create a second node, with its own session ID, for a device that must have a different IP; leave the session out only for a collection job that wants a new IP per connection. Sessions are set in the username (a session ID and a lifetime, up to 120 minutes on Basic, up to 24 hours on Premium), so no proxy list is needed.

### Can I use OpenClash to set a QuanticData proxy?

QuanticData proxies go into OpenClash as an http or socks5 node: they are standard HTTP and SOCKS5 endpoints with a host, a port, a username and a password, and those are the four fields of the node. Add the node under Servers and Groups (or paste the YAML into the config), select it in the Proxy group, apply, and every device the rules send to that group leaves through the exit set in the username — country, and a session ID with a lifetime when the devices must keep one IP.

### How do I set up a residential proxy for OpenClash?

QuanticData gives you host, port, username and password the moment a plan is active: create a free account, open Plans → Residential, pick a bundle ($1.00/GB to start) and copy the credentials from the dashboard. In OpenClash open Servers and Groups, add a server of type http or socks5 with the QuanticData host, port, username (country, session ID, lifetime) and password, put it in the Proxy group, apply, and check the exit from a device behind the router; the same node as YAML imports into Clash for Android and Clash Verge. For OpenClash, the countries asked for most are the United States, the United Kingdom and Germany.

### Can I use Shadowrocket with QuanticData for OpenClash?

QuanticData residential proxies are standard HTTP and SOCKS5 endpoints with a host, a port, a username and a password, so any client that accepts a proxy node works, Shadowrocket included: enter those four values as a server of type HTTP or Socks5 in Shadowrocket on the iPhone, and OpenClash traffic from the phone leaves through the exit set in the username. For OpenClash give each account its own sticky session — a session ID and a lifetime in the username — so the phone keeps one IP for the whole login. Host and port are in your dashboard; the HTTP and the SOCKS5 port are different, so pick the one that matches the node type.

### Mobile or residential proxies for OpenClash?

QuanticData's answer for OpenClash depends on the job: accounts and logins go on the mobile network (a carrier IP, sticky for up to 24 hours, from $5 for 1 GB), data collection goes on residential (from $1.00/GB, rotating through 200+ countries). This page covers residential; the mobile page for OpenClash covers the same workflows on the other network.

## Related use cases

Same network, other platforms in apps, tools and travel — and the other network for OpenClash.

[Mobile Proxies for OpenClash Carrier IPs shared with real phones, sticky up to 24 hours, from $5 for 1 GB.](https://quanticdata.io/mobile-proxies/for/openclash/) [Residential Proxies for Discord The chat platform for communities, with servers, bots, voice and a developer platform.](https://quanticdata.io/residential-proxies/for/discord/) [Residential Proxies for Steam Valve's PC game store and platform, with regional pricing, a community market and public APIs.](https://quanticdata.io/residential-proxies/for/steam/) [Residential Proxies for Telegram The messaging platform with channels, bots, groups and the TON mini-app ecosystem.](https://quanticdata.io/residential-proxies/for/telegram/)

All platforms: [residential proxies by use case](https://quanticdata.io/residential-proxies/use-cases/) · [mobile proxies by use case](https://quanticdata.io/mobile-proxies/use-cases/)

Brand names and logos belong to their respective owners and are used to identify the platforms only. QuanticData is not affiliated with or endorsed by any of them.

## Get residential proxies for OpenClash in minutes

Free account, pick a bundle, credentials in your dashboard. Residential starts at $1.00/GB.

[Buy residential bandwidth](https://app.quanticdata.io/login?next=%2Fplans%3Fnetwork%3DRESIDENTIAL) [Create a free account](https://app.quanticdata.io/register)

## Also on this site

Quantic**Data**

Residential proxies & web data APIs for AI.

#### Proxies

- [Residential Basic](https://quanticdata.io/residential-proxies/#basic)

- [Residential Premium](https://quanticdata.io/residential-proxies/#plans)

- [Cheap Residential](https://quanticdata.io/cheap-residential-proxies/)

- [Mobile Proxies](https://quanticdata.io/mobile-proxies/)

- [Datacenter Proxies](https://quanticdata.io/datacenter-proxies/)

- [ISP Proxies](https://quanticdata.io/isp-proxies/)

- [Web Unlocker proxy](https://quanticdata.io/web-unlocker/)

- [Enterprise solutions](https://quanticdata.io/enterprise-solutions/)

- [Rotating Proxies](https://quanticdata.io/rotating-proxies/)

- [Sneaker Proxies](https://quanticdata.io/sneaker-proxies/)

- [SOCKS5 Proxies](https://quanticdata.io/socks5-proxies/)

- [IPv6 Proxies](https://quanticdata.io/ipv6-proxies/)

- [Proxy locations](https://quanticdata.io/proxies/)

#### Data APIs

- [MCP Server](https://quanticdata.io/mcp-server/)

- [Web Scraper API](https://quanticdata.io/web-scraping-api/)

- [SERP API](https://quanticdata.io/serp-api/)

- [Collectors](https://quanticdata.io/collectors/)

- [Web Data for AI](https://quanticdata.io/web-data-api-for-ai/)

- [Quantic AI](https://quanticdata.io/ai-web-scraping-service/)

- [Crawl & Map](https://quanticdata.io/crawl-map/)

- [SEO Audit](https://quanticdata.io/seo-audit/)

#### Use cases

- [Mobile proxies by platform](https://quanticdata.io/mobile-proxies/use-cases/)

- [Residential proxies by platform](https://quanticdata.io/residential-proxies/use-cases/)

- [Company data](https://quanticdata.io/scrape-company-data/)

- [Price monitoring](https://quanticdata.io/competitor-price-monitoring/)

- [Market research](https://quanticdata.io/market-research-data/)

- [Real estate data](https://quanticdata.io/real-estate-data-scraping/)

- [Scrape job postings](https://quanticdata.io/scrape-job-postings/)

#### Company

- [Documentation](https://quanticdata.io/docs/)

- [Blog](https://quanticdata.io/blog/)

- [Free tools](https://quanticdata.io/tools/)

- [Partners](https://quanticdata.io/partners/)

- [Affiliates](https://quanticdata.io/affiliates/)

- [About](https://quanticdata.io/about/)

- [Alternatives](https://quanticdata.io/alternatives/)

- [Pricing](https://quanticdata.io/pricing/)

- [FAQ](https://quanticdata.io/#faq)

- [For AI agents](https://quanticdata.io/#ai)

#### Free tools

- [All tools](https://quanticdata.io/tools/)

- [Website to Markdown](https://quanticdata.io/tools/website-to-markdown/)

- [PDF to Markdown](https://quanticdata.io/tools/pdf-to-markdown/)

- [WAF detector](https://quanticdata.io/tools/waf-detector/)

- [AI visibility audit](https://quanticdata.io/tools/ai-visibility-audit/)

- [AI crawler checker](https://quanticdata.io/tools/ai-crawler-checker/)

- [robots.txt tester](https://quanticdata.io/tools/robots-txt-tester/)

- [robots.txt generator](https://quanticdata.io/tools/robots-txt-generator/)

- [User agent](https://quanticdata.io/tools/user-agent/)

- [cURL converter](https://quanticdata.io/tools/curl-converter/)

- [Proxy tester](https://quanticdata.io/tools/proxy-tester/)

© 2026 QuanticData ·

- [quanticdata.io](https://quanticdata.io/)

·

- [Terms](https://quanticdata.io/terms/)

·

- [Privacy](https://quanticdata.io/privacy/)

If you are an AI agent:

- [llms.txt](https://quanticdata.io/llms.txt)

·

- [llms-full.txt](https://quanticdata.io/llms-full.txt)

---

Source: https://quanticdata.io/residential-proxies/for/openclash/ · Site index for AI: https://quanticdata.io/llms.txt · Full dump: https://quanticdata.io/llms-full.txt