Whole-device routing
Shadowrocket covers Safari and native iOS apps through the device VPN profile, so your ProxyOmega residential IP applies system-wide, not just in a browser.
Shadowrocket is the most popular way to run a proxy on an iPhone or iPad, routing iOS traffic through a server you define. This guide covers adding a ProxyOmega endpoint as a Shadowrocket server, choosing SOCKS5 or HTTP, entering username and password authentication, and turning it on. Steps follow the current Shadowrocket interface on iOS.
Shadowrocket is a paid iOS app that acts as a rule-based proxy client for iPhone and iPad. It builds a local VPN profile on the device and funnels traffic through whichever server you configure, supporting SOCKS5, HTTP, HTTPS, Shadowsocks, and several other protocols. For proxy users it is the standard tool for putting a residential IP on an Apple mobile device.
The app organises everything around servers and rules. A server entry holds the type, host, port, and credentials of an exit. Rules can then route specific domains or apps through specific servers, or connect them directly. For a straightforward setup you can add one server and switch it on globally.
Because Shadowrocket routes at the device level through the iOS VPN mechanism, it covers Safari and native apps alike, not just a single browser. That makes it well suited to mobile QA, checking geo-restricted content on iOS, and managing accounts from a phone or tablet. The app also keeps a per-connection log, so you can see exactly which server each request used and whether it matched a rule or fell through to the default.
Shadowrocket gets traffic off the device and to a server; ProxyOmega determines the address that server presents. Combining them lets an iPhone or iPad appear to browse from a real residential connection in the country you choose, across Safari and apps.
Shadowrocket covers Safari and native iOS apps through the device VPN profile, so your ProxyOmega residential IP applies system-wide, not just in a browser.
Pair Shadowrocket with the Mobile plan for genuine 4G/5G carrier IPs, or with residential plans for consumer broadband addresses, matching whatever the target expects.
Shadowrocket's rule system can send only the domains you care about through the proxy while everything else stays direct, keeping the rest of the device fast.
From the ProxyOmega dashboard, note your username with any targeting parameters and your account API key, which is used as the password. Then add the server in Shadowrocket.
Shadowrocket supports both SOCKS5 and HTTP proxy types, and every ProxyOmega port serves HTTP, HTTPS, and SOCKS5 at once, so switching the Type never means changing the port. SOCKS5 is the usual pick because it carries all TCP traffic and forwards DNS through the tunnel, which suits full-device routing across apps. HTTP is fine for browser-style traffic if you prefer it. The host, port, user, and password stay identical either way.
On iOS, the Mobile plan is a natural companion when a target expects a carrier IP, but any plan works. Because Shadowrocket routes the whole device, remember that background app refresh and system services will also travel through the proxy, which counts toward usage on pay-per-GB plans. Pick by target.
| Workload | Plan | Why |
|---|---|---|
| General iOS browsing, rotating IPs | Budget Unlimited | Fresh residential IP per port; -country-xx targets a country |
| Heavier mobile sessions | Premium Unlimited | Higher-speed residential on premium.proxyomega.com:8000 |
| City, state, or ASN targeting, pay per GB | Platinum | Precise geo control on platinum.proxyomega.com:20228 |
| Apps that require a mobile network | Mobile | Real 4G/5G carrier IPs on mobile.proxyomega.com:20229 |
| A fixed IP for logins or allowlists | Static ISP | Stable US IP (Dallas) on isp.proxyomega.com, ports 30000-30099 |
iOS proxy issues in Shadowrocket usually trace back to the credentials, the username suffix, or the VPN permission. Work through the cards below, and check Shadowrocket's own connection log for the specific failure.
A 407 means authentication failed. Confirm the Password field holds your dashboard API key rather than your login password, and that the username's targeting parameters are valid, since an unsupported parameter also returns 407. If you use IP whitelisting, note that once any IP is whitelisted only those IPs can connect, so your phone's current address must be on the list.
Make sure you approved the iOS VPN configuration prompt and that the server row is selected before toggling on. If you switched networks, the mobile IP may have changed, which matters when you authenticate by whitelist. Toggle Shadowrocket off and on to rebuild the tunnel.
A few apps use certificate pinning or their own networking and may bypass or fail through any proxy. Test in Safari first to confirm the proxy itself works, then adjust Shadowrocket rules for the specific app.
Add a ProxyOmega server to Shadowrocket and route iOS traffic.
90M+ ethically-sourced IPs across 200+ countries and 30,000+ cities. Residential, mobile, ISP and IPv6 proxies for scraping and AI agents.