Productivity browser with isolated sessions per tab or workspace. Use KnoxProxy with Ghost Browser to assign different proxy identities to each workspace for multi-account workflows without full antidetect overhead.
Launch Ghost Browser from your applications.
Click the "+" button to create a new isolated workspace (or use an existing one).
Right-click the workspace tab and select "Proxy Settings" (or go to Settings > Proxies).
Click "Add Proxy" and select HTTP or SOCKS5 as the protocol.
Input the KnoxProxy gateway information.
Host: gw.knoxproxy.com
Port: 7000 (HTTP) or 7001 (SOCKS5)
Username: your_username-country-us
Password: your_passwordAssign the proxy to the workspace. Open a site like httpbin.org/ip to confirm the proxy IP is active.
{
"proxy": {
"protocol": "HTTP",
"host": "gw.knoxproxy.com",
"port": 7000,
"username": "your_username-country-us",
"password": "your_password"
},
"workspace": "US Account"
}Use -session-{workspaceName} for consistent IPs per workspace. Omit the session parameter to get a fresh IP each time.
| Problem | Fix |
|---|---|
| Proxy not applying to workspace | Right-click the workspace tab and verify the proxy assignment. Re-assign if needed. |
| Authentication popup appears | Re-enter username and password in the proxy settings. Ensure no special characters are URL-encoded incorrectly. |
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.
Not exactly. Ghost Browser isolates cookies and sessions per workspace but does not spoof browser fingerprints the way dedicated antidetect tools like Octo Browser or Lalicat do. It works well for lightweight multi-account use, such as social media management, where a fresh KnoxProxy IP per workspace is enough separation.
Yes. Create a separate proxy entry for each workspace with -country-{cc} in the username, for example your_username-country-us for one workspace and your_username-country-de for another, then assign each entry through the workspace's Proxy Settings. Every workspace keeps its own KnoxProxy exit country alongside its isolated cookies and sessions.
Yes. When adding the KnoxProxy proxy entry to a workspace, choose SOCKS5 as the protocol instead of HTTP and set the port to 7001 rather than 7000. Enter the same KnoxProxy username and password you would use for HTTP, then assign the entry and verify it on a site like httpbin.org/ip.
Yes. Each workspace keeps its own cookies and session state, so you can log into multiple social accounts simultaneously without cross-contaminating logins, and each workspace can carry a different KnoxProxy IP through its own proxy entry. This gives lightweight per-account isolation without the overhead of a full antidetect browser.
Rotating residential proxies -- 2 minutes setup, instant activation, 14-day money-back guarantee.