WPE PROXY CAP
WPC is a proxy client, with a Windows version and an Android version, built to work with WPE x64 Proxy Mode. The forwarding rules are pushed by WPE, so the client only needs one-click subscribe to route a PC's or phone's traffic to the WPE proxy server — no hand-written proxy rules. Once connected it shows live status and throughput. Subscription IDs are issued by the subscription server (see Where subscription IDs come from).
Features
Traffic is forwarded according to the rules you set for each node in WPE x64 — only what needs accelerating goes through the proxy. The client fetches the rules itself; nothing to configure by hand.
Enter a subscription ID and the client gets the proxy server address from the subscription server, then pulls the nodes and forwarding rules from your WPE x64. No manual entry.
Connecting to a proxy server requires a username and password, with live feedback — Checking / Passed / Failed.
Once connected, uplink and downlink speed, latency and session time are shown in real time.
Session timer with pause and resume, a healthy-usage reminder and a daily total — the whole connection state on one screen.
The home screen lists the latest notices and events by category, title and date.
- Clean disconnect: on Windows, closing the window stops the acceleration core and disconnects — there is no background mode; if the core crashes, or the link to the server drops, the client marks itself disconnected automatically. The Android version can keep the connection in the background — see Android version.
- Remember me: tick it once and the next launch skips the credentials.
- Device identity: when it connects, the client registers this PC as one online device, which you can see in WPE x64's client list (shown as the client version and the OS); one account's device limit counts PCs and phones together.
- Clean UI: on Windows, a borderless window with System Log, Preferences, Always on top and Minimize / Maximize / Exit in the title bar; the subscription server's status sits in the SUBSCRIPTION bay on the right. The Android version keeps the same look but is laid out for phones: four tabs at the bottom (Boost / Nodes / Inbox / Me), turning into a side rail on tablets.
A proxy client for Windows and Android, built specifically for WPE x64 Proxy Mode. One-click subscribe gets the proxy server address, then pulls the nodes and forwarding rules from WPE x64, so setups like game traffic acceleration need no manual configuration.
Getting started
Three steps, together with WPE x64 Proxy Mode:
Turn on Proxy Mode in WPE x64, then configure the rules it will push out.
Open the client and enter the subscription ID issued by the subscription server; the client gets the server address and pulls the nodes and rules from WPE x64.
Pick a server, enter the account credentials and connect.
- After connecting, the Control Center takes over: the telemetry bay on the left shows upload and download speed sparklines and memory live, while the centre shows the latency and the timer core with the session time.
- Tick "Remember me" to skip the credentials next time.
- On Windows, closing the window stops the acceleration core and disconnects; there is no background mode. On Android, the Back button only sends the app to the background and the connection keeps running.
The Windows version needs administrator rights (it asks through UAC when you double-click it); the Android version asks you to allow Android's VPN connection request on the first connection. The proxy server must already be configured on the WPE x64 Proxy Mode side.
The subscription ID in step ② has to be requested from the subscription server — you cannot create one yourself. See Where subscription IDs come from.
For the full checklist of what to turn on in WPE and how to set up nodes, see Proxy Mode · bringing in devices with WPC.
Where subscription IDs come from
WPC never asks you to type a server address. It works off a subscription ID — not a name you pick, but a record on the subscription server that binds that ID to the public address of your WPE x64 proxy server, with an expiry date attached.
- Get the server running: in WPE x64, set up the SOCKS5 service and proxy accounts under Proxy Mode, and enable Remote MGT — that is the port the client pulls nodes from.
- Decide what to push: fill in the server list, forwarding rules and notices under WPC Config.
- Request a subscription ID: submit your server's public IP and the Remote MGT port of WPE x64 (88 by default — not the SOCKS5 port); a record is created on the subscription server and the ID is sent back to you.
- Subscribe in WPC: enter the ID and the client resolves the address, then pulls nodes, rules and notices.
The ID registry lives on the subscription server alone — neither the client nor WPE x64 can create one. To let others reach your WPE server with one-click subscribe, you have to request an ID first.
Ask via GitHub Issue, or QQ group 1121552990.
Notices in WPC come from two places. Global notices are pushed by the subscription server; server notices come from your own WPE, under WPC Config → Notice List. You cannot change the first, and you fully control the second.
Android version
WPC for Android latest is WPC's Android client. Enter a subscription ID, choose a node and supply the account credentials; Android's system VPN sends phone traffic to in-process mihomo, which follows the node rules and forwards applicable traffic over SOCKS5 to WPE x64 for capture, editing and filters. The ARM64 package is — and is available from Downloads.
| Item | Requirement |
|---|---|
| System | Android 8.0 or later on an ARM 64-bit (arm64) phone |
| WebView | Android System WebView 90 or later |
| Root | Not required |
| License | GPL-3.0; source code on GitHub |
- System VPN: traffic is taken over through Android's system VPN — no administrator rights and no virtual network adapter to install; the app itself never goes through the proxy.
- Per-app proxy: choose "All apps use the proxy" or "Only selected apps", with support for manually adding package names; selected apps are listed first and changes take effect on the next connection (the entry point only appears while disconnected).
- Background running: the Back button only sends the app to the background and the connection keeps running; while connected, a persistent notification offers a Disconnect button; Android's Always-on VPN is supported.
- Automatic re-registration: if a network switch or a brief system freeze breaks the control link, the app quietly re-registers and hot-swaps the token and kernel configuration without rebuilding the VPN tunnel; it disconnects only after retries fail or the account is rejected.
- Rule protection: unsupported, malformed and phone-inapplicable rules are screened first, then the kernel validates rules one by one. Skipped rules are written to the System Log instead of breaking the whole configuration; use per-app proxy instead of
PROCESS-NAME/PROCESS-PATH. - Devices: the phone and the PC count as separate devices against the account's device limit.
Tutorial
The illustrated WPC tutorials live on the Tutorial page, under the WPC tab with Windows and Android sub-tabs: Windows (install, subscription ID, connecting, Control Center, security check, System Log, preferences, troubleshooting) and Android (install and permissions, subscription and account, connecting, per-app proxy, background running and reconnection, after connecting and the Me tab, rules and DNS, troubleshooting).
Download
WPC downloads and its changelog sit next to WPE x64 on the Downloads page. Windows version: v— (—). Android release: v— for ARM 64-bit phones on Android 8.0 or later (—).