Using a VPN on iPhone: what trips most people up isn't whether they can connect — it's where the subscription link is supposed to go. iOS keeps network configuration under system control, and apps can't build a tunnel on their own, so the process splits into four stages: get the client, import the subscription, approve the configuration, then choose a server and verify it. The walkthrough below follows those four steps, spelling out what to tap and what appears on screen.
Before You Start: What You Need
Gathering everything first beats hunting for a link halfway through the install. You need an iPhone, an active subscription, an iOS client, and a working internet connection. You don't have to assemble the subscription yourself — sign in to the user panel and you'll find the subscription link on the overview page, ready to copy with one tap.
Signing up takes only a username and password — no email address required. Payment is accepted via Alipay, WeChat, and USDT. Your first payment is covered by a 14-day, no-questions-asked full refund, so there's no need to commit to a long-term plan right away; pick a tier that matches your usage and start there.
- ✅ An iPhone where Settings → General → VPN & Device Management is available
- ✅ An active subscription, with its subscription link ready to copy from the overview page of the user panel
- ✅ An iOS client — get one from the download page, or use any client that supports importing a subscription link
- ✅ A working Wi-Fi or cellular connection; importing the subscription itself doesn't require a proxy connection first
- ❌ Don't use subscription links that arrived as screenshots, forwards, or posts in public groups — the link carries your account identifier, and anyone who gets it can burn through your data
Step 1: Get the iOS Client
Clients on iOS work differently from desktop: they can't edit the routing table directly and must request a tunnel through the system's NetworkExtension framework. That's why the first connection always triggers a system permission prompt — it isn't the client asking for extra access, it's simply how iOS works.
-
Open the download page
On your iPhone, open the download page, choose iOS from the platform list, and the page will show the matching install option.
-
Install, then sign in
Open the client and sign in with the username and password you registered — there's no email field. Once you're in, the subscription syncs to your device automatically.
-
Check the server list
Open the servers or subscription screen; if you see a list of servers grouped by region, the client has your configuration. If the list is empty, tap Update Subscription once.
Step 2: Copy and Import a Subscription
A subscription link is an http(s) address; when the client requests it, it receives a list of servers (usually base64-encoded text) and parses it into individual entries. Adding servers one by one on iOS is tedious, so the subscription link is the easiest route — and when you switch devices, you just copy it again.
- Find the subscription link on the overview page of the user panel and tap Copy — the link goes to your system clipboard.
- Back in the client, look for Add Subscription, Import from Clipboard, or the plus button, and choose the subscription type.
- Paste the link, give it a label such as iPhone, and save.
- Tap Update Subscription or pull to refresh, and the server list appears grouped by region.
There's more than one way to import — pick whichever suits your habits:
| Import method | What you need | How it updates | Best for |
|---|---|---|---|
| Sign in inside the client | Username + password | Updates automatically when you open the client | Most users — set it up once and forget it |
| Import a subscription link | A subscription URL | Tap Update Subscription manually | You want to control when updates happen, or switch between several clients |
| Add servers manually | Server address, port, password, encryption method | Edit each server individually | Testing whether one particular server works |
A subscription link is an account credential. Don't post it in public groups or share it as a screenshot; when you switch devices, just copy it again from the user panel.
Step 3: Allow the VPN Configuration
The first time you tap Connect, iOS shows a system dialog titled something like "'Client Name' Would Like to Add VPN Configurations", with two buttons: Don't Allow and Allow. You have to tap Allow here — otherwise the tunnel can't be established and the client will keep showing Disconnected.
After that, the system asks you to authenticate with Face ID, Touch ID, or your device passcode. This is a standard iOS requirement for VPN configurations — it confirms that the person holding the device agreed, not that the client is collecting information.
Once authentication succeeds, a VPN badge appears in the status bar — usually a small box with an arrow in the top-right corner. To check or remove the configuration, go back to Settings:
Settings → General → VPN & Device Management → VPN
Name Configuration written by the client
Status Connected / Not Connected
Connect On Demand On / Off
With Connect On Demand enabled, iOS establishes the connection automatically when you switch to cellular or join an unfamiliar Wi-Fi network, so you don't have to tap Connect every time. To remove the configuration entirely, swipe left on it on the same screen, or just uninstall the client.
If you tap Don't Allow by mistake, you don't need to reinstall the client: go back to the client and tap Connect again, and the system prompt reappears.
Step 4: Choose a Server and Verify It Works
Pick a server before you connect. The server list usually shows the region, the route type, and the result of a latency test; the latency figure is only a snapshot and will change on a different network, so don't keep hunting for the lowest number.
Tap Connect and wait for the status to change from Connecting to Connected. Then run the four checks below to confirm it's actually working, not just showing an icon:
- ✅ Open any IP lookup page — the exit country or region matches the server you picked
- ✅ Run a DNS leak test — the resolver follows your server, not your local ISP's address
- ✅ Open a site that requires an international route, and it loads normally
- ✅ Settings → General → VPN & Device Management shows the status as Connected
There are two ways to disconnect: tap Disconnect in the client, or turn the VPN switch off in Settings. When you move between Wi-Fi and cellular, the system reconnects on its own if Connect On Demand is on; if it's off, you'll need to tap Connect once.
Protocols and Route Types: How to Choose
When you pick a server you'll see names like Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC. These are transport protocols — they decide how data is packaged and disguised. IEPL, relay, and direct, by contrast, describe which path the data takes. The two are independent: the same route can run different protocols.
| Protocol | Transport | Key characteristics |
|---|---|---|
| Shadowsocks | TCP, can forward UDP | The earliest of the group; low overhead and simple to configure, with replay protection added in newer cipher suites |
| VMess | TCP / WebSocket | Includes a time check — the handshake fails if the client and server clocks differ too much |
| VLESS | TCP + TLS | The protocol itself doesn't encrypt; it rides on outer TLS, which keeps overhead lower |
| Trojan | TLS, usually over port 443 | Traffic looks like standard HTTPS, which is friendlier to intermediate network devices |
| Hysteria2 | QUIC / UDP | Better throughput on weak or high-loss networks; affected when your local network blocks UDP |
| TUIC | QUIC / UDP | Also QUIC-based; connections establish quickly, which suits situations where you switch networks often |
Route type, meanwhile, determines the path:
- IEPL: runs over carrier-grade private lines and skips the congested exit points of the public internet, so latency and jitter stay lower during peak evening hours — at a higher cost.
- Relay: traffic connects to a relay server first before heading out, giving a more controllable path than direct connections and mid-range stability.
- Direct: the client connects straight to the exit server — the shortest path, but the most exposed to your local network and exit congestion.
For everyday browsing, documents, and email, any server will do. For jitter-sensitive work like video calls and real-time collaboration, prefer servers marked as IEPL. If you're seeing heavy packet loss on a mobile network, switch to a QUIC-based protocol and test again.
Common Problems and Fixes
Won't connect, connects but no internet, and drops after a while — these three account for the vast majority of cases. Work through the list below in order; you usually won't need to reinstall the client.
| Symptom | Likely cause | Fix |
|---|---|---|
| Spins forever after tapping Connect | The subscription hasn't been updated, or the server you picked is offline | Tap Update Subscription first, then switch to another server |
| Still shows Disconnected after the prompt | You tapped Don't Allow during authorization | Go back to the client, tap Connect again, and re-authorize |
| Shows Connected but pages won't load | Routing rules are sending all traffic direct | Switch the routing mode and check that the rules cover the target domain |
| Needs a manual reconnect after the screen has been locked for a while | Background refresh is restricted, or Low Power Mode is on | Turn off Low Power Mode and enable Background App Refresh |
| Doesn't reconnect automatically after switching Wi-Fi networks | Connect On Demand is off | Turn on Connect On Demand in the VPN configuration |
| Speeds on the same server keep fluctuating | Peak-hour congestion, or the protocol doesn't suit your current network | Switch servers; on a mobile network, try a QUIC-based protocol and test again |
Work down through four layers: subscription, authorization, routing, protocol. If the subscription is wrong, nothing downstream will help. Without authorization, the tunnel can't be built at all. With routing misconfigured, you may connect but never reach the proxy. A protocol mismatch only affects speed, not whether you can connect.
If you've ruled all of these out and still can't connect, take the client's error message to the Help Center, where entries are organized by problem type in more detail.
Everyday Use and Privacy Settings
Whether to leave it on all the time depends on how you use it. If you only visit international sites occasionally, connect when you need to. If you move between Wi-Fi and cellular often, turn on Connect On Demand and let the system handle it.
Routing rules decide which traffic goes through the proxy and which goes direct. Rule mode matches by domain and IP range and is the most data-efficient day to day; global mode sends everything through the tunnel — simple to set up, but it uses up your plan's data faster and can slow down access to local services. Plan data resets monthly on your activation date; check the user panel for your remaining balance.
On privacy, this service's stance is anonymous and no-logs: browsing activity isn't recorded, and signing up doesn't require an email address. That's a statement of policy, not an absolute technical guarantee — no network tool should be treated as an all-purpose shield, and important accounts still need strong passwords and two-factor authentication.
Of the four steps for using a VPN on iPhone, only two really trip people up: importing the subscription and granting system authorization. The first answers where servers come from; the second answers whether iOS will let the tunnel be built. Get past those two and the rest — picking servers, troubleshooting — is just a matter of practice.