Skip to main content
First generate a live connection. Under Ready to connect, open Connection details and click Reveal credentials. Then open Code examples and choose your tool’s tab to view and copy the complete example. Generated examples may use the website you entered during onboarding. Check the destination before running an example.

​
Browser

Open your browser or application’s proxy settings. Enter Host, Port, Username and Password from Connection details in their separate fields. Copy the Host without the protocol or port. If the application accepts a single proxy URL instead, use Copy connection. Save or apply the settings in that tool before testing. Opening the ProxyLane dashboard alone does not route browser traffic through a proxy.

​
Python and cURL

Open Code examples and select Python or cURL. The generated example includes the connection and destination. For Python, follow the install note for requests, including SOCKS support when selected. Run the example in your own environment and inspect the response. Keep the credentials in your private environment; do not commit the copied example to a shared repository.

​
Playwright

Select HTTP / HTTPS under Advanced settings and regenerate the connection. Open Code examples, then Playwright. The example passes the proxy server, username and password separately to the browser. Use those values together. Check the destination in the example and inspect the page response after running it.

​
n8n

Open Code examples, then n8n. Use an HTTP Request node with the shown method and URL, and set its Proxy option to the generated proxy URL. Keep the credentials private when sharing or exporting a workflow. Run the node once and inspect its output before adding it to a larger workflow.

​
Confirm your tool is using the proxy

First request https://api.ipify.org?format=json with the proxy turned off and note the ip value. Enable the proxy and repeat the request. A different IP is a useful check that your route changed. If both values match, recheck whether your tool applied its proxy settings; a successful JSON response alone does not prove proxy use. Then test your intended website through the same setup. The dashboard’s Test connection runs from ProxyLane, so it cannot verify the settings inside your local tool. If that check passes but your tool fails, compare its protocol and all four connection fields with the latest generated result. Treat copied examples and connection URLs as secrets. Keep credentials out of shared workflows, screenshots and source repositories. If you get stuck, email support with the tool name, version and error text. Use troubleshooting to narrow down the failing step first.