Surge proxy setup

Surge for iOS and macOS sends traffic to proxy policies written in its profile. Add our gateway as a SOCKS5 policy with your login and turn on UDP relay.

Protocols
SOCKS5 and HTTP with a user name and password
UDP
Over SOCKS5 with udp-relay=true; never over HTTP
Where the setting is
The [Proxy] and [Rule] sections of the profile
Works with
Residential and mobile proxies. Written from the Surge manual (Surge 5 for iOS, November 2026)

Before you start

  • Surge from the App Store on iPhone or iPad, or Surge for Mac.
  • Your proxy login and password from the Residential or Mobile page of the dashboard.
  • Traffic on the product you use: a login without traffic is refused.
Connection details
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

Surge keeps proxies as policies in the [Proxy] section of the profile. Edit the profile as text and add a line with your login:

[Proxy]
AeonProxy = socks5, gate.aeonproxy.com, 7001, username=LOGIN-cc-us-sid-ios01-time-1800, password=PASSWORD, udp-relay=true

For the HTTP port add a second line:

AeonProxyHTTP = http, gate.aeonproxy.com, 7000, username=LOGIN-cc-us-sid-ios01-time-1800, password=PASSWORD

Use the type http, not https: in Surge https means TLS to the proxy, which port 7000 does not speak. For the same reason use socks5, not socks5-tls.

Send traffic through it

The rule list must end with a FINAL rule, which sets the policy for everything the other rules do not match. Point it at the new policy:

[Rule]
FINAL,AeonProxy

This works while the outbound mode is Rule-Based. In Global mode Surge skips the rule list and sends everything to the policy picked for Global mode, so pick AeonProxy there. Direct mode sends nothing through the proxy.

UDP and calls

With udp-relay=true Surge relays UDP through the SOCKS5 server with UDP ASSOCIATE, which our port 7001 supports. Surge leaves it off unless you set it, and HTTP policies never carry UDP. What Surge does with UDP a policy cannot carry is set by udp-policy-not-supported-behaviour; Surge for Mac 6 and later rejects it by default.

Rotating or sticky

Phone apps open new connections all the time, and with a rotating login each of them gets a new IP. Apps that keep you signed in can treat that as a new device. A sticky login such as LOGIN-cc-us-sid-ios01-time-1800 keeps one exit for 30 minutes (6 hours at most), then moves to a new IP in the same country. Changing the key (ios02) gives a new IP at once. A second policy with another key or country lets you switch between two exits.

Check the proxy

Open IP checker in Safari. The IP and the country should be the exit’s, and the WebRTC test, which runs over UDP, should show the exit too rather than your own address.

If it does not work

What you seeWhat to check
Nothing loads after the changeThe type and port pair: socks5 with 7001, http with 7000. https or socks5-tls hang on our ports.
It fails right after connectingThe login, the password, a key that is not in the lists, or no traffic left on the product.
/ip-checker shows your own IPA rule above FINAL sends the site direct, or the outbound mode is Direct.
Calls or games leave from your own IPudp-relay=true is missing, or the policy is the HTTP one.
One site never opens, the rest workSome targets are blocked by default for every account: mail ports 25, 465, 587 and 2525, .gov / .mil sites and some banking and ticketing sites (limits, Acceptable Use Policy).

Questions

Yes: socks5, host, port, user, password works as well as username= and password=. The named form is easier to read and keeps the values in place when you edit the line.

Surge for Mac reads the same [Proxy] and [Rule] lines, so the policy above works there too.

Proxy questions? Ask support in the live chat.