WPE PROXY CAP
WPC is a Windows proxy client 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 this machine'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 pushed by the subscription server — only what needs accelerating goes through the proxy. Nothing to configure by hand.
Enter a subscription ID and the client pulls the matching proxy servers and forwarding rules from the subscription server. 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.
- Keeps running in the background: hiding the window does not drop the proxy — existing connections stay up. Only quitting disconnects.
- Remember me: tick it once and the next launch skips the credentials.
- Clean UI: a borderless window whose title bar shows subscription-server status and the current time.
A Windows proxy client built specifically for WPE x64 Proxy Mode. One-click subscribe fetches the proxy servers and forwarding rules from the subscription server, 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 to pull the servers and rules.
Pick a server, enter the account credentials and connect.
- After connecting, the control center shows uplink / downlink speed, latency and session time live.
- Tick "Remember me" to skip the credentials next time.
- Hiding the window keeps the proxy running; only quitting disconnects.
Run it as administrator the first time. 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.
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 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.
Changelog
WPC ships on its own release cycle, so its versions are tracked here. For the main program see Downloads.
Release Pending
The first public build is being packaged and tested; downloads are not open yet. Once it ships, this block becomes a normal release card and changelog, with the download links published at the same time.
WPC connects to your own WPE x64 proxy server. Get the SOCKS5 service and accounts ready under Proxy Mode, then prepare the nodes and notices in WPC Config — so the client can connect the day it lands.