This guide is for anyone whose v2rayN setup works on a PC and who wants other devices on the same home network to use its local proxy. Find the PC’s LAN IP address and HTTP listening port, check the firewall, then enter the details in each device’s Wi-Fi proxy settings. If a connection fails, troubleshoot the relevant step.
First, identify the port you’re sharing
Allow LAN connections changes which interfaces v2rayN’s local proxy listens on. Other devices can connect to the proxy port on your PC, and requests are still handled by the client and core running there. This setting does not copy subscriptions or server configurations to your phone or TV, or change those devices’ network settings. The PC must be on, connected to the LAN, and running v2rayN with a working connection.
Traffic flows from the device to your PC, where the proxy processes it. Enter the PC’s IPv4 address on the current LAN—not the router’s admin address or a proxy server address. Enabling Set system proxy alone is not enough: it mainly affects apps on the PC that use the system proxy. Other devices still need the proxy host and port entered separately.
Typical setups provide both SOCKS and HTTP ports. If a device’s Wi-Fi settings only offer an “HTTP proxy” or “Proxy hostname” field, use the HTTP port currently shown in v2rayN. Don’t swap the ports just because their numbers are close. Use the SOCKS address and port only in apps that explicitly support SOCKS5. The numbers below illustrate where each value goes; always use the values shown in your local settings and logs.
Enable listening in v2rayN and find your PC’s address
On your PC, first select a working connection and confirm that a local app can reach its destination through v2rayN’s proxy. Then open Settings → Parameter settings, find Allow LAN connections or a similarly named option such as Allow connections from LAN, enable it, and save. The wording and location can vary by version, so check your actual interface. If other devices still can’t connect after you change the listening settings, restart the core if prompted, then check the logs for the local listening address and port.
When checking the listening address, distinguish 127.0.0.1 from 0.0.0.0: the former accepts connections only from the PC itself; the latter listens on available network interfaces, subject to the system firewall. You can also listen on a specific LAN address, but check the setting again if the PC changes networks or gets a new address. Don’t expose the proxy port through your router’s public port forwarding. This guide covers connections on a trusted local network only.
v2rayN on your PC
- Settings path
- Settings → Parameter settings
- LAN connections
- Enabled
- Listening address
- Make sure it is not limited to 127.0.0.1
- HTTP port
- Note the value shown on your PC
After saving, check the logs to confirm the proxy port is listening.
HTTP proxy on other devices
- Proxy type
- Manual
- Server
- 192.168.1.20, example only
- Port
- 10809, example only
- Network requirement
- A LAN that can reach the PC
Enter the PC’s actual IPv4 address and HTTP port, not the subscription URL.
On a Windows PC, run ipconfig in Command Prompt and find the “IPv4 Address” for the Wi-Fi or Ethernet adapter in use. On a Mac, open System Settings → Network and check the IP address in the details for your current network. If you see virtual adapters, disconnected adapters, or other subnets, use the address on the network shared with your phone or TV. For example, if a device’s address is 192.168.1.36, the example PC address 192.168.1.20 may be on the same common home subnet.
Quick check: Read the listening log before configuring devices
If the v2rayN logs show the proxy listening only on 127.0.0.1, fix the PC settings first. Changing the phone’s IP or browser settings won’t make the PC accept LAN connections.
Allow the connection through the firewall, and limit who can access it
Even if the proxy listens on a LAN address, Windows Firewall may block other devices. First make sure the current network is set to Private, then check any first-run prompts to allow v2rayN or its core through the firewall. If you need to create an inbound rule manually, select TCP, enter the actual HTTP port you’re sharing, enable the rule for the Private profile only, and restrict its remote addresses to your home subnet—for example, 192.168.1.0/24. If devices will also use the SOCKS port, check that port separately as needed.
A shared network name doesn’t guarantee that devices can reach each other. Guest Wi-Fi, router client isolation, and separate VLANs can all prevent a phone from connecting to a PC. When a phone uses mobile data, it may not send traffic to the proxy over the expected Wi-Fi connection. For troubleshooting, connect both devices to the same router network with device-to-device access enabled, temporarily turn off other proxy settings on the devices, and note whether the PC’s IP changes after reconnecting.
- Allow only trusted local devices to access the proxy port. Don’t forward that port to the public internet through your router.
- Restrict the firewall rule by network profile and remote address instead of turning off the firewall entirely.
- When you leave the shared network or no longer need proxy sharing, turn off Allow LAN connections and review any temporary firewall rules.
Quick check: If the PC works but a device times out, check the inbound connection path
If the local proxy works on the PC but a phone times out connecting to the proxy host, check the listening address, firewall rules, and router isolation first. Switching to a different remote server usually won’t help if the PC’s port itself can’t be reached.
Configure a phone or TV
On an Android phone, open the details or edit screen for the connected Wi-Fi network. Under Proxy, select Manual. Set Proxy hostname to the PC’s LAN IPv4 address and Proxy port to the HTTP port shown in v2rayN, then save. Menu names and locations vary, but make sure you’re editing the Wi-Fi network currently in use. When switching networks, check whether the new network still has the same proxy settings.
You can enter the PC’s IP address and HTTP port on a TV only if its network settings provide an HTTP proxy field. Some TV apps ignore the system Wi-Fi proxy, while others proxy only certain requests. Saving the setting doesn’t mean every app will use that port. Test with the TV’s built-in web browser or an app known to support the system proxy before troubleshooting a specific app. If the TV has no proxy setting, enabling LAN connections in v2rayN alone won’t connect it automatically.
- Note the PC’s current IPv4 address and HTTP port, and keep v2rayN running.
- In the phone or TV’s settings for the current Wi-Fi network, select manual HTTP proxy.
- Enter the PC’s IP address and HTTP port, save, then test a website that should be accessible.
- When you’re done and want the device to connect directly again, set the Wi-Fi proxy option to None.
If you want an Android device to manage its own connection instead of relying on the PC to stay on, you can use v2rayNG or v2flyNG and import a connection using a configuration method it supports. That means running a client directly on the device, not sharing a proxy over your LAN. The two approaches use different network paths and have different failure points, so first identify which one you’re using when troubleshooting.
Troubleshoot by symptom
Test the PC first, then the connection from the device to the PC’s port, and finally the specific app. If the PC itself can’t access destinations through the current proxy, check the selected v2rayN connection, core status, and logs. Even with correct settings, the phone is just sending its requests to a PC that isn’t working properly. If the PC works but the phone says the proxy server is unavailable, check LAN listening, the firewall, and the address.
Phone says it can’t connect to the proxy server?
Check the PC’s current IPv4 address and make sure the HTTP port on the phone matches the value under Settings → Parameter settings. Then check whether the logs still show listening only on 127.0.0.1 and review the inbound rule for the Windows Private network profile.
Only some pages load on the phone over Wi-Fi?
Test in a browser first, then check whether the specific app uses the system HTTP proxy. If the same destination also fails on the PC, check the current connection and core logs in v2rayN rather than only changing the phone’s Wi-Fi settings.
TV settings are saved, but nothing changes?
Make sure the proxy settings apply to the TV’s current Wi-Fi network, and test with a feature that supports the system proxy. If only certain apps are unaffected, check whether they ignore the system proxy. That alone doesn’t mean the PC’s port isn’t working.
Everything worked yesterday, but no devices can connect today?
Compare the PC’s current IPv4 address with the one saved on each device. If the PC changed networks, got a new LAN address, or switched from a Private to a Public network, check the address and firewall profile again.
Can I set the proxy host to 127.0.0.1?
No. On a phone, 127.0.0.1 points to the phone itself; on a TV, it points to the TV. Other devices must use an address on the LAN that can reach the PC running v2rayN.
When reporting a problem, describe separately whether the PC can use the proxy, whether the device can connect to the PC’s port, and which app is affected. This is more useful than simply saying “the proxy stopped working.” For intermittent disconnects, check whether the PC is sleeping, Wi-Fi has switched networks, or another program is using the proxy port. Sharing depends on the PC staying online. When it shuts down, set the device’s manual proxy option back to None so requests aren’t sent to an unavailable address.