HTTP debugging proxy for developers and QA engineers. Route Charles Proxy through KnoxProxy as an upstream proxy to inspect and debug traffic while using real residential IPs from any target country.
Launch Charles Proxy. It starts recording traffic automatically.
Go to Proxy > External Proxy Settings from the menu bar.
Check "Use external proxy servers" and check "Web Proxy (HTTP)".
Fill in the upstream proxy fields for HTTP.
Web Proxy Server: gw.knoxproxy.com
Port: 7000
Proxy Authentication: checked
Username: your_username-country-us
Password: your_passwordCheck "Secure Web Proxy (HTTPS)" and enter the same KnoxProxy details.
Secure Proxy Server: gw.knoxproxy.com
Port: 7000
Username: your_username-country-us
Password: your_passwordOpen a browser configured to use Charles (localhost:8888) and visit httpbin.org/ip. Verify the IP matches your KnoxProxy target country in Charles traffic view.
{
"externalProxy": {
"http": {
"host": "gw.knoxproxy.com",
"port": 7000,
"username": "your_username-country-us",
"password": "your_password"
},
"https": {
"host": "gw.knoxproxy.com",
"port": 7000,
"username": "your_username-country-us",
"password": "your_password"
},
"bypassDomains": [
"localhost",
"127.0.0.1"
]
}
}Add -session-{debugSession} to the username for a consistent IP during a debugging session. Remove the session flag to rotate IPs between requests.
| Problem | Fix |
|---|---|
| HTTPS sites show certificate errors | Go to Help > SSL Proxying > Install Charles Root Certificate and trust it in your OS certificate store. |
| No traffic appears in Charles | Set your browser proxy to localhost:8888 or enable macOS/Windows proxy in Charles (Proxy > macOS Proxy / Windows Proxy). |
| External proxy connection fails | Verify gw.knoxproxy.com:7000 with correct username and password in Proxy > External Proxy Settings. |
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. Install the Charles Root Certificate from Help > SSL Proxying and trust it in your OS certificate store, enable SSL Proxying for your target domains, then set KnoxProxy as the external proxy for both HTTP and HTTPS. You get full request and response inspection while your traffic still exits through KnoxProxy's geo-targeted IP.
Minimal. Charles intercepts traffic locally on your machine, while KnoxProxy handles the actual upstream connection to the target server as the external proxy. Total added overhead is typically under 20ms, so debugging sessions still feel responsive even with SSL Proxying enabled and requests routed through a geo-targeted KnoxProxy exit IP.
Yes. Point your mobile device's Wi-Fi proxy settings to the machine running Charles, the same way a browser would use localhost:8888. Traffic flows from device to Charles, then to KnoxProxy as the external upstream proxy, and finally out to the internet. Install the Charles Root Certificate on the device too for HTTPS traffic.
Yes. Open Proxy > External Proxy Settings and change the username's -country-{cc} suffix for both the HTTP and HTTPS proxy fields, then restart Charles to apply it. If you are mid debugging session, add a -session-{debugSession} flag first to keep results consistent before switching to a new country IP.
Rotating residential proxies -- 5 minutes setup, instant activation, 14-day money-back guarantee.