Which BrowserStack Local Proxy Flags Belong to Which Connection?
The Local binary's connection to BrowserStack and its connection to an application can require different proxies. Choose flags for the path that needs them.
Start from the machine running the BrowserStack Local binary. It makes two connections that can require different proxy settings:
| Connection | Option family | Documented default port |
|---|---|---|
| The binary reaching BrowserStack from behind a corporate proxy | --proxy-host / --proxy-port | 3128 |
| The binary reaching a local application through its proxy or intended recording intermediary | --local-proxy-host / --local-proxy-port | 8081 |
Choose either path or both according to the failure. The remote browser's location does not tell you how the binary reaches either destination. Use the actual listener ports instead of relying on the two different defaults. A loopback listener also belongs to the binary's machine; a proxy on your workstation is not automatically reachable from a build agent.
Attach each account to its hop. The proxy username and password are separate from the BrowserStack access key and application login. The corporate account options document HTTP Basic; integrated sign-in working in a desktop browser does not establish that the Local binary supports the same exchange. Check the installed binary's authentication capabilities and PAC limitations for the selected mode.
If the expected proxy log is empty, inspect the product's flags governing whether the relevant traffic is forced through the local or proxy route. Providing an endpoint and requiring its use are separate decisions.
Keep the failed path, binary location, selected endpoint and first error together. Redact verbose logs before sharing them; they can contain application requests, responses and private addresses.