To set up a VPN on iPhone, start by choosing an iOS client that can import subscriptions. Don’t paste the subscription URL into the system’s “Server” field. After importing, select a server, allow the VPN configuration, and check that the app you want to use is routed as expected.
Check iOS client and subscription compatibility
First, open the client instructions in your service dashboard. Then check the app’s name, developer, and system requirements in the App Store. If you can’t find the recommended app, check whether it’s available in your current App Store region. Don’t choose an app based on its icon alone, and don’t submit your link to an unknown subscription-conversion website.
Check compatibility in two parts: the client must be able to read the subscription’s format and support the protocols used by its servers. For example, an app may support manual Shadowsocks setup but not recognize the subscription format provided by your service dashboard. iOS’s built-in manual VPN settings are for system-supported connection types such as IKEv2—not for importing Shadowsocks, Trojan, or VLESS subscriptions.
If you’re moving from another device, look up the iOS-specific import instructions in your service dashboard. A desktop client’s exported configuration may refer to separate rule files or plugins, so copying it over doesn’t guarantee it will work. Find VPNQiang’s setup instructions on the site’s Getting Started page.
Import your subscription and update the server list
- Copy the correct link. Find the subscription section in your service dashboard. If it offers different options for different clients, choose the one for the app you installed. Copy the entire URL; don’t remove anything after the question mark.
- Add a remote subscription. In the client, open “Subscriptions,” “Configuration,” or “Remote Configuration,” then choose an option such as “Import from URL.” The labels vary by app. If the form asks for a port, protocol, and password, you’re probably looking at the manual setup form for a single server.
- Make sure the list is populated. Save the subscription, tap “Update” or “Refresh,” then open its server list. Seeing the subscription name only confirms that the link was saved. Seeing servers means the client read a recognized configuration, but it doesn’t confirm that a server can connect.
- Select a server to test. If the app has multiple configurations, enable the one you just imported, then choose a server. When troubleshooting for the first time, don’t change routing rules and switch servers at the same time—you won’t know which change made a difference.
Allow the VPN configuration
After selecting a server, turn on the connection in the client. The first time, iOS will usually ask whether to let the app add a VPN configuration. Check the app name in the prompt, tap “Allow,” and follow the system instructions to authenticate. This authorizes the app to create a connection on your device; it doesn’t install a root certificate, and you don’t need to accept a configuration profile from an untrusted source.
If you tapped “Don’t Allow,” return to the trusted client and try connecting again. If the prompt still doesn’t appear, go to “Settings → General → VPN & Device Management” and check whether a VPN configuration is already there. Menu names may vary slightly by iOS version. An older client with on-demand connection enabled may reconnect automatically after you disconnect. Turn off on-demand connection in the old client and disconnect it before testing the new one. If your organization manages the device and restricts VPN configurations, ask the administrator to check; don’t remove the management profile.
Verify the VPN is connected and routing as expected
First, check that the client says it’s connected, then open the website or app you actually want to use. Don’t rely on the status bar icon alone: “VPN connected” means the tunnel is up, not that every request uses the same route. In rule-based mode, some websites may connect directly, so your browser may show the same public IP as before.
- ✅ Stay on the same network and open the same test page once with the VPN disconnected and once connected. If you’re comparing public IP addresses to check your route, make sure the client’s rules send the test site through the proxy.
- ✅ Send a new request from the app you want to use. If the client has connection logs, check whether the destination domain matched a direct-connection rule, a proxy group, or the selected server. Don’t rely on a page that may be cached.
- ✅ If your browser works but the app doesn’t, note the full error message first. An in-app login error, a region notice, and a network timeout are different kinds of problems.
Test the request that matters. The server list confirms that the subscription was imported; the system status confirms that the tunnel started. Setup is only verified for your use case once the target app can send a new request, receive a response, and follow the expected route.
Subscription won’t import, connection fails, or apps won’t load
| What you see | Check first | What to try next |
|---|---|---|
| Update fails; server list is empty | Check that the full URL was copied and that the subscription format matches the client | Copy the link in the correct format from your dashboard, then update again on a network that can reach it |
| Servers appear, but the connection switch turns off again | Check whether iOS has authorized the VPN configuration and whether another VPN is reconnecting | Check the iOS VPN status and the client’s error message. If it mentions a handshake or timeout, test a different server separately |
| Connected, but most websites won’t load | Check whether the network requires sign-in and whether connection logs show a DNS or transport error | On hotel or airport Wi-Fi, disconnect the VPN, sign in to the network, then reconnect and test the same page |
| Only one app won’t load | Check whether the app’s requests match the expected rule and whether the error comes from the platform itself | Check the rules and the platform’s message first; there’s no need to reinstall the client or reset all network settings |
If the issue occurs only on a particular Wi-Fi network, keep the same server and test on another available network. If it works there, the issue is related to the network you connected through, but that alone doesn’t identify the cause. If it fails on both, keep the network fixed and try another server. Change one thing at a time so your troubleshooting notes can pinpoint the problem.
If the network is working but the logs repeatedly show DNS lookup timeouts, check whether the client is using the DNS settings from the subscription or a manual override. A failed lookup isn’t the same as a DNS leak: the first means no result was returned; the second means the query took a different route than expected. Don’t infer the DNS route from whether your public IP changed—check each separately.