iOS VPNbeginner guide: import a subscription and connect

Follow the steps to set up a VPN on your iPhone: choose a compatible app, import a subscription, approve the VPN configuration, and verify the connection.

Get a VPN app: Check subscription compatibility first

To set up an iOS VPN on your iPhone, first choose an app that supports your subscription format. Then import the subscription, approve the VPN configuration, and test the connection. Don’t rely on the status switch alone: try a fresh request in the app you need and confirm that traffic uses the expected route.

Check the app name and developer against your provider’s iOS instructions, then get the app from a trusted source. 2NVPN users can start with the getting started guide, then check the dashboard download page for the currently supported app. An app with the same name on another platform may have different import steps and features, so follow the instructions for the iOS version.

Check subscription format and route protocol compatibility separately. The format determines whether the app can read the route list; protocol support determines whether a selected route can connect. Even a standard HTTPS subscription URL can return data in different formats, so you can’t tell compatibility from the URL alone. The manual VPN settings in iOS aren’t a general-purpose subscription importer—don’t enter a subscription URL in the system’s server address field.

Import the subscription: Check the route list before connecting

  1. Find the right import option. In your service dashboard, locate the subscription option for your current app. Copy the full link or use an import method the dashboard provides for that app. Don’t copy the dashboard page URL or use a single route’s share link as a full subscription.
  2. Add and update. In the app, look for an option such as “Subscription,” “Configuration,” or “Import from URL.” Paste the link and save it. If the app doesn’t fetch it automatically, trigger an update manually. Menu names vary by app version; if the app reports an unsupported format, check the export options in your dashboard.
  3. Verify the update. Check that the app reports a successful update and that the expected routes appear in the list. If the app separates configurations from routes, enable the newly imported configuration first, then select a route from it. Some apps retain the old list after a failed refresh, so seeing routes doesn’t confirm that this update succeeded.

Allow adding the configuration: Review the system prompt

Once you’ve chosen a route, start the connection in the app. Apps that create a system tunnel usually ask to add a VPN configuration the first time they connect. Make sure the request comes from the app you just installed and are using, then approve it when prompted by iOS. If you previously denied the request, try connecting again from the app. If no prompt appears, check the app’s error message and whether a corresponding configuration already exists in Settings.

On a company- or school-managed device, management policies may restrict configuration changes. Contact the administrator rather than deleting managed configurations yourself. On a personal device, if another network tool is taking over the connection, temporarily pause connections you manage and don’t need right now, then test the new configuration. Don’t install unknown profiles or trust root certificates just to connect; that’s separate from approving a VPN configuration.

After approval, check that the app shows the selected route as connected, then confirm the VPN status in iOS. If the app starts connecting but quickly returns to disconnected, check the error instead of importing the same subscription again. Importing retrieves route details; approval lets the app create a tunnel. Neither confirms that the route is actually reachable.

Verify the connection: Distinguish system status from real-world access

  • ✅ Note how things work before and after connecting on the same network. Don’t switch between Wi-Fi and cellular data during the test, or you may mistake a network change for a route change.
  • ✅ After connecting, make a fresh request in the app you want to use—for example, open a page that hasn’t loaded before or refresh the app to fetch new content. A cached screen doesn’t prove the current request succeeded.
  • ✅ If the app provides request logs, check which rule matched the target domain and whether the request went direct or through the selected route. Checking a public IP address alone doesn’t verify access in the app you’re testing.
  • ❌ A VPN status icon, an address shown by an IP test site, or the app’s latency reading doesn’t prove that every app and domain uses the same route.

What counts as a successful connection: The app establishes a connection, the target app completes a fresh request, and—when available—the logs confirm that the request took the expected path. In rule-based mode, an IP-check website may use a direct connection. Seeing your usual address there doesn’t, on its own, mean the tunnel has failed.

If an IP test passes but you’re also concerned about DNS, check name resolution separately. The exit IP shows where the test request went out; it doesn’t tell you which resolver handled the domain. Compare the app’s DNS settings with its resolution logs. Results from a test website apply only to that test, and your browser’s encrypted DNS settings may affect what you see. Don’t conclude there’s a DNS leak just because a single result shows a different region from the route.

Troubleshooting: Find the issue by failure stage

Choose the next check based on what you see
SymptomCheck firstNext step
Import fails or the list is emptyWhether the URL is complete, the current network can reach the subscription service, and the format is compatibleCopy the correct link from the dashboard again, update manually, and check the error message
Routes appear, but the connection times outThe selected route, the latest subscription update result, and the underlying networkKeep the network unchanged and try another available route in the same configuration
Connected, but one app won’t loadThe rule matching the target domain, DNS resolution, and the target service’s statusRetry the same action and check the logs for a DNS resolution failure or a direct connection to the target
Disconnected after switching networksWhether the new network is online and whether public Wi-Fi requires sign-inGet the new network online first, then reconnect and test the target app again

Change one thing at a time while troubleshooting. For example, if switching routes on the same Wi-Fi fixes the issue, check the original route or the path to it first—but don’t assume that route is unusable on every network. If several routes fail only on one Wi-Fi network, first check whether ordinary webpages load on that network without the VPN. On public Wi-Fi, disconnect to complete any sign-in or access step, then reconnect and test again.

If your app offers rule-based and global modes, briefly switch modes on a network where it’s permitted to compare the same failed request, then restore your original setting. If access works in global mode, check the routing rules or DNS settings that change with the mode; this doesn’t prove a specific rule is wrong. For regular use, choose which traffic should use a route based on your needs.

If you still can’t connect, use the support page to share the app name and version, iOS version, network type, time the issue occurred, a redacted error message, and what happened after trying another route or network. Specify whether the failure occurred during “subscription update,” “configuration approval,” “connection,” or “accessing the target app.” This is more helpful than sending a screenshot of the connection screen alone.

Start Free