Clash Verge Rev proxy setup
Clash Verge Rev runs the mihomo core on Windows, macOS and Linux. Our gateway goes into a profile's YAML as a `socks5` or `http` entry under `proxies:`.
- Protocols
socks5andhttpentries withusernameandpassword- UDP
- Yes with
udp: trueon the socks5 entry (off by default) and Tun Mode - Where the setting is
- Profiles → New → Local, then Edit File
- Works with
- Residential and mobile proxies
Before you start
- Clash Verge Rev 2.x from the project's GitHub releases (this guide follows 2.5) with its default mihomo core.
- Your proxy login and password from the Residential or Mobile page of the dashboard.
- For Tun Mode: Service Mode or admin rights (the app says *TUN requires Service Mode or Admin Mode*).
- Host
gate.aeonproxy.com- Port (HTTP / HTTPS)
7000- Port (SOCKS5)
7001- Login
- your proxy login, with targeting keys if you need them:
LOGIN-cc-us-sid-abc123 - Password
- your proxy password
Copy the login and password from the Residential or Mobile page of the dashboard; the generator there also writes ready lines. Key syntax: targeting and sessions.
Add the proxy
- Open Profiles and click New. Choose type Local, give it a name such as AeonProxy, and Save.
- Right-click the new profile card and choose Edit File. Replace the template with the YAML below, put in your login and password, and save.
- Click the card to make it the active profile.
- On Proxies, keep mode Rule (the rules send everything to the group) and pick
aeon-usin theAeonProxygroup. - Turn on System Proxy for browsers and most apps, or Tun Mode for every app, UDP included.
proxies:
- name: aeon-us
type: socks5
server: gate.aeonproxy.com
port: 7001
username: LOGIN-cc-us-sid-cv01-ttl-30
password: PASSWORD
udp: true
- name: aeon-us-http
type: http
server: gate.aeonproxy.com
port: 7000
username: LOGIN-cc-us-sid-cv02-ttl-30
password: PASSWORD
proxy-groups:
- name: AeonProxy
type: select
proxies:
- aeon-us
- aeon-us-http
rules:
- IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
- IP-CIDR,10.0.0.0/8,DIRECT,no-resolve
- IP-CIDR,172.16.0.0/12,DIRECT,no-resolve
- IP-CIDR,127.0.0.0/8,DIRECT,no-resolve
- MATCH,AeonProxyudp: truelets UDP through the socks5 entry. mihomo leaves it off unless you set it.- The
httpentry carries TCP only. Do not addtls: trueto either entry: both ports speak plain SOCKS5 and HTTP. - The
IP-CIDRrules keep private and local addresses direct; everything else goes to theAeonProxygroup.
To add the gateway to a profile you already use, right-click it, Edit Proxies, and append a URI such as socks5://LOGIN-cc-us:[email protected]:7001?udp=true#aeon-us. That profile's groups do not list it, so pick it in Global mode.
Check the proxy
On Proxies, run the delay check on aeon-us. A time in ms means the gateway accepted the login; a timeout points to the server, port or password. Then open /ip-checker in the browser: the IP and country should be the exit's. With Tun Mode on, the WebRTC test should show the exit too.
Rotating or sticky
mihomo opens a new connection to the gateway for each connection an app makes, so a rotating login spreads one session over many IPs. The sticky keys in the example hold one exit for 30 minutes (60 at most), then move to a new IP in the same country. For several exits, add one entry per key or country and switch between them in a select group. Avoid url-test and load-balance groups for signed-in sessions: they move connections between entries, so the IP changes.
If it does not work
| What you see | What to check |
|---|---|
| The profile does not activate | YAML indentation, or a name in proxy-groups that does not match a proxies name exactly. |
| The delay check times out | Server, port, username and password, a key that is not in the lists, tls: true set by mistake, or no traffic left. |
| The browser uses the proxy, other apps do not | System Proxy covers only apps that read it. Turn on Tun Mode. |
| UDP apps fail in Tun Mode | udp: true is missing, or the http entry is selected. |
| The IP changes between page loads | A rotating login, or a url-test / load-balance group. |
Questions
mihomo does not send UDP through a proxy entry unless the entry allows it. Our SOCKS5 port relays UDP (UDP ASSOCIATE), so set it on the socks5 entry.
Yes. Only the active profile is used. Switch to the AeonProxy profile when you need it, or add the gateway to another profile with Edit Proxies.
socks5: it carries UDP in Tun Mode. The http entry is a fallback for networks that only let web proxy traffic out.