1. Import a Subscription and Check the Server List

First, identify what you received. A subscription URL is usually an HTTPS address that the client accesses to retrieve a set of connection configurations. Content beginning with vmess://, vless://, or trojan:// is usually a single share link. Each uses a different import option. Don't paste a subscription URL into the manual server editor, or copy only the domain-looking part of a share link.

v2rayN: Add a Group, Then Update Subscriptions

Open the v2rayN main window, find the subscription group menu, and open subscription group settings. Click Add. Enter a recognizable name in the remarks field, such as “Everyday,” then paste the full subscription URL into the address or URL field. Check for spaces, line breaks, or punctuation added by a chat app at either end of the URL, then save. This creates a subscription entry; it's normal for no servers to appear in the main list yet. You still need to update the subscription.

Return to the main window and choose Update current subscription from the subscription menu, or update all enabled subscriptions. If you don't have a working connection yet, start with an update that doesn't use a proxy. Use an update option that routes through an existing proxy only if the subscription provider specifically requires it. When the update finishes, select the group you just created. The main panel should show server names, protocol types, and other details. Confirm the configurations appear before continuing; there's no need to change each server's settings yet.

v2rayNG: Save the Subscription, Then Update the List

In v2rayNG, open the menu, go to subscription group settings, and use Add to enter a remark and subscription URL. Save, then return to the main screen. Open the main menu and select Update subscription, or the equivalent option in your version. Wait for the result message, then check the configuration list. If the group appears in subscription group settings but no configurations show on the main screen, check whether you updated the subscription, enabled the group, and cleared any filters on the current list.

On Android, after pasting the URL, check that it is complete in the input field. Don't post a full URL containing access credentials in a public chat. A subscription URL provides access to configurations; when sharing a screenshot for troubleshooting, hide URL parameters, user IDs, passwords, and QR codes. If you need to contact the provider, sharing the error message and steps to reproduce it is usually safer than sharing the full subscription.

If You Have a Single Share Link

If you received a share link, copy the entire link. In v2rayN, look in the server menu for an option such as Import share links from clipboard. In v2rayNG, tap Add and choose Import from clipboard. For a QR code, use the client's scan option and grant any required permissions when prompted. A successful import adds a configuration, but it doesn't turn the link into an automatically updatable subscription or guarantee that the server is currently reachable.

If an update reports success but the list is still empty, clear any group filters first. Then check that the provider returned a configuration the client can recognize, rather than a web login page. If parsing fails, don't reinstall the client right away. Check the link type, make sure you copied the entire link, and review the format instructions from the provider. For the difference between share links, subscription collections, and servers, see the Glossary. Once servers appear, choose how traffic should be routed through the client.

2. Choose a Proxy Mode and Start with Routing Rules

System proxy settings and routing modes do different jobs. The system proxy tells apps that follow system settings to send requests to the local client. Routing rules decide whether requests that reach the client should use the proxy, connect directly, or be blocked. Changing routing rules alone doesn't connect your browser to the client. Conversely, enabling the system proxy doesn't mean it will handle every type of traffic from every app.

v2rayN: System Proxy for Traffic Entry, Routing for Traffic Exit

In the v2rayN main window or tray menu, find Automatic system proxy configuration. Familiarize yourself with this option first; you'll enable it when you connect. Next, find the routing settings or routing mode selector and choose a built-in rule set suitable for everyday use. Names vary by version, so read the rule descriptions and check which destinations connect directly and which use the proxy rather than guessing from the name.

For your first setup, keep the default local listening port. Don't change it just to match a screenshot. If an app requires manual proxy settings, use the listening address, port, and protocol shown in your client. If you're using the proxy only on this device, there's no need to enable Allow connections from the LAN. That setting controls whether other devices can access the local proxy and has no direct bearing on subscription imports.

Global proxy mode can help diagnose whether routing rules are affecting a request, but “global” generally refers to traffic handled by the relevant routing rules. It doesn't automatically cover all network activity on your device. For everyday use, start with rule-based routing. If an app doesn't follow the system proxy, check its own network settings. This guide doesn't require TUN mode, or changes to virtual adapters, DNS, and routing rules during your first connection.

v2rayNG: Check Routing Rules and App Scope Separately

In v2rayNG settings, review the routing options and choose a rule mode that matches your needs. If you've enabled per-app settings, check whether the browser you're testing is included and whether the list is set to proxy only selected apps or bypass selected apps. The same selections can have opposite effects depending on which mode is active; a check mark alone doesn't tell you how an app will be routed.

Leave other advanced settings at their defaults for now. Connect and verify the setup first, then adjust the app scope if needed. This makes it easier to tell whether a problem is due to a failed server connection or traffic not reaching the client. For more on how protocols, cores, and routing work together, see the Protocols and Cores Reference. For now, choose a mode you can explain, then select a server.

3. Select a Server and Connect

With the servers imported and a proxy mode selected, choose one configuration from the list as your active connection. Don't change server addresses, security layers, or transport settings across multiple servers at once. Subscription fields are usually designed to match the server, and changing the protocol or port at random can break a working configuration. For initial troubleshooting, leave imported settings unchanged and switch only the active server.

Test a Server, Then Set It as Active

In the v2rayN server list, select one or a few candidate configurations and look for a connection test option in the right-click menu. TCPing mainly checks whether the destination port is reachable. A real connection test attempts to access a test destination through the proxy, so it more closely reflects the actual connection path. The results aren't equivalent, and an inaccessible test destination can affect them. A single test score can't tell you whether a server will work well for every app.

Choose a configuration that passed testing and select Set as active server, or the equivalent option in your version. Check the active marker, status bar, or current server details at the bottom to confirm that the selected configuration is in use, not merely highlighted in the list. Some versions switch servers on double-click, but confirm the change using the active marker or status information.

v2rayN: Confirm the System Proxy After the Core Starts

After you select an active server, v2rayN usually loads its configuration and starts the core. Check the log panel for configuration or startup errors. If you see an error, resolve it before enabling the system proxy. Once the core is running normally, set the system proxy to Automatic system proxy configuration and confirm its status in the client menu or system proxy settings. There's no need to look for a large Connect button like the one in v2rayNG.

If you see a local port-in-use message, check whether another instance of the client is running or another proxy app is listening on the same port. Close duplicate instances and try again; this makes the cause easier to identify than changing several ports at once. If a field is unsupported or the configuration can't be parsed, note the error and check whether your client and core support that configuration. The same protocol name doesn't mean every extension setting is interchangeable.

v2rayNG: Approve the System Connection Request

In the v2rayNG main list, tap the configuration you want and confirm it is selected, then tap Connect. The first time you start a connection, Android shows a VPN permission prompt. Review it and allow the request only after confirming that v2rayNG initiated it. This uses the system's traffic-routing interface; it doesn't mean you need to buy another connection service. If you deny permission, having servers in the list doesn't mean a connection has started.

After connecting, check the client status and the system VPN indicator. If another VPN connection is active on the device, disconnect it before trying again. If the connection stops immediately, errors keep appearing, or no running status is shown, check the logs instead of repeatedly tapping Connect. Once the status is stable, leave the client running and test the connection in a browser.

4. Verify the Proxy and Check Network Recovery

A lit connection icon is only the first sign that the proxy is working. A complete check includes the client status, whether an app can complete a request, and whether the request follows the expected route. A webpage loading by itself doesn't prove the proxy works: it may match a direct-connection rule, come from cache, or use the browser's own proxy settings. Test a destination with a known routing rule so you can interpret the result.

Use a Fresh Request to Check the Connection Path

First confirm that your regular network is working. Open a new browser tab and visit a trusted HTTPS page with clear, predictable content. Wait for the page and its required resources to load; don't rely only on the title appearing in the address bar. If you've visited the page before, refresh it or open a new page path to reduce cache effects. Don't enter account details on an unfamiliar site for testing, and don't paste your subscription URL into an online testing tool.

Return to the client and check the connection logs. If the current log level shows the relevant details, verify that the request destination, connection errors, and exit label match the routing rules in use. If the logs don't show enough information, temporarily choose a suitable log level for troubleshooting, then restore the previous setting. Logs may include destinations and local paths, so check for sensitive information before sharing screenshots.

If you need to check your exit IP, use a trusted IP lookup service, but keep its limits in mind: it shows the exit used for that specific request, not whether every app or domain takes the same route. With rule-based routing, different destinations may use different exits by design. Compare the result with your current rules and client logs rather than relying only on whether the IP changed.

If the Test Passes but Pages Won't Load

First check whether the browser's traffic is actually reaching the client. On desktop, confirm that the system proxy is enabled, check whether a browser extension overrides system settings, and look for another tool that may be changing the proxy settings. On Android, confirm the connection is still running and that the browser is included in the app scope. If the client logs show no activity when the browser makes a request, troubleshoot the traffic entry path before switching protocols.

If the logs show requests but connections time out or secure handshakes fail, try another imported configuration and check that the device's date and time are correct. Consider DNS settings only if domain lookups are failing. Don't replace every DNS parameter at the outset. Change one factor at a time, repeat the same request, and note what changes. For specific errors, see the Help Center rather than combining multiple advanced changes into one troubleshooting attempt.

Disconnect and Confirm Your Network Is Restored

Before finishing on desktop, select Clear system proxy in v2rayN, then exit the client. Otherwise, apps that follow system proxy settings may keep sending requests to a local port that's no longer listening, making the browser appear to lose network access after the client closes. If you've already closed the client, reopen it and clear the proxy, or check system network settings for leftover manual proxy settings. Disabling system security isn't a solution.

On Android, tap Stop in v2rayNG, then confirm the system VPN indicator disappears and your browser works over your regular network. If the system terminates the client in the background, check the system connection status rather than assuming the connection ended just because the app window closed. Only if you actually experience background interruptions should you review battery and background activity restrictions. You don't need to grant every permission during initial setup.

For future updates, use the existing subscription group instead of creating a new group with the same name each time. If a server stops working, update the subscription, select another configuration, and repeat the checks. If server settings change, use the updated configuration from the provider. For in-depth guidance on protocol selection and core compatibility, continue with the Protocol Guide. The four steps on this page also make a useful check after any changes.

v2rayN Subscription Import and Connection Guide