Import a subscription and update the server list
A subscription URL downloads a server list; it is not a proxy address to enter in your browser’s network settings. Copy the full URL from your provider, including any parameters after the question mark. Don’t edit or remove any characters. The group name is just a label to identify the source, so choose something easy to recognize. Don’t share the subscription URL in public screenshots or troubleshooting posts—it may contain access credentials.
v2rayN for desktop: Open “Subscription Group” in the main window, go to “Subscription Group Settings,” then click “Add.” Enter a remark and the subscription URL, then save. Back in the main window, switch to the new group, then choose “Update Current Subscription” from the “Subscription Group” menu. It’s normal for the list to be empty right after saving: saving stores the URL, while updating fetches the servers. When the update finishes, confirm that the group contains entries with server names and protocol types.
v2rayNG for Android: Open the top-left menu and go to “Subscription Group Settings,” then tap the plus icon in the top-right corner. Enter a remark and URL, then tap the check mark to save. Return to the main screen, switch to the new group, then choose “Update Subscription” from the top-right menu. When the update finishes, server cards should appear in the group. If the client also has manually imported servers, don’t treat those older entries as proof that the new group updated successfully.
If the list is still empty, first make sure the new group is selected, then check the update message. If it times out, check your internet connection and whether the subscription URL is reachable. If the message says the link has expired, check with your provider to see if the URL has changed. For a certificate error, check the device’s date and time and make sure the URL is correct; don’t disable certificate verification. A successful update only means the list was fetched—it doesn’t mean its servers can forward requests. Make sure at least one server appears in the current group before configuring proxy access.
Choose a proxy mode and app scope
Keep two things separate: the system proxy or Android VPN determines which apps send requests through the client; routing rules determine whether those requests go through a remote proxy, connect directly, or are blocked. Even with “Global” routing, desktop apps that ignore the system proxy won’t be covered. Conversely, a browser that uses the system proxy may still connect directly if a direct-connection rule matches.
v2rayN for desktop: Find “System Proxy” at the bottom of the main window or in the tray menu. Confirm that “Auto-configure system proxy” is available, note the current setting, and wait until you’ve chosen a server before enabling it. For your first test, use a browser that reads the operating system’s proxy settings. If the browser has its own proxy configuration, don’t use it to test the system proxy unless you’ve confirmed it uses system settings. For the initial check, avoid enabling TUN or changing browser extensions at the same time; otherwise, it’s hard to tell which change affected the connection route.
Next, check “Routing” in the same interface. If you already have a routing setup, leave it as is and choose a test site expected to go through the proxy under those rules. If you’re unfamiliar with the rules, you can briefly use the client’s global proxy routing in a network environment where it’s permitted, just for one test, then switch back to your original setup. With split routing, an earlier matching rule may take precedence. To find out why a domain connects directly, see routing fields and match order.
v2rayNG for Android: Check “Per-app proxy” in settings. If only selected apps are proxied, add the test browser to the list. If selected apps are bypassed, make sure the browser isn’t on the bypass list. You don’t need to add apps one by one when per-app proxy is off, but routing rules may still send some requests directly. If another VPN is running, confirm you can switch before disconnecting it—don’t interrupt a connection you need for work. Once the test browser is covered, return to the group list.
Select a server and connect
Choose a server from the group you just updated and note its name, especially if some entries differ only by a suffix. For your first connection, keep the parameters provided by the subscription. Test one server at a time, and don’t update the group while testing: an update may change the list or server parameters, making it hard to compare results with the current settings.
v2rayN for desktop: Right-click the server you want in the list and choose “Set as active server,” or the equivalent option in your version. Highlighting a row with the mouse alone may not switch servers. Confirm that the selected server is active, then choose “Auto-configure system proxy” under “System Proxy.” Check the log area for core startup failures or local port conflicts. If a port conflict appears, first check whether another proxy client is still running; don’t change ports at random. The port used by the system proxy must also match the client’s listening port.
v2rayNG for Android: Tap the server card you want and confirm that the selection indicator is on it, then tap Connect on the main screen. The first time you connect, Android will show a VPN connection request. Make sure it’s from the client you just opened, then approve it. Return to the main screen and wait for the status to show connected. If it switches back to disconnected right after you tap the button, check the client logs to see whether the service started instead of repeatedly tapping Connect. A VPN-connected status only means local traffic capture has started; it doesn’t confirm that the remote server is working.
Protocols and cores: Keep the subscription settings
A server’s protocol name isn’t a connection mode. If the subscription specifies VLESS, VMess, or Trojan, keep the imported protocol and its associated parameters. REALITY is a security configuration used for the connection, not another server type to swap in casually. If the logs say the current core doesn’t recognize a field, first ask your provider which core the config requires, then check the “Core Type” in v2rayN. Don’t delete fields just to clear an error. To distinguish server protocols from connection parameters, see outbound configuration fields. Once the client stays running, test with a real browser request.
Check that the proxy is working
Keep the selected server, routing, and network unchanged. In the browser you chose in step two, visit an HTTPS page expected to go through the proxy under your rules. Don’t rely on a page that’s already open—it may be cached. Reload it and check whether the client logs show a request to the same destination at that time. If the logs show an outbound tag, use your current routing setup to confirm whether it points to a proxy or a direct connection. A running status, a page that loads, or a single latency reading alone doesn’t tell you which route the browser took.
If an IP lookup service is available and its requests are expected to go through the proxy, compare the exit IP in the same browser before and after enabling the proxy. If you know the server’s expected exit IP, matching it is a more direct check. An unchanged IP alone isn’t conclusive: routing rules may send the lookup site directly, or both routes may happen to use the same exit. In that case, check the routing result for the target domain or test against a known exit IP. Don’t switch between Wi-Fi and mobile data during the test, or you’ll lose a consistent baseline for comparison.
If request logging is enabled but you can’t see the test request, return to proxy scope settings and check whether the browser is covered by the client. If the request appears but goes direct, check which routing rule matched; there’s no need to re-import the subscription. If it uses a proxy outbound but times out, try another compatible server in the same group, keeping the browser and routing unchanged. If only the original server fails, investigate that server first rather than changing the entire client setup. If the logs first report a DNS resolution error, identify whether it’s the server domain or the destination domain that failed, then see the DNS module. Don’t start by changing the system resolver.
After verification, if you plan to keep using split routing, switch back from the temporary global routing setup to your preferred rules and test again. If you’re done, restore the previous system proxy setting on desktop before exiting the client. On Android, tap the disconnect button and confirm the system VPN has stopped. Keep the name of the verified group and server; there’s no need to import the subscription again next time.