Clash proxy setup
How to add an HTTP or SOCKS5 proxy in Clash Verge and other mihomo-based clients, and check the exit.
Adding Proxy302 Nodes to Clash: Rotating Residential, Static ISP or Datacenter — Which to Pick and How to Configure
All three Proxy302 lines can be written as Clash nodes. This page is about picking a line for the job and pairing its protocol with its port: rotating residential is prepaid per GB and can rotate the exit; static ISP and datacenter are billed per IP per term with a fixed exit. The five universal fields and the proxy-groups and rules syntax are covered in the Clash proxy setup guide — this page does not repeat them, only the differences.
What this page covers
Clash Verge Rev runs on the open-source Mihomo (Clash Meta) core; nodes live in the proxies list of your config file, and the skeleton fields are the same for all three lines — type, server, port, username, password — with the gateway always proxy.proxy302.com and authentication always username + password. How to fill in each of the five fields, plus the minimal proxy-groups and rules setup, are already covered in full in the Clash proxy setup guide on this site; this page does not repeat them.
This page answers a different question: which of the three lines to take, how protocol and port pair up for each line inside Clash, and how the exit behavior differs. Rotating residential is prepaid per GB, from US$1.50/GB, with a 1 GB minimum and no expiry on purchased traffic; static ISP and datacenter are billed per IP per lease term.
The three lines compared: node syntax, billing, exit behavior
| Item | Node syntax (type and port) | Billing | Exit IP behavior |
|---|---|---|---|
| Rotating residential | type: socks5 with port 3333, or type: http with port 2222 (pick the protocol when generating the proxy) | Prepaid per GB: from US$1.50/GB, 1 GB minimum, purchased traffic never expires | By default every request goes through a new real residential IP; a sticky session can hold the same IP across a sequence of requests |
| Static ISP (static residential IP) | As chosen at generation: SOCKS5 goes with 3333, HTTP with 2222; one IP carries only one protocol | Per IP per term: 1/3/7/30/60/90 days, from US$0.50 for 1 day | The IP stays fixed for the whole lease and never rotates |
| Datacenter | type: socks5 with port 3333, or type: http with port 2222 | Per IP per term: from US$0.25 for 1 day | A fixed server IP, unchanged for the whole term |
All three lines share one gateway and one authentication method; HTTPS websites open normally over both HTTP and SOCKS5.
Generate the proxy for your line and get the username and password
Step 1
Generate the proxy for your line: for rotating residential pick the country and protocol; for static ISP pick the country, the term (1 to 90 days) and the protocol (HTTP or SOCKS5, one of the two); for datacenter pick the country, the term and the protocol.
Step 2
Open My assets (the console section holding every proxy you have bought), find this proxy and copy its USERNAME and PASSWORD — copy the whole string, with no spaces or line breaks at either end.
Step 3
When you need a reference, the Connect tools page shows ready-made examples filled in with your own connection details.
Rotating or fixed: pick the line by use case
The biggest difference between the three lines is exit behavior, and that decides which one you take. Rotating residential sends every request through a different real home IP by default — the right choice for scraping-style jobs that need many different exits; when consecutive actions must come from one IP, a sticky session holds the same residential IP across a sequence of requests. Static ISP IPs are registered to consumer broadband providers rather than hosting-server ranges and stay fixed for the whole lease — the right choice for account environments that need one long-term exit; the product page recommends one account per IP. Datacenter is a fixed server IP with low latency and high concurrency, right for APIs, test environments, monitoring and bulk jobs on sites that do not block server IPs.
When you pick a fixed line, remember the pairing rule: the protocol of a static ISP is one of two, chosen at generation — if HTTP was chosen, connect on 2222 only; SOCKS5 connects on 3333. Rotating residential and datacenter support both protocols, with the port following the type.
Where DNS resolves, and how to verify the exit
After enabling the node, visit ipinfo.io and confirm that the exit IP and country have become the location you chose at purchase; what each field means is explained in the proxy location check guide.
Resolution behavior is decided by Mihomo's DNS module: the official resolution flow states that a connection matching a proxy rule sends the domain to the proxy side to handle, and only connections matching direct rules resolve locally; with dns.enable off, the system DNS is used. If you suspect wrong resolution, compare the exit IP before and after enabling the node to judge.
Which traffic goes through the node
Once the node is added, the routing mode decides how traffic leaves. The Clash Verge Rev documentation splits it into three: rule mode matches traffic against the rules in your config file one by one; global mode sends all traffic through the one node you pick by hand; direct mode sends everything over the local network. Rules match from top to bottom — a rule at the top of the list takes priority over those below, and the MATCH rule at the end of the official example catches whatever is left.
As for which apps' traffic Clash captures, that depends on the inbound method: the system proxy writes the listening port into the place the operating system keeps for it by convention, and apps read it on their own — not every program follows this non-binding convention, and it cannot proxy UDP traffic. Tun mode instead creates a virtual network adapter and takes over all TCP/UDP traffic without relying on app cooperation; the official tutorial uses it to capture programs that ignore the system proxy, such as games and command-line tools.
Line-specific errors and what to check
| Item | Check first | Fix |
|---|---|---|
| A static ISP will not connect although everything is filled in right | The protocol chosen when the proxy was generated | If HTTP was chosen, connect on 2222; SOCKS5 must be chosen at generation — one IP never serves both protocols at once |
| The exit is right but resolution behavior looks suspicious | Mihomo's DNS module | See the DNS section above: connections matching proxy rules get their domain resolved on the proxy side; only direct ones resolve locally |
| The local network cannot reach the gateway directly | Whether your network can reach proxy.proxy302.com | Follow the current instructions on the helper tool page; this page does not restate connection methods |
Generic troubleshooting — auth failures, YAML syntax, rule order — lives in the FAQ section of the Clash proxy setup guide.
Clash or the official browser extension?
Proxy302 ships its own official browser extension: push a proxy from My assets with one click and skip the fields entirely; Clash writes nodes into a config and routes traffic by rules. The split between the two is in the table below; installing and using the extension is covered in the browser extension guide.
Clash vs the official browser extension
| Item | Clash / Clash Verge | Official browser extension |
|---|---|---|
| Scope | Traffic that enters Clash goes through the node by your rules; system proxy or Tun mode can cover apps beyond the browser | Proxies only the one browser it is installed in; the rest of the computer's network is untouched |
| Configuration | Fill five fields by hand, or write the nodes into a local config | My assets → More actions → Use plugin, then click Connect inside the plugin — no fields to fill (plugin v1.5 or newer) |
| Protocol | Both HTTP 2222 and SOCKS5 3333 can be configured | HTTP proxy only (the dynamic connection address, port 2222); Chrome cannot authenticate a SOCKS5 proxy with a username and password — for SOCKS5 use a fingerprint browser or a mobile app |
| Best for | Splitting traffic per site or app, and sending more apps through the same residential exit | Only the browser needs the proxy, with as little typing as possible |
In one line: to change only the browser's exit with minimum effort, use the official extension; for rule-based routing and more apps on the same residential exit, use Clash.
Prices and getting started
Connecting costs nothing extra — what you pay for is the proxies: rotating residential is prepaid per GB, from US$1.50/GB on the Budget line (US$1.35/GB at 100 GB), 1 GB minimum, purchased traffic never expires, no subscription; static ISP is billed per IP per term, from US$0.50 for one day; datacenter likewise per IP per term, from US$0.25 for one day.
Frequently asked questions (FAQ)
Can a static residential IP be added to Clash (static residential IP Clash)?
Yes. When generating the static ISP proxy choose SOCKS5, then write proxy.proxy302.com:3333 and that credential pair as a node following the Clash proxy setup guide. The protocol is one of two, chosen at generation — one IP never serves HTTP and SOCKS5 at the same time; the IP stays fixed for the whole lease, right for account environments that need one long-term exit.
Does the datacenter line support SOCKS5?
Yes. Datacenter fixed server IPs work over HTTP or SOCKS5, and HTTPS websites open normally through either; SOCKS5 goes on port 3333, HTTP on 2222.
Does rotating residential change IP on every request? What if I need the same exit?
By default, yes: every request goes through a different real residential IP. To hold one IP across a sequence of requests, use a sticky session. When the exit must stay unchanged for a whole period (say a long-term account environment), a fixed IP from static ISP or datacenter fits better.
Per GB or per IP — what differs once it is in Clash?
Nothing differs in the Clash config itself — the node syntax is the same. The difference is money and exits: per-GB rotating residential can rotate the exit and purchased traffic never expires; per-IP static ISP and datacenter are billed by lease term, and the IP stays fixed for the whole term.
Clash or the official browser extension?
To change only the browser's exit with minimum effort, use the official extension: My assets → More actions → Use plugin, no fields to fill — but it supports the HTTP proxy only (port 2222). For rule-based routing, coverage beyond the browser, or SOCKS5, use Clash.
How does Telegram traffic go through the proxy in Clash (Telegram proxy settings Clash)?
This page covers only the configuration of Clash nodes and the lines themselves. Once the node is configured, client traffic that reads the system proxy or matches your routing rules goes through it as you set it in Clash; how to access any particular service is outside this page's scope — follow that service's official documentation and the rules applicable in your region.
Read next
Proxy302 Chrome extension
Install the Proxy302 browser extension in Chrome, Edge or 360 Browser, send a proxy from My assets with one click and check your exit IP. HTTP proxies only.
Proxy address, port, username and password
Every working proxy is described by five basic fields: protocol, host address, port, login, and password.
Check a proxy's IP, country and ISP
Check the exit IP, country and ISP your proxy really gives you in 30 seconds — and why IP databases disagree on the city. With our own test of three lookup services.
Reference links
13
- Proxy302 guide: Clash proxy setup (Chinese edition)
Product observation · Confirmed on:
Checked live on 28 October 2026: the route returned HTTP 200, and the brand repo's published document guides--clash-proxy-setup zh.json (revisedOn 2026-10-25) was read in full — that page covers the universal five-field syntax, the minimal proxy-groups and rules setup, and generic troubleshooting such as auth failures and rule order. This page is positioned against it: only line choice and differences, with everything generic linked out to avoid duplicate intent. The English route /guides/clash-proxy-setup/ was additionally checked live on 28 October 2026 (HTTP 200).
- Mihomo official documentation: common proxies fields
Third-party source · Confirmed on:
Read in full on 28 October 2026: proxies is an array; name (required, proxy names must not repeat), type (required), server (required, domain/IP), port (required); udp is an optional field defaulting to false.
- Mihomo official documentation: routing rules
Third-party source · Confirmed on:
Read in full on 28 October 2026: 'rules match in order from top to bottom; a rule at the top of the list takes priority over rules below it'; the official example ends with MATCH as the catch-all.
- Mihomo official documentation: DNS module
Third-party source · Confirmed on:
Read in full on 28 October 2026: with dns.enable false, the system DNS is used for resolution; enhanced-mode offers fake-ip / redir-host.
- Mihomo official documentation: DNS resolution flow
Third-party source · Confirmed on:
Read the resolution flow diagram on 28 October 2026: when a domain matches a proxy, 'the domain is sent to the proxy'; only connections matching direct resolve locally via nameserver.
- Clash Verge Rev official documentation: terminology
Third-party source · Confirmed on:
Read in full on 28 October 2026: the system proxy writes the listening port into the place the operating system keeps by convention and apps read it voluntarily — not all programs comply, and it cannot proxy UDP; Tun mode creates a virtual network adapter that takes over all TCP/UDP traffic, independent of developer cooperation, with no extra per-app configuration; routing modes are rule / global / direct; Clash Verge Rev uses the Mihomo (Clash Meta) core.
- Clash Verge Rev official documentation: quick start
Third-party source · Confirmed on:
Read in full on 28 October 2026: the system proxy toggle edits the operating system's proxy settings automatically and covers most browser needs; Tun mode installs a virtual network adapter and takes over programs that do not support the 'system proxy' (games and command-line tools, for example).
- Proxy302 guide: proxy address, port and login
Product observation · Confirmed on:
From the self-facts.json fact pack, fetched with curl (browser UA) and verified on 28 October 2026 (page HTTP 200, server-rendered): rotating residential gateway proxy.proxy302.com, HTTP 2222, SOCKS5 3333; username + password authentication; HOST, PORT, USERNAME and PASSWORD are shown in My assets; the Connect tools page shows a ready example with your own connection details; from mainland China, start the helper tool first. The Chinese routes /zh/guides/proxy-address-port-login/ and /zh/guides/helper-tool/ were additionally curl-checked on 28 October 2026, both HTTP 200.
- Proxy302 price page
Product observation · Confirmed on:
From the self-facts.json fact pack, fetched with curl (browser UA) and verified on 28 October 2026: rotating residential Budget line US$1.50/GB (any amount), US$1.35/GB at 100 GB, minimum purchase 1 GB; purchased GB never expire; no subscription; static ISP per IP per term (1/3/7/30/60/90 days), from US$0.50 for 1 day; datacenter per IP per term, from US$0.25 for 1 day. The English route /pricing/ was additionally curl-checked live on 28 October 2026 (HTTP 200).
- Proxy302 rotating residential product page
Product observation · Confirmed on:
From the self-facts.json fact pack, fetched with curl (browser UA) and verified on 28 October 2026: rotating residential supports HTTP and SOCKS5; by default every request goes through a different real household IP, and a sticky session can hold one residential IP across a sequence of requests. The Chinese route /zh/proxies/rotating-residential/ was additionally curl-checked on 28 October 2026 (HTTP 200).
- Proxy302 static ISP product page
Product observation · Confirmed on:
From the self-facts.json fact pack, fetched with curl (browser UA) and verified on 28 October 2026: the HTTP or SOCKS5 protocol is chosen at purchase; each IP works with the protocol you picked (HTTP on port 2222, SOCKS5 on port 3333); the IP is fixed for the whole lease and does not rotate; IPs are registered to consumer broadband providers; one account per IP is recommended. The Chinese route /zh/proxies/static-residential/ was additionally curl-checked on 28 October 2026 (HTTP 200).
- Proxy302 datacenter product page
Product observation · Confirmed on:
From the self-facts.json fact pack, fetched with curl (browser UA) and verified on 28 October 2026: datacenter supports HTTP or SOCKS5; HTTPS websites open normally through either; fixed server IPs never change during the term — low latency and high concurrency, for APIs, test environments, monitoring and bulk jobs on sites that do not block server IPs. The Chinese route /zh/proxies/datacenter/ was additionally curl-checked on 28 October 2026 (HTTP 200).
- Proxy302 guide: browser extension (Chinese edition)
Product observation · Confirmed on:
Fetched live with curl (browser UA) on 28 October 2026, HTTP 200: the extension supports the HTTP proxy only (dynamic connection address, port 2222); Chrome cannot authenticate a SOCKS5 proxy with a username and password — for SOCKS5 use a fingerprint browser or a mobile app; My assets → More actions → Use plugin (plugin v1.5 or newer) → Connect inside the plugin; the extension proxies only the browser it is installed in and does not change the rest of the computer's network. The English route /guides/browser-extension/ was additionally checked live on 28 October 2026 (HTTP 200).
Ready to try it?
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.