Quick Start

Get up and running with WePROXA in just a few steps.

macOS

1. Launch WePROXA from your Applications folder.

   

2. Start the proxy by clicking the play button in the toolbar or pressing ⌘ + P. WePROXA starts capture and configures the Mac’s system proxy automatically.

   

3. (Optional) Enable remote capture — stop the proxy, click the Remote capture / LAN access device button, then start the proxy again. Leave this off when you only need traffic from this Mac.

4. (Optional) Auto-start on launch — enable Auto-start proxy on launch in Settings → Proxy Config. For remote capture, also enable Auto-enable LAN access on launch in Settings → Remote Access. WePROXA saves these choices and restores them after your settings finish loading on the next launch.

   

5. Install the CA certificate — to inspect HTTPS traffic, go to Settings → CA Certificate and click Install to macOS. This is a one-time setup. See Certificate Trust for details.

6. Enable SSL for a host — click the lock icon in the toolbar and add the hosts you want to inspect (e.g., api.example.com or *.example.com). Alternatively, right-click any request and select Enable SSL. See SSL Interception for details.

7. Browse the web — open your browser or app and make some requests. They’ll appear in the request list in real time.

8. Inspect a request — click on any request in the list to see its full details: headers, body, timing, and more.

Windows

1. Launch WePROXA from the Start menu.

   

2. Start the proxy by clicking the play button in the toolbar or pressing Ctrl + P. WePROXA starts capture and configures the current user’s Windows proxy settings automatically.

   

3. (Optional) Enable remote capture — stop the proxy, click the Remote capture / LAN access device button, then start the proxy again. Leave this off when you only need traffic from this PC.

4. (Optional) Auto-start on launch — enable Auto-start proxy on launch in Settings → Proxy Config. For remote capture, also enable Auto-enable LAN access on launch in Settings → Remote Access. WePROXA saves these choices and restores them after your settings finish loading on the next launch.

5. Review HTTPS certificate trust — HTTPS body inspection on Windows requires a trusted local CA. Open Settings → CA Certificate and click Learn More, or read Windows HTTPS Certificate Setup before deciding whether HTTPS inspection is appropriate for your device.

6. Enable SSL for a host — click the lock icon in the toolbar and add the hosts you want to inspect (e.g., api.example.com or *.example.com). Alternatively, right-click any request and select Enable SSL. See SSL Interception for details.

7. Browse the web — open your browser or app and make some requests. They’ll appear in the request list in real time.

8. Inspect a request — click on any request in the list to see its full details: headers, body, timing, and more.

Find Your Way Around

The main window uses three floating surfaces separated by resize gutters:

• Explorer / Workspaces on the left organizes captured traffic and reusable debugging setups.
• Request List in the center shows live and saved traffic.
• Request Details on the right or bottom shows headers, bodies, timing, and capture-time Scenario attribution.

Drag a gutter to resize adjacent surfaces. The left sidebar keeps the same width and collapsed state when you switch between Explorer, Workspaces, Scenarios, Shared Rules, and the Rule Library.

Settings uses a section list on the left and the selected controls on the right. Use Arrow Up, Arrow Down, Home, and End to move through sections from the keyboard. Main and detached windows remember their last usable size, position, and maximized state.

Auto-start Behavior

Auto-start proxy on launch is the main switch for automatic capture. When Auto-enable LAN access on launch is also enabled, WePROXA enables LAN access first and then starts the proxy on the saved port. The persisted settings are loaded before either action runs, so a cold start uses the same configuration you selected previously.

Terminal Proxy Setup

Most browsers use the system proxy once you enable it in WePROXA. Some terminal tools prefer environment variables, especially inside shells, package managers, or language runtimes.

macOS

In Settings → Proxy Config, click Open Configured Terminal to open a Terminal session with WePROXA proxy variables already set. You can also copy the export commands into your current shell:

export HTTP_PROXY=http://127.0.0.1:4545
export HTTPS_PROXY=http://127.0.0.1:4545
export ALL_PROXY=http://127.0.0.1:4545

Windows

In Settings → Proxy Config, copy the terminal proxy commands for your current port. For PowerShell, set the variables in the shell you want to capture from:

$env:HTTP_PROXY = "http://127.0.0.1:4545"
$env:HTTPS_PROXY = "http://127.0.0.1:4545"
$env:ALL_PROXY = "http://127.0.0.1:4545"

For Command Prompt:

set HTTP_PROXY=http://127.0.0.1:4545
set HTTPS_PROXY=http://127.0.0.1:4545
set ALL_PROXY=http://127.0.0.1:4545

What’s Next?

Now that you’re capturing traffic, explore WePROXA’s powerful features:

• Set breakpoints to intercept and modify requests
• Organize projects with workspaces and package acceptance criteria as Scenarios
• Map local files to replace remote resources
• Repeat requests to test different scenarios
• Use advanced filters to find specific requests