First, make sure your node works on the PC. Then enable LAN listening in v2rayN and set the Android phone, tablet, or TV to use the PC’s local IPv4 address as its HTTP proxy. This guide covers Windows as the host, explains the difference between a mixed port and a separate HTTP port in older versions, and walks through troubleshooting the listener, network, firewall, and app. Use the port shown in your current settings—don’t rely on numbers from a guide.
1. How Proxy Sharing over a LAN Works
This feature makes your PC a proxy endpoint; it does not turn the PC into a router. Connected devices must actively use that endpoint. v2rayN on the PC then routes traffic directly or through the proxy according to its current routing rules. The PC must stay on, the proxy core must be running, and the phone and PC must be able to reach each other.
The “Set system proxy” option on the PC only affects apps that honor the PC’s system proxy settings; it does not configure a proxy on your phone. TUN mode is not required for this setup: a local HTTP or mixed inbound listener can accept proxy requests sent by devices on your LAN.
- Host: A PC running v2rayN with a working node selected and access to the target site through its local proxy.
- Client device: An Android phone, tablet, or TV with manual proxy settings. The device does not need to import a node subscription.
- Network: Prefer a regular home network where both devices connect to the same router. Avoid guest networks, wireless client isolation, and restrictions between VLANs.
2. Enable LAN Access and Check the Actual Port
In v2rayN, open Settings → Parameter Settings, enable “Allow connections from the LAN,” and note the local listening port. Settings groups and port layouts vary by version. After saving, restart the core if prompted. If there’s no prompt, close and reopen the client, then check that it is listening.
Newer configurations may use a mixed inbound that accepts both HTTP and SOCKS, commonly on port 10808. In some older configurations, SOCKS uses 10808 and HTTP uses 10809. The port number alone does not tell you which protocol it supports. If Android’s Wi-Fi settings ask for an HTTP proxy, use the port for an HTTP or mixed inbound—not a SOCKS-only listener.
| Inbound type | How to configure the client device | What to check |
|---|---|---|
| HTTP inbound | Enter its port in the manual Wi-Fi proxy settings | Often 10809 in older versions; use the actual value |
| Mixed inbound | One port can serve HTTP proxy clients and apps that support SOCKS | Often 10808; verify the current core configuration |
| SOCKS-only inbound | Enter it in an app that explicitly supports SOCKS | Not suitable as a Wi-Fi HTTP proxy |
Bottom line: identify the inbound type before entering a port
If your current configuration has one mixed port, use it. Don’t open 10809 just to match an older guide. If you already have a separate HTTP inbound, use its actual port.
3. Find Your PC’s IP and Configure the Phone or TV
In Windows Terminal, run ipconfig and find the IPv4 address under the connected “Wireless LAN adapter WLAN” or “Ethernet adapter.” Don’t use an address from a disconnected adapter, virtual machine, or TUN interface. 192.168.1.20 below is just an example; use the PC’s current address.
ipconfigExample: mixed inbound
- Proxy mode
- Manual HTTP proxy
- Host name
- 192.168.1.20
- Port
- 10808
- Requirement
- 10808 confirmed as a mixed inbound
Enter only the IP address as the host—no http:// prefix or port.
Example: separate HTTP inbound
- Proxy mode
- Manual HTTP proxy
- Host name
- 192.168.1.20
- Port
- 10809
- Requirement
- 10809 confirmed as an HTTP inbound
Use this port only if a listener is actually configured on it.
- On your Android device, open Settings → Network & internet → Internet, then open the details or edit screen for the current Wi-Fi network. Some devices place this option under WLAN.
- Expand Advanced options, set Proxy to Manual, enter the PC’s IPv4 address and the confirmed HTTP or mixed port, then save.
- First, test by opening the target site in a browser. Temporarily turn off mobile data so the request doesn’t go over a different network.
- If your TV has a Network → Current network → Proxy settings menu, enter the address and port there. If the system has no such option and the app offers no proxy settings either, this setup won’t work directly.
On your phone, 127.0.0.1 refers to the phone itself, not the PC. 0.0.0.0 is a wildcard address used for listening, not the destination to enter on a client device. The PC’s address may change when it reconnects to the network. For a stable setup, reserve an address for the PC in your router’s DHCP settings, then verify the address again.
4. Allow Access Through Windows Firewall on Trusted Networks Only
Even with LAN listening enabled, Windows Firewall may block connections from other devices. First make sure you trust your home network. Go to Settings → Network & Internet → the current connection’s properties, then set the network profile to Private. Don’t mark a work, hotel, or public hotspot as trusted just to share a proxy.
- Search for and open Windows Defender Firewall with Advanced Security, then go to Inbound Rules → New Rule.
- Choose Port, select TCP, and enter only the port in use under Specific local ports—for example,
10808for a mixed inbound. - Select Allow the connection, check Private only under profiles, and give the rule a descriptive name.
- Open the rule’s Properties → Scope and limit the remote IP addresses to Local subnet, or narrow them further to the addresses of the devices that need access.
This TCP rule allows HTTP proxy connections as described here; it does not mean that every UDP app can use the proxy. If another firewall or endpoint security tool is installed, check its inbound rules too. Don’t disable all firewalls as a permanent fix.
5. Troubleshoot the Listener, Network, and Proxy Requests
Identify which layer is failing before changing settings. A page loading on the PC only shows that the local path may work; the browser may be connecting directly, so that doesn’t prove the phone can reach the PC’s proxy. The commands below use 10808 as an example. Replace it with the separate HTTP port if that’s what you use.
1. Check the listening address on the host PC
Get-NetTCPConnection -State Listen |
Where-Object { $_.LocalPort -in 10808,10809 } |
Select-Object LocalAddress,LocalPort,OwningProcessIn PowerShell, interpret the results as follows: 127.0.0.1 means listening on local IPv4 only; 0.0.0.0 means listening on all local IPv4 interfaces; a specific LAN address means listening on that interface only. If you see ::, test IPv4 reachability separately; this line alone doesn’t confirm dual-stack behavior. If the port isn’t listed, check whether the core failed to start, the port is in use, or the settings weren’t saved.
2. Test TCP connectivity from another computer on the LAN
Test-NetConnection -ComputerName 192.168.1.20 -Port 10808Run this command on another Windows PC to test the LAN path. TcpTestSucceeded : True means only that the TCP connection was established; it doesn’t confirm that the proxy protocol, node, and destination site are all working. If it returns False, check the PC’s IP, firewall, guest network isolation, and whether the PC is asleep, in that order. A failed ping alone doesn’t prove the proxy is unavailable, since ICMP may be filtered.
3. Send an explicit HTTP proxy request
curl.exe --proxy http://192.168.1.20:10808 --connect-timeout 5 --max-time 20 --head https://example.comRun this command on another Windows PC, replacing the address with the host PC’s actual IP. The URL is the test destination, not a node address. A refused connection usually points to the listener or firewall; a timeout suggests a network path issue. If the connection succeeds but the proxy request fails, check the inbound protocol, selected node, and logs. The HTTP status code reports only the result of this request; it is not a measure of overall connection speed.
- TCP connection fails: troubleshoot the LAN and listener first; don’t keep switching remote nodes.
- TCP connects, but the HTTP proxy request fails: check for a mismatched port protocol and review the core logs.
- Browser works, but one app doesn’t: first check whether the app honors the system HTTP proxy.
6. Common Questions About Sharing a Proxy
Why can’t my phone connect even though it’s on the same Wi-Fi?
Make sure the phone isn’t connected to a guest network, then check the router for AP or client isolation. The PC can use Ethernet while the phone uses Wi-Fi, as long as wired and wireless devices are allowed to communicate. The same network name doesn’t guarantee that devices can reach each other.
Why don’t either 10808 or 10809 work?
Go back to Settings → Parameter Settings to check the actual inbound port, then verify it with a listening command. If it listens only on the local device, reapply the setting that allows LAN connections. If the port has been changed, use the new value instead of trying those two common numbers again.
Why can I open webpages, but video apps on my TV don’t use the proxy?
Check whether the TV app supports the system HTTP proxy. Some apps open their own network connections and ignore system proxy settings. Look for proxy settings in the app itself. If there’s no such option, changing the PC’s system proxy or routing rules won’t automatically route that app’s traffic through the PC.
What should I do if my phone loses its connection after the PC restarts?
Check in order that v2rayN and the core are running, the PC’s IPv4 address hasn’t changed, and the network profile is still Private. Apps that honor the phone’s manual proxy settings may fail to connect when the PC isn’t providing the proxy. When you’re not sharing, set the Wi-Fi proxy back to None.
Does all DNS traffic go through the proxy too?
Not necessarily. An HTTP proxy can receive a destination as a domain name and have the PC resolve it, but an app may resolve names itself or bypass the proxy. First verify a proxy request in a browser, then use the core logs to check the destination and outbound route. A Wi-Fi proxy setting does not route all DNS traffic from the device.
7. Checklist for Regular Use
For everyday sharing, keep the proxy endpoint reliable rather than adding more ways to route traffic. Sleep mode, switching wireless networks, DHCP address changes, and a stopped core can all disconnect devices that depend on the PC. Keep a note of the actual port and PC address; it’s easier to restore access than changing several settings repeatedly.
- Reserve a DHCP address for the PC and make sure client devices use its current LAN address.
- Open only the TCP port you need, and restrict the firewall rule to trusted devices or the local subnet.
- Keep the PC connected to the network and the core running while sharing. Before closing a laptop lid, check whether its power settings will put it to sleep.
- Turn off LAN sharing before connecting to a public network. When you’re finished, clear the manual proxy settings on client devices.
- If an Android device needs its own connection, choose v2rayNG or v2flyNG based on the core you need. They use Xray and v2fly cores respectively, and don’t depend on the PC as a local proxy endpoint.