Verify the exit in the same application that will run the task.
Verify the exit IP in the right application
A system browser, an automated browser and a script can have separate connection settings. Testing one does not validate the others.
Record the application, proxy settings with secrets removed, observed exit IP, detected country and time. Then visit a small target page through the same application. If the result differs, investigate routing and bypass rules supported by that tool.
Record the connection details
- Application name and version, plus the workspace or profile being tested.
- Proxy product, host and protocol; omit passwords and authentication tokens from shared notes.
- Observed exit IP, reported region and the time of the check.
- A representative target URL and the result returned by that same application.
Find the first point of failure
| Result | Next check |
|---|---|
| Proxy authentication fails | Confirm the proxy username and password, resource status and any required authorisation. |
| Connection times out | Check the host, port, supported protocol and network reachability. |
| IP lookup works, target fails | Inspect the target response. Rendering, access conditions and extraction are separate from proxy connectivity. |
| Region differs | Compare the IP lookup result with the website’s own account, cookie and region settings. |
Repeat after a change
Recheck after changing the proxy, updating the tool or moving the task to another environment. Testing your desktop browser does not confirm the connection used by a cloud browser or an agent’s separate HTTP client.
When asking for help, include the timestamp, tool version, redacted error and steps already tried. These details help support work out whether the problem is with routing or the target page.