Step 1: Import a Subscription
Before you start, copy the subscription URL and make sure it comes from a provider you trust. You need a subscription link for retrieving server configurations—not a login page, order page, or documentation URL. Subscription URLs often contain access credentials, so treat them like passwords. Don’t share the full URL in public screenshots or paste it into online conversion tools. If you’re unsure what you received, ask the provider which clients and import methods it supports.
v2rayN: Add a Subscription Group and Update It
Open v2rayN and find Subscription Group in the top menu. Go to Subscription Group Settings and choose Add. Enter a label that helps you identify the source, paste the copied URL into the subscription address field, and check for extra spaces or line breaks before saving. Back in the main window, use the Subscription Group menu to update the subscription. Some versions offer separate options to update through or without the proxy. If you’re not connected yet, try updating without the proxy first.
Once the update finishes, the main window should show the server configurations in the group. Open the group, select a configuration you want to use, and leave its protocol, port, and transport settings unchanged for now. These values come from the subscription; changing them at random may make them incompatible with the server. If the update reports success but the list is empty, check that you’re viewing the right group and that no search or filter is hiding the entries.
v2rayNG: Save a Group and Load Its Configurations
On the v2rayNG main screen, open the side menu and go to Subscription Group Settings. Tap Add, enter a label and subscription URL, then save. Return to the main screen and select Update Subscription from the menu. Depending on the version, this may be called Update Current Group Subscription or something similar. Wait for the update to finish, check that the group’s configurations appear in the list, then select a server configuration. The selection indicator only means the configuration is selected—it doesn’t start the connection.
If your provider gave you a single share link rather than a subscription URL, use the add option on the main screen and import it from the clipboard. Don’t enter it as a subscription group address. The main difference is how updates work: a subscription fetches its contents again from the source, while an individually imported configuration usually needs to be replaced manually. For more on the difference, see Subscriptions and nodes in the concept reference.
Once the configurations have loaded, decide how apps should route requests through the client. Leave the subscription’s original settings intact for now and focus on the proxy entry point and routing options.
Step 2: Choose a Proxy Mode
The two settings that are easiest to confuse during first-time setup are the traffic interception method and the routing rules. System proxy or VPN mode determines how traffic reaches the client. Rules such as bypass mainland China, global, or custom routing determine which outbound route handles requests after they reach the client. Choosing global routing does not make every app use the system proxy automatically. Understand these two layers first so you know what to check during testing.
v2rayN: Start with the System Proxy
In the status area at the bottom of the main window, or in the system tray menu, find System Proxy and select Set system proxy automatically. The tray icon may be in the taskbar’s hidden icons area, so you may need to expand it first. Then check the system proxy status shown by the client instead of assuming it’s active because the window is open. If your browser has a proxy management extension, switch it to use the system settings so older extension rules don’t override your selection.
For your first test, leave TUN disabled. The system proxy is easier to check and works well for testing a browser connection; some apps don’t use the system proxy and can be handled separately later. Don’t enable multiple traffic interception options to get a single app working, or it will be harder to tell which route its requests are taking. For details on system proxy, in-app proxy, and TUN, see Proxy mode concepts.
v2rayNG: Check VPN Mode and App Coverage
Open Settings in v2rayNG and check that it is using VPN mode. If your version doesn’t have a separate mode setting, continue with its default VPN behavior. Next, check Per-app proxy. For your first test, temporarily disable this restriction so the browser you’re testing is included. If you need to enable it, read carefully whether it proxies only selected apps or bypasses selected apps. These settings mean opposite things, so don’t rely only on whether the browser appears in the list.
Next, open Routing settings. For your first setup, keep the client’s default rules or choose Bypass mainland China if that suits your needs. Don’t change domain strategies, DNS, sniffing, and custom rules all at once. Preset names can vary by version; the key is to start with one clear rule set that you can restore. For details on how DNS resolution relates to routing, see the DNS settings chapter in the full guide.
To check whether a request is being routed as expected, you can briefly switch to global routing and compare the results, then restore your original setting. Global routing only controls route selection; it doesn’t guarantee a working connection. It won’t help if the server is unavailable, the subscription has expired, or the app isn’t covered by the proxy. At this point, you should be able to identify both your traffic interception method and routing rules. Next, start the connection.
Step 3: Connect
Before connecting, quit any other proxy or VPN apps that are currently handling network traffic. Multiple apps may overwrite system proxy settings, compete for local listening ports, or create conflicting virtual network interfaces. You don’t need to uninstall them—just stop their connections temporarily. If your device is managed by your employer or school and you can’t change its proxy settings, follow the device management requirements rather than repeatedly changing managed network options.
v2rayN: Set a Server as Active
Return to the main window, right-click the selected server configuration, and choose Set as active server or a similarly named option. Some versions also let you double-click to switch. Check that the active indicator is on the configuration you want, then confirm the system proxy is still set to automatic configuration. v2rayN usually starts or reloads the relevant core when the active configuration changes, so it may not have a separate Connect button like the mobile client. Check the active indicator, status area, and logs together.
If switching configurations immediately produces a core startup failure or port-in-use error, resolve that specific error before changing routing. Try closing any duplicate client instances, then restart the current client. If your system asks for network access permission, allow access as needed. For local use only, you don’t need to enable Allow connections from the local network just to connect a browser.
v2rayNG on Android: Connect and Approve VPN Access
On the main screen, select the configuration you just imported and check that it’s marked as selected. Then tap the Connect button at the bottom of the screen. The first time you connect, Android displays a VPN connection request. Confirm it only after checking that the request is from v2rayNG. This permission lets the app create a VPN interface on your device and handle matching traffic; it doesn’t mean the subscription has passed a connection test. If another VPN is still running, stop it and try connecting in v2rayNG again.
After granting permission, check whether the client enters the running state and whether a VPN icon appears in the system status bar. If the Connect button quickly returns to its disconnected state, open the client log and check the latest errors. A successful subscription update only means the configurations were downloaded and parsed; it doesn’t prove that every server can connect. Likewise, a VPN icon means the interface is active, not that the remote service is reachable. Identify which state is failing before deciding whether to check device permissions or server configuration.
You don’t need to change battery or background restrictions during your first foreground test. Keep the client open and complete the next step. Only check background settings if the connection drops after the app has been in the background for a while. Change one setting at a time and note what you changed; this makes it easier to find the cause than flipping several switches at once.
The client is now ready to handle requests. Don’t rely only on a “Running” status—use an app to check whether traffic is following the expected route.
Step 4: Test the Connection
Open a browser tab and first visit a website that normally works for you to confirm your basic internet connection is still available. Then visit a site that should use the proxy under your current routing rules. Enter the full URL and load it again instead of relying on an already open page; cached content may still appear after the connection stops. If your browser has its own proxy setting or extension, make sure it isn’t overriding the system settings you chose earlier.
Check the Results Alongside the Logs
Check the v2rayN or v2rayNG logs, then refresh the test page. If your current log level records connections, look for entries related to the test request and check whether it was sent through the proxy or routed directly. Few log entries don’t necessarily indicate a problem; some versions don’t log every successful request by default. Don’t change your entire configuration just to get a particular message. If you need to share an error, include only the relevant lines and redact subscription URLs, server addresses, and personal credentials.
Compare results with the connection stopped and restarted. On desktop, clear the system proxy, then enable it again. On Android, stop the VPN, then reconnect. Open a new page each time. Choose a site that actually depends on the current proxy route for this comparison. It’s normal for a site that connects directly to work in both states. If your routing rules send the test site directly, a successful page load alone doesn’t prove the proxy connection is working.
Choose Your Next Step Based on What You See
If both regular websites and sites expected to use the proxy load successfully, keep your current settings and test your usual apps. If the browser works but a desktop app doesn’t, first check whether that app uses the system proxy. On Android, check whether the app is included in the per-app proxy settings. Don’t replace the subscription or adjust DNS right away: the browser test shows the basic connection works, so the issue is more likely how that app accesses the proxy.
If regular websites load but a site expected to use the proxy doesn’t, try another server from the same subscription without changing the proxy mode or routing rules. If all servers fail, check that the service is active, your device clock is correct, and the logs don’t show a connection timeout or handshake error. If even regular websites stop loading when the proxy is enabled, disconnect to restore access, then check the proxy entry point, active configuration, and routing rules. For a detailed troubleshooting sequence, see the complete guide from beginner to advanced. There’s no need to try every advanced setting during your first setup.
Once basic access is confirmed, you can update the subscription and handle routine maintenance. Providers may change subscription contents, so don’t treat manually edited entries as permanent backups. To compare server availability, see maintenance and server testing. Client test results only reflect the specific test conditions; they don’t guarantee the same experience for every website or app.
After these four steps, you should know where to update your subscription, be able to describe your proxy mode, and know how to test the connection with real traffic. Keep the basic settings that work. If you later need TUN, custom routing, or more detailed DNS rules, follow the full guide and add one setting at a time.