Surge and Stash Proxy Chain: Static IP Behind Your Node
Config lines for Surge and Stash, and an honest note on Loon and Quantumult X.
Four iOS and Mac clients, what we could confirm
Four iOS and Mac clients, what we could confirm
Item
Chain setting
What we confirmed
Surge
underlying-proxy=NodeName on the policy line
Surge manual: the parameter, an example and its limits
Stash
dialer-proxy: NodeName on the proxy
Stash docs: the field, rules and version numbers
Loon
Not confirmed
The manual pages we could read do not mention chaining
Quantumult X
Not confirmed
The sample configuration shows http and socks5 nodes with login, and no chaining
Sources: the Surge manual (common policy parameters, HTTP proxy policy and the proxy-provider knowledge-base page), the Stash dialer proxy and proxy types pages, the Loon manual and the Quantumult X sample.conf, all read on 16 November 2026. "Not confirmed" means we did not find it documented, not that the app cannot do it.
A chain means the connection to the second proxy is opened through the first one. Here the first is your existing node (the entry) and the second is the static IP (the exit). Your device talks to your node, your node talks to the static IP, and the static IP talks to the website, so the website sees the static IP. If your node later switches server, the exit stays the same.
This suits people who already have a working connection and want a steady exit that agrees with the country of one account. It adds a hop, so expect more latency. Keep it to the countries and regions a service supports, and complete any verification it asks for.
Surge describes underlying-proxy as the name of another proxy policy or policy group, used to connect through it: Surge first establishes a connection to the underlying policy, then connects to the target proxy server through it. The value can be a policy group, so the entry can be switched by hand. The manual also says ip-version has no effect on a policy with an underlying proxy, and that to chain every member of a group you use the group-level parameter, which needs Surge Mac 6.9.0 or iOS 5.22.0 or later.
The HTTP policy line is Name = http, host, port, username, password, followed by optional parameter=value pairs; SOCKS5 follows the same pattern. After adding the policy, use it in a rule or policy group for the apps or domains that need the static IP.
[Proxy]
# YourNode is the name of the node you already use
Static-US = http, HOST, 2222, LOGIN, PASSWORD, underlying-proxy=YourNode
# SOCKS5 version of the same IP, if it was bought as SOCKS5
Static-US-S5 = socks5, HOST, 3333, LOGIN, PASSWORD, underlying-proxy=YourNode
Example only: replace HOST, LOGIN, PASSWORD and YourNode. Not run in Surge here; the syntax follows the Surge manual. Use the line that matches the protocol the IP was bought with.
Stash: dialer-proxy
Stash describes dialer-proxy as a field in a proxy definition naming another proxy: the connection to the target proxy server goes through another proxy first. It names a proxy or a strategy group, works on proxies in the main configuration or a remote proxy set, and cannot be set inside proxy-groups. A name that does not exist makes the proxy unavailable, loops are not allowed, and dialer-proxy and interface-name are mutually exclusive.
Stash lists version numbers for the feature (iOS and tvOS 3.2.5 or later, macOS 4.1 or later) and warns that UDP depends on the proxy in front: UDP over UDP can cause MTU mismatches and packet loss. HTTP and SOCKS5 proxies take server, port, username and password fields.
Example only: replace HOST, LOGIN, PASSWORD and YourNode, and use type: http with port 2222 for an IP bought as HTTP. Not run in Stash here; the fields follow the Stash dialer proxy and proxy types pages.
Loon and Quantumult X: what we did not find
Loon's manual pages that we could read describe adding nodes and policy groups for ss and ssr, and do not mention chaining, so we cannot give a chain setting. Quantumult X's sample configuration shows how to add an http or socks5 node with username and password in the server_local section, and does not show a proxy-to-proxy chain.
Neither result proves the app cannot chain; it means we found nothing official to quote. Check the app's current documentation, and if you only need the static IP for one app, adding it as a plain node and selecting it for that app's traffic is the documented part.
Open the static residential page, pick a country, a lease (1 to 90 days) and the protocol, HTTP or SOCKS5. A 1-day IP is US$0.50 and a 30-day IP is US$7.99, about US$0.27 a day. Stock by country shows on the order page.
In My assets, copy HOST, PORT, LOGIN and PASSWORD. Use port 2222 for HTTP and port 3333 for SOCKS5.
Step 3: add the IP with the entry chained
Add the Surge line or the Stash proxy shown above, with the entry set to your node.
Step 4: send only the traffic that needs it
Point the rule or policy group for the one account's app or domains at the static IP, and keep that account on that IP. One account per IP, no sharing the account, follow the platform terms.
Step 5: check the exit
Open an IP lookup page through the chain and confirm it shows the static IP and the country you bought.
If the chain does not connect
The static IP shows as unavailable
Check The entry node is down, the name in underlying-proxy or dialer-proxy does not match, or (Stash) it points to a group that includes itself.
Fix Check the exact spelling and case of the entry name, and test the entry node on its own first.
Stop when If the entry works alone and the chain still fails, stop editing and test the static IP without the chain.
Connection works without the chain, fails with it
Check Wrong protocol or port for how the IP was bought, or a wrong login.
Fix Compare with My assets: HTTP with port 2222, SOCKS5 with port 3333, same LOGIN and PASSWORD.
Stop when Do not keep retrying wrong credentials; open a ticket with the order number if they match.
Slow, or UDP apps drop
Check A second hop adds latency, and UDP depends on what the entry proxy supports.
Fix Use the chain only for the apps that need the static IP, and prefer TCP for them.
Stop when If it is still slow, compare a direct test to the static IP with a chained one before changing anything else.
Surge, Stash, Loon and Quantumult X chain: FAQ
How do I chain a proxy in Surge?
Add the second proxy as a policy and set underlying-proxy to the name of the first, for example underlying-proxy=YourNode. Surge connects to the underlying policy first, then to the target proxy through it.
How do I chain a proxy in Stash?
Add the second proxy under proxies and set dialer-proxy to the name of the first proxy or a strategy group. It cannot be set inside proxy-groups.
Does Loon support proxy chains?
The Loon manual pages we could read do not say. Check the app's current documentation.
Does Quantumult X support proxy chains?
The sample configuration we read does not show one. It does show http and socks5 nodes with username and password.
Which comes first, my node or the static IP?
Your node is the entry and the static IP is the exit, so the website sees the static IP.
Add a Proxy302 HTTP or SOCKS5 proxy to Shadowrocket on iPhone: which boxes to fill, how to switch it on, how to check your exit IP and what to do in mainland China.
Read on 16 November 2026: underlying-proxy is the name of another proxy policy or group; Surge connects to it first, then to the target proxy through it; example with an HTTPS entry and a Snell exit; ip-version has no effect with it; group-level parameter.
Read on 16 November 2026: syntax Name = http, host, port[, username, password][, parameter=value]; underlying-proxy is among the parameters every proxy policy accepts.
Read on 16 November 2026: dialer-proxy field, example, rules (no loops, not inside proxy-groups, exclusive with interface-name), UDP notes and version numbers.
Read on 16 November 2026: the pages we could open describe adding ss and ssr nodes, subscriptions and policy groups; chaining is not mentioned. The linked full manual page returned no readable text.
Read on 16 November 2026: server_local examples for http and socks5 nodes with username and password; no proxy-to-proxy chaining.
A sample file, not the full documentation.
Proxy302 product facts and price list
Product observation · Confirmed on:
Product information of the site, checked 16 November 2026: static ISP and datacenter per-IP prices in US$, lease terms, protocols and ports (HTTP 2222, SOCKS5 3333), no free trial.
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.