Modern macOS HTTP debugging proxy with a native interface and upstream proxy support. Connect Proxyman to KnoxProxy to inspect API calls and web traffic while routing through geo-targeted residential IPs.
Launch Proxyman from your Applications folder.
Go to Proxyman > Settings > Tools tab > External Proxy.
Check "HTTP Proxy" and enter the KnoxProxy gateway details.
Host: gw.knoxproxy.com
Port: 7000Check "Authentication Required" and enter your KnoxProxy credentials.
Username: your_username-country-us
Password: your_passwordCheck "HTTPS Proxy" and enter the same KnoxProxy details as the HTTP proxy.
Open Safari or Chrome and visit httpbin.org/ip. Check the Proxyman traffic log to confirm requests route through KnoxProxy with the correct IP.
{
"externalProxy": {
"httpEnabled": true,
"httpsEnabled": true,
"host": "gw.knoxproxy.com",
"port": 7000,
"authRequired": true,
"username": "your_username-country-us",
"password": "your_password",
"bypassDomains": [
"localhost",
"*.local"
]
}
}Use -session-{id} in the username for a sticky IP during your debugging session. Remove the session flag to get a new IP on each connection.
| Problem | Fix |
|---|---|
| No traffic captured after enabling external proxy | Click the "Enable macOS Proxy" toggle in the Proxyman toolbar to route system traffic through Proxyman. |
| SSL certificate errors on HTTPS sites | Go to Certificate > Install Certificate on this Mac and follow the prompts to trust the Proxyman CA in Keychain Access. |
USER-country-de-city-berlin-session-profile07Order matters -- geo flags before the session flag. The session name is free text; use the profile ID so the mapping is self-documenting. Password stays as issued; no flags belong there. HTTP on :7000, SOCKS5 on :7001, same credentials.
Yes. Proxyman intercepts traffic locally, then forwards every request to KnoxProxy as its configured external upstream proxy on gw.knoxproxy.com port 7000. You still see full request and response details in the Proxyman traffic log, while the actual connection to the target site exits through a KnoxProxy residential IP.
Yes. Install the Proxyman certificate on your iOS device to trust HTTPS interception, then set the device's Wi-Fi proxy to your Mac's IP address. Proxyman captures the traffic locally and forwards it to KnoxProxy as the external upstream proxy already configured under Settings > Tools > External Proxy, so requests exit through a residential IP.
The desktop app is macOS-only, since Proxyman's prerequisites require macOS to run. On Windows or Linux, use Charles Proxy instead: it supports the exact same KnoxProxy upstream setup, with gw.knoxproxy.com on port 7000 and country-targeted credentials entered in External Proxy Settings, plus the same sticky-session flag for consistent debugging IPs.
Yes. Proxyman's external proxy configuration includes a bypass domains list, so add localhost and *.local to it under Settings > Tools > External Proxy. Requests to those domains skip KnoxProxy entirely and connect directly, while everything else still routes through the upstream proxy for geo-targeted testing.
Rotating residential proxies -- 3 minutes setup, instant activation, 14-day money-back guarantee.