Import a Subscription and
Set Up a Proxy Connection

01 Import a Subscription and Update the List

Copy the complete URL provided by your subscription provider. A subscription URL retrieves a set of server configurations; it is not the same as a single-server share link. Don't include explanatory text, quotation marks, or line breaks, and don't use the URL of a subscription management page. If you're unsure, check the provider's instructions for the subscription link rather than guessing by editing the URL.

v2rayN: Add a Subscription Group

Open v2rayN and find Subscription Group or Subscription Group Settings in the top menu. In the management window, choose Add. Enter a recognizable name in the remark field, then paste the full URL into the subscription address field. Leave the other options at their defaults for the initial setup, then save and close the window. This only registers the URL; it's normal for the server list to remain empty until you update the subscription in the next step.

Return to the main window and use the Subscription menu to update the relevant group. Before your first connection, if the menu offers updates through or without a proxy, choose the option without a proxy. The update will succeed only if your current network can reach the subscription URL. Afterward, switch to the group you created and check for server names, protocol details, and other entries. If the log reports a request failure, verify the URL and subscription status; don't keep creating groups with the same name.

v2rayNG: Add the URL and Fetch Configurations

Open the side menu, go to Subscription Group Settings, tap Add, enter a remark and subscription URL, then save. Return to the main screen and select Update Subscription from the menu; wait for the request to finish. Depending on the version, you may see an option to update all groups or a single group. If you have only one group, update that one. Back in the configuration list, confirm the imported servers appear. Tap one to select it; there's no need to connect yet.

If the update completes but no entries appear, first check that the right group is selected, then verify the URL is still valid and the response uses a subscription format the client supports. Opening a subscription management page in a browser doesn't mean the client received valid configurations. See the glossary for the difference between subscription formats and node share links. If updates keep failing, continue with installation, setup, and troubleshooting in the FAQ.

If you have only a single share link, copy it and use the client's Import from Clipboard feature; use the scanner to import a QR code. After importing, check that the protocol, address, and transport security match the provider's instructions. A matching name alone doesn't confirm that configurations are identical. Put manually added entries in a separate group so they don't get mixed in with subscription updates. Once a configuration is available to select, move on to proxy mode settings.

02 Choose a Traffic Capture Method and Routing Mode

There are two separate questions to answer here: whether app traffic enters the client, and which outbound route it takes afterward. System proxy and VPN mode control traffic capture; direct, proxy, and block rules determine routing. Selecting a server alone usually won't make your browser use it automatically. For the initial setup, choose an easy-to-check capture method and keep routing simple so you can troubleshoot one thing at a time.

v2rayN: Start with the System Proxy to Test Your Browser

Find the System Proxy option at the bottom of the main window or in the tray's right-click menu. Check its current state, then choose Set system proxy automatically or a similarly named option when you're ready to connect. Don't mistake Clear system proxy for a routing mode: clearing it usually sends apps that rely on the system proxy back to a direct connection. The exact menu location varies by desktop version, but the goal is to point the system proxy to the client's local listener.

Next, open the routing options and start with the built-in bypass-LAN preset. If a preset includes common direct-connection rules, you can choose it to suit your needs. Preset names don't tell the whole story; check the rules included in the selected preset. You don't need TUN mode or custom local ports for an initial test. The system proxy doesn't cover every app: some apps must be configured to use it in their own settings. Check those differences one by one after the connection works.

v2rayNG: Keep VPN Coverage Broad for the First Test

Open Settings and confirm that VPN mode is enabled. If your version offers a mode that exposes only a local proxy port, use it only for apps explicitly configured with an upstream proxy; it's not the right choice for this guide's initial connection. Turn off per-app proxying for the first test so the browser won't be excluded. If you've already set an allowlist or bypass list, note its current settings, then restore a straightforward traffic-capture scope.

In routing settings, start by enabling bypass LAN so local network devices connect directly. Choose other presets only from the options actually available in your client. Don't change remote DNS, enable FakeDNS, turn on Mux, and switch protocols all at once. Subscriptions usually include the transport settings required by the server, and changing them at random can break a working configuration. To understand these options, read the protocol guide rather than enabling them one by one during your first connection.

When you're done, return to the server list and check that switching groups hasn't changed the selected entry. You should now have an imported configuration, a clear traffic capture method, and basic routing rules. Next, start this configuration without running another proxy client at the same time, so you can match the results to the settings in use.

03 Connect and Check the Client Status

Before connecting, make sure the device has the correct time and time zone; automatic time is recommended. Some authentication and secure handshakes depend on accurate time, and a large clock error can cause failures that are hard to diagnose from the interface. Also check that the network itself is working. If it requires a web sign-in, complete that first. A running status in the client doesn't replace these basic checks.

v2rayN: Set the Active Server and Check the Logs

Select the target entry in the server list, then use the right-click menu to choose Set as active server or the equivalent option. Some versions also let you double-click an entry; for your first setup, follow the menu label. Confirm that the active marker moves to the right configuration, then check that the system proxy is set as described in the previous step. v2rayN usually loads or reloads the core when you switch the active configuration; it may not have a prominent standalone Connect button, so don't follow the Android steps here.

Open the log panel in the main window and look for specific errors, such as a failed configuration load, a port conflict, or an unsupported field. If loading fails, review the selected configuration. If a port is in use, close any tool that may be using the same local port. No immediate record of a remote connection doesn't necessarily indicate a problem: some protocols connect only after an app makes a request. Trigger a browser request in the next step.

v2rayNG: Connect and Approve the System Request

On the main screen, make sure the intended configuration is selected, then tap Start. The first time you connect, Android will usually show a VPN connection request explaining that the app wants to establish a VPN connection. Confirm that the request is from v2rayNG before approving it; without approval, the client can't capture traffic in VPN mode. After approval, the Start button or status message will change, and a VPN indicator may appear in the system status bar.

If the system says another VPN connection is active, decide whether to stop the existing service before continuing. Avoid switching repeatedly between two tools while the configuration is still being tested. If startup fails, open the side menu and check the log entries around the time of the attempt. Server addresses and account fields in logs may be sensitive; redact them before asking for help, and share only the error type and relevant settings.

Don't consider setup complete just because the client says it's running. That status usually confirms only that a local service or VPN tunnel has started; it doesn't prove remote authentication, DNS lookups, or access to your destination are working. A test button may check only one connection condition, not every app. Leave the client running, make a real request in the next step, and check the logs to see how traffic is routed.

04 Verify the Connection and Save Your Settings

The goal isn't just to see an icon; confirm that the app's request reaches the client, matches the expected rule, and completes successfully. Start with an HTTPS page that should use the proxy under your current rules, then choose a page for everyday direct access. Test pages should reflect your actual use case. If the page matches a direct-connection rule, opening it successfully doesn't prove the proxy was used.

Cross-Check Real Requests Against the Logs

Open a new browser window and visit the test page. If needed, use a private window to reduce the effects of cached content and existing connections. Check the client logs for a matching destination domain or connection entry, and confirm that any visible outbound tag matches your expectations. Log details vary by level. If individual destinations aren't shown, don't assume the connection failed; first check whether a more useful diagnostic log level is available, then restore your usual setting when you're done.

If you use an IP lookup page, treat it as a supplementary check and first confirm that its domain is routed through the proxy. With split routing, different destinations may use different outbound routes, so one lookup result can't represent all traffic. Opening a webpage also doesn't prove DNS is configured as expected. First confirm basic access; for DNS troubleshooting, see the relevant guidance in the FAQ.

Next, visit a page that should connect directly and confirm that the basic routing rules haven't disrupted normal access. On desktop, also test the apps you actually use. If the browser works but an app doesn't, check whether it reads the system proxy or has its own proxy settings before changing servers. On Android, if only one app is affected, review the per-app proxy list first, then check the app's connection method and routing rules.

If It Fails, Troubleshoot One Layer at a Time

If no pages load, stop the client and clear the system proxy on desktop, or stop the Android VPN, then confirm the original network still works. Once it does, check the subscription status and active configuration. If the client starts but logs show authentication or handshake errors, update the subscription and verify the device time first. If only domain names fail, investigate DNS settings. Change one setting at a time, restart, and test the same page so you can tell what helped.

After a successful test, note the current group, active server, traffic capture method, and routing preset. If you need a backup, use the client's export feature and check exactly what it includes; subscription URLs, manual configurations, and routing rules may require different export options. Store backups somewhere secure, and don't share them publicly. Subscription updates can change group contents, so save important manual entries separately.

Disconnecting and Connecting Again Later

Before you stop using v2rayN on desktop, clear the system proxy from its menu, then exit the client to avoid leaving the system pointed at a closed local port. If your device uses proxy settings managed by your organization, restore them as required rather than overwriting them. On Android, tap Stop, confirm the client shows that it's no longer running, and check that the VPN indicator has disappeared. Returning to the home screen doesn't stop the service.

You usually don't need to import the subscription again next time. Open the client, update the relevant group if needed, confirm the active entry, and reconnect. If the issue appears after locking the screen or leaving the app in the background, check the system's background restrictions instead of reinstalling. Your initial setup is complete. For protocol differences and core compatibility, read the protocol guide; for everyday issues, find the relevant topic in the FAQ.