Residential Proxies for OpenClash

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.

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 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.

How to start with OpenClash in minutes

1. Create a free QuanticData account and open Plans → 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.