Frequently Asked Questions
General
Section titled “General”What is WePROXA?
Section titled “What is WePROXA?”WePROXA is a native macOS and Windows HTTP/HTTPS proxy debugger. It lets you capture, inspect, modify, and replay network traffic from apps on your computer.
What platforms does WePROXA support?
Section titled “What platforms does WePROXA support?”Starting with WePROXA 3.0.0, WePROXA supports macOS 11.0+ (Big Sur and later) on Apple Silicon and Intel Macs, plus Windows 10 and Windows 11. The Windows build is installed from the Microsoft Store.
Is WePROXA free?
Section titled “Is WePROXA free?”WePROXA offers a free tier with core features. Advanced features are available with a Pro license. See Pricing for details.
What license details does WePROXA show?
Section titled “What license details does WePROXA show?”When a Pro license is active, Settings → License shows the details returned when the key was validated: the subscription (product and variant), the expiration date and time (or a note when none is scheduled), the customer email on the license, the activation usage (seats used out of the limit, or an unlimited indicator), and when the license was last validated. Use Revalidate to refresh these details against the license server, or Deactivate to release the activation on this machine.
Setup & Configuration
Section titled “Setup & Configuration”Why does WePROXA need a certificate for HTTPS inspection?
Section titled “Why does WePROXA need a certificate for HTTPS inspection?”To inspect HTTPS (encrypted) traffic, WePROXA needs a trusted local Certificate Authority. This is standard practice for proxy debugging tools. The certificate is generated locally and never leaves your machine. On macOS, see Certificate Trust. On Windows, see Windows HTTPS Certificate Setup.
How do I enable the system proxy?
Section titled “How do I enable the system proxy?”Click the play button in the toolbar or press ⌘ P on macOS / Ctrl + P on Windows. WePROXA configures the system proxy automatically when capture starts and restores the previous settings when capture stops or the app exits normally. The separate device button controls LAN access for remote capture.
Does WePROXA work with all apps?
Section titled “Does WePROXA work with all apps?”Most apps that respect macOS or Windows system proxy settings will work automatically. Some apps (like those using custom proxy configurations or certificate pinning) may need additional setup.
Can I activate my license or open settings from a link?
Section titled “Can I activate my license or open settings from a link?”Yes. WePROXA registers the weproxa:// URL scheme. Opening a weproxa:// link — for example from your browser after a purchase — can activate a license key or jump straight to a Settings section without hunting through the app. If activation from a link fails, WePROXA opens the License settings so you can see the error and retry. For example, weproxa://settings/certificate opens the CA Certificate settings. See Deep Links for every link format and section name.
HTTPS & Security
Section titled “HTTPS & Security”Is my data safe?
Section titled “Is my data safe?”Yes. WePROXA runs entirely on your local machine. No traffic data is ever sent to external servers. The CA certificate and private key are stored locally in the app’s data directory.
Can WePROXA decrypt HTTPS traffic?
Section titled “Can WePROXA decrypt HTTPS traffic?”Yes, when the WePROXA CA certificate is trusted. This is a standard man-in-the-middle (MITM) technique used by all proxy debugging tools.
What about certificate pinning?
Section titled “What about certificate pinning?”Apps with certificate pinning will reject WePROXA’s generated certificates. This is by design — it’s a security feature of those apps.
Troubleshooting
Section titled “Troubleshooting”I don’t see any requests
Section titled “I don’t see any requests”- Make sure the proxy is running (green indicator in toolbar)
- Check that the system proxy is enabled
- Try opening a website in a browser that uses system proxy settings, such as Safari on macOS or Edge/Chrome on Windows
- If one app is missing while other apps still show up, see Why does an app refuse the WePROXA certificate?
HTTPS requests show certificate errors
Section titled “HTTPS requests show certificate errors”The WePROXA CA certificate may not be trusted. On macOS, see Certificate Trust. On Windows, see Windows HTTPS Certificate Setup.
Why does an app refuse the WePROXA certificate?
Section titled “Why does an app refuse the WePROXA certificate?”When SSL decryption is on for an app or a host, WePROXA shows the app its own certificate instead of the website’s. If the device does not trust the WePROXA certificate, the app refuses to connect. WePROXA can’t see anything the app sends, so the app’s requests are missing from the list while other apps still show up.
The request list shows a failed entry for each detected refusal. It carries the host, the client name when available, and the label Not decrypted: certificate rejected. Open its response pane for an explanation and a Learn more link to this page. These entries stay in the traffic log without raising a notification.
To fix it, do one of these:
- Install and trust the WePROXA certificate on the device that runs the app. Each simulator, emulator, phone, and tablet needs its own copy. See iOS Simulator, Android Emulator, and Remote Devices. If you regenerated the certificate, install the new one too.
- Turn off SSL decryption for that app or host if you don’t need to see its HTTPS traffic. The app then connects normally, and WePROXA shows the connection as a tunnel.
If the certificate is installed and trusted and the app still refuses it, the app probably uses certificate pinning. See What about certificate pinning?
WePROXA counts a connection as rejected when the app says it doesn’t trust the certificate, or when the app closes the connection right after receiving the certificate. iOS and macOS apps reject a certificate the second way. A connection that closes before WePROXA sent its certificate isn’t counted. WePROXA also doesn’t add an entry when the website’s own certificate is the problem, for example when it is expired, self-signed, or issued for another name. WePROXA passes that problem on to the app on purpose, so the app refuses it just as it would without WePROXA.
An app that quits while it is still connecting can close the connection the same way, so a silent close alone cannot prove that the certificate was refused. The response pane describes both possibilities. After that client successfully trusts WePROXA’s certificate for the same host during the current run, later silent closes for that pair are ignored; an explicit certificate rejection is still recorded. Regenerating the CA or restarting WePROXA resets that history.
The app is slow with many requests
Section titled “The app is slow with many requests”WePROXA keeps up to 10,000 requests in memory. Use the Clear button in the toolbar to remove old requests, or use filters to focus on relevant traffic. Save or record a Session to keep a run after the live log is cleared or old entries are evicted.