Clash Verge Rev normally exposes its proxy to the Windows computer running the client. To let a phone, tablet, or another computer use that proxy, the client must accept connections from the local network, the Windows firewall must allow those connections, and the other device must point to the Windows computer’s LAN address and the correct proxy port. Enabling only the Windows system proxy is not enough: that setting configures applications on Windows, but does not automatically make the proxy reachable from other devices.

This setup is intended for devices on a trusted home or office network. It does not create a public proxy service, and it should not be used to expose a proxy port to the internet. The exact labels and default port can vary between Clash Verge Rev releases and configurations, so verify the running settings rather than assuming a particular port number.

How to Enable LAN Proxy Sharing in Clash Verge Rev on Windows

Understand the requirements for LAN sharing

A client device sends its proxy request to a listening port on the Windows computer. Clash Verge Rev passes the request to its Mihomo core, which applies the active configuration’s rules and proxy groups. The Windows computer therefore acts as the proxy host, while the phone or second computer is a proxy client. Both devices need a usable network path to each other; being connected to the same Wi-Fi name does not always guarantee that the router permits communication between them.

Three settings or conditions must line up:

For most everyday use, a mixed-port is convenient because it can accept both HTTP proxy and SOCKS5 requests on one port. If the active configuration instead defines separate port and socks-port values, choose the matching proxy type and its corresponding port on the client device. Do not confuse the proxy listener with the external controller. The controller is used to manage the core, not to proxy ordinary web traffic.

Value or setting Purpose What to use for a phone or second PC
mixed-port Accepts HTTP and SOCKS proxy connections on one listener. Usually the simplest choice; select HTTP or SOCKS5 as supported by the device.
port HTTP proxy listener. Choose HTTP and enter this port.
socks-port SOCKS proxy listener. Choose SOCKS5 and enter this port.
external-controller Management API used by the client or compatible tools. Do not enter this as the proxy port or expose it for ordinary proxy use.

Enable LAN access and find the active port

Start Clash Verge Rev and confirm that a configuration is loaded and the core is running. Look in the application’s settings for the Clash or Mihomo settings section and find the LAN access control, which may be labelled Allow LAN. Turn it on, apply or save the setting if required, and check whether the client restarts or reloads the core. Menu names can differ by release; if the control is not visible, inspect the active configuration and the client’s configuration or override controls instead of editing a generated subscription file directly.

In a YAML configuration, LAN access is commonly represented by allow-lan. A wildcard bind address allows the listener to bind to available network interfaces, while 127.0.0.1 restricts it to the local computer. The following is an example of the relevant structure, not a complete configuration to paste over an existing profile:

mixed-port: 7897
allow-lan: true
bind-address: "*"

The value 7897 is only an example. Use the port shown in Clash Verge Rev’s current port settings or active configuration. If a port is changed, make sure the core reloads the configuration and that no other application has already claimed that port. A saved YAML value is not proof that the core successfully started a listener on it.

Next, identify the Windows computer’s IPv4 address on the network the other device will use. Open Command Prompt and run:

ipconfig

Under the connected Wi-Fi or Ethernet adapter, note the IPv4 address, such as 192.168.1.24. Do not use the default gateway address: that belongs to the router. Also avoid copying an address from a disconnected adapter, a virtual machine, or a VPN interface. If Windows has both Wi-Fi and Ethernet active, use the address associated with the same local network as the phone or tablet. The host address may change after reconnecting or restarting the router, so check it again if the connection later stops working.

Configure and test from another device

Complete these steps after enabling LAN access and noting the active proxy port. Keep Clash Verge Rev running during the test, and initially test with a simple website or application that supports a manual proxy setting.

  1. Confirm both devices are on the same local network. Connect the phone or second computer to the same non-guest Wi-Fi network as the Windows host, or connect both through the same trusted LAN. If one device uses a guest SSID, mobile hotspot, or isolated VLAN, the router may intentionally prevent device-to-device connections.
  2. Open the proxy settings on the client device. On a phone, this is often part of the Wi-Fi network’s advanced or manual proxy settings. On another computer, use the operating system’s proxy configuration or an application-specific proxy option. The exact menu depends on the operating system and application.
  3. Enter the Windows host’s IPv4 address. Use the address from ipconfig, not localhost, 127.0.0.1, or the router’s gateway address. Those loopback and gateway addresses do not identify the Clash Verge Rev listener on the Windows host.
  4. Choose a matching proxy type and port. For a mixed-port, select HTTP or SOCKS5 according to what the device supports. For separate listeners, pair HTTP with port and SOCKS5 with socks-port. Enter the exact active port number.
  5. Save the setting and make a fresh request. Open a new page or restart the test application so it does not reuse an existing connection. Check Clash Verge Rev’s connection list or logs for the new request and confirm which rule and proxy group handled it.

For example, if the Windows address is 192.168.1.24 and the active mixed-port is 7897, the client device should be configured with host 192.168.1.24 and port 7897. That example does not imply that every Clash Verge Rev installation uses either value. If the connection appears in the client’s log but the website fails, the LAN path is probably working; investigate the selected proxy group, DNS behavior, rule match, or upstream node next.

When testing with a second Windows computer, PowerShell can check whether the host’s TCP port is reachable:

Test-NetConnection 192.168.1.24 -Port 7897

Replace both example values with the host address and actual listener port. A result with TcpTestSucceeded : True confirms that a TCP connection can reach that port from the second computer. It does not prove that the proxy type is configured correctly, that the selected node works, or that every destination is allowed by the active rules. A failed TCP test points first to the listener, firewall, address, or network isolation rather than to a particular proxy node.

Allow the listener through Windows Firewall

If the settings appear correct but another device cannot connect, Windows Defender Firewall is a common cause. When Windows first asks whether an application may communicate on a network, allowing it only on a trusted Private network is generally more appropriate than allowing it on every network type. The process that opens the proxy port may be the bundled Mihomo core rather than the visible Clash Verge Rev window, so approving only the GUI does not always permit the core’s inbound listener.

First check the active Windows network profile. Open Settings > Network & internet, select the connected Wi-Fi or Ethernet network, and confirm that its profile is set to Private only if it is a trusted network. Do not mark a public network as private merely to bypass a firewall block. Then review the firewall notification or the allowed-app list in Windows Security. If the core executable is listed, allow it on the trusted Private profile; avoid enabling access on Public networks unless there is a specific, justified need.

If the application is not listed, create a narrowly scoped inbound rule for the actual proxy port and the appropriate network profile, or use the supported Windows firewall prompt when the core starts. The Windows Defender Firewall with Advanced Security console provides inbound rules where a TCP local port can be specified. Use the real listener port, select Private as the applicable profile when suitable, and give the rule a clear name so it can be identified and removed later. A broad rule that allows every port or every profile is harder to audit and increases exposure.

Do not open a UDP port unless the setup specifically requires one. A standard HTTP or SOCKS proxy connection is established over TCP; enabling a random UDP rule will not fix a blocked TCP listener. If the client uses an additional feature that requires UDP, determine that requirement from the active configuration and feature documentation instead of assuming it from the proxy port alone.

After adjusting the firewall, repeat the connection test from the other device. If the test begins succeeding, inspect the Clash connection log to verify that traffic reaches the intended profile and rule set. If Windows displays more than one rule for different copies or locations of the core, remove obsolete entries once the current installation is confirmed. Firewall rules tied to a deleted executable can make later troubleshooting confusing, while an overly broad replacement rule can leave unnecessary access open.

Troubleshoot common LAN sharing failures

Use the order below to isolate the failing layer. Changing the proxy node repeatedly is not a useful first step when the remote device cannot establish a TCP connection to the Windows listener.

Symptom Likely cause Next check
The host works, but the phone cannot connect. LAN access is disabled, the listener is bound to loopback, or the firewall blocks inbound traffic. Confirm allow-lan, the bind address, the actual port, and the Private-profile firewall rule.
The port test fails from another PC. Wrong host address or port, stopped core, firewall block, or client isolation. Check ipconfig, verify the core is running, and test both devices on a non-guest network.
The port test succeeds, but browsing fails. Wrong HTTP/SOCKS selection, proxy authentication expectation, routing rule, DNS issue, or unavailable node. Match the proxy type to the listener and inspect the connection log and selected proxy group.
It works briefly, then stops after reconnecting. The Windows host received a different DHCP address. Run ipconfig again and update the client device’s proxy host field.
It works on home Wi-Fi but not on guest Wi-Fi. The access point isolates clients by design. Use a trusted network that permits local device communication; do not disable isolation on a network you do not manage.

Also check for more than one network interface or proxy program on Windows. A VPN, virtual machine adapter, mobile hotspot, or second proxy client can change which address is reachable or can claim a port first. In Clash Verge Rev, verify that the currently selected profile is loaded and that the core has not reported a port-in-use error. If the port is occupied, choose a free listener port and update both the firewall rule and the remote device’s proxy settings to match.

Some phones apply a manual proxy only to the selected Wi-Fi network, not to mobile data or every application. A browser may honor the Wi-Fi proxy while another app ignores it. Test with an application known to use the device’s proxy setting, and check the Clash connection log rather than relying only on whether a page loads. If no request appears in the log, the traffic has not reached this Clash instance; if it does appear, investigate its matched rule, DNS result, and selected outbound group.

When troubleshooting, temporarily changing one variable at a time makes the result easier to interpret. First confirm local host proxy operation, then remote TCP reachability, then proxy protocol and port, and finally rule and node behavior. Restore any temporary firewall or network changes afterward. When finished sharing, turn off LAN access if it is no longer needed, or keep it limited to a trusted network with a specific firewall rule.

Download Clash