This guide shows the fastest path from account access to a verified working InstantProxies connection.
It is written for developers, scraping engineers, automation engineers, and technical operators who want a clean working baseline before moving into language integrations, browser automation, troubleshooting, reliability, or security topics.
If you follow the steps in order, you should finish with a confirmed proxied request, a verified outbound proxy IP, and a clear next step for your workflow.
What You Will Do
By the end of this guide, you should be able to:
- access your assigned proxy details
- choose the correct authentication method for your environment
- send a proxied request through one InstantProxies endpoint
- verify that the request is routing through the proxy path correctly
- choose the right next step for your code, browser, or automation workflow
Before You Start
Make sure you have:
- an active InstantProxies account or order
- access to the InstantProxies client area and control panel
- one assigned proxy IP and port
- a terminal or command prompt
- cURL installed
If you plan to use IP whitelisting, also make sure you know the current public IP address of the machine or server that will actually send the request.
If you are testing from a server, cloud VM, CI runner, container host, or remote desktop environment, use the public IP of that environment rather than the IP of your personal laptop.
Understand the Access Model First
InstantProxies supports both:
- IP whitelisting or authorization
- username and password authentication
Before you test anything, confirm which authentication method is active for the proxy setup you plan to use.
Many first-time setup failures are not caused by the proxy endpoint itself. They usually happen because:
- the wrong source IP was authorized
- the request is being sent from a different environment than expected
- the wrong authentication method was used for the request
- the proxy entry was copied incorrectly
If you want a clearer overview of how the service works before you begin, read How InstantProxies Works. If you need to review the layout of the control panel, start with Dashboard Overview.
Step 1: Sign In and Open the Control Panel
Log in to the InstantProxies client area and open your control panel.
The control panel is where you view the proxies assigned to your package, review authentication settings, and prepare the endpoint you want to test.
Before doing anything else, confirm that you can identify the active package or proxy allocation you want to use.
Success Looks Like This
You can access the control panel and identify the active proxy package you want to use.
Step 2: Locate One Proxy Entry
Find one assigned proxy IP from your package.
For your first test, keep the workflow simple. Choose one proxy IP and one supported port. Do not begin with multiple proxies, multiple threads, rotation logic, or a full automation workflow.
Write down the following:
- proxy IP
- proxy port
- the machine or environment you are testing from
- the authentication method you plan to use
This gives you a clean baseline and makes troubleshooting much easier if the request fails.
If you need help locating the right endpoint details, use Finding Your Proxy List.
Step 3: Configure the Correct Authentication Method
Choose one authentication method for your first test and keep the request path simple.
If You Are Using IP Whitelisting
Add the public IP address of the machine that will send the request to the allowlist in the dashboard.
This is the most important step when IP-based access is active.
If you are testing from a different machine than the one you originally had in mind, update the authorized IP before continuing. If your egress IP changes later, requests can stop working until the new IP is authorized.
If you need help with this step, use Authorizing Your IP Address.
If You Are Using Username and Password Authentication
Make sure you have the correct proxy username and password exactly as shown in the dashboard.
Use those credentials exactly as provided in your first request. Do not mix credential-based testing with assumptions from an IP-whitelisted setup.
Success Looks Like This
You know which authentication method is active for the request you are about to test, and the required access details are ready.
Step 4: Choose a Test Port
For your first test, use one known-good port only.
If the request does not work in your environment, you can test another supported port later during troubleshooting. At this stage, keep the variables controlled.
Step 5: Send Your First Proxied Request with cURL
Use one of the following minimal request patterns depending on the authentication method you selected.
If You Are Using IP Whitelisting
curl -x http://PROXY_IP:PORT http://checkip.instantproxies.com/
If You Are Using Username and Password Authentication
curl -x http://USERNAME:PASSWORD@PROXY_IP:PORT http://checkip.instantproxies.com/
Replace the placeholders with the exact values from your dashboard.
Do not add retries, scraping logic, browser options, or application-specific code yet. The goal of this step is to prove one clean request path.
If you want a deeper explanation of the request format, continue to First Request with cURL.
Step 6: Verify the Result
If the request succeeds, the response should show the outbound IP address seen through the proxy path.
Expected format:
IP=YOUR_PROXY_IP
This confirms that:
- the proxy endpoint is reachable
- the selected authentication method is working
- traffic is routing through the proxy
- the destination sees the proxy IP instead of your direct connection
Success Looks Like This
The request completes successfully and the returned IP reflects the proxy path you intended to test.
Once you reach this point, the next step is Verify Your Connection so you can confirm the runtime path more carefully before moving into a larger workflow.
Step 7: Double-Check Using the Built-In Tools
After the cURL test works, use the built-in tools to confirm the environment more clearly.
Test Proxies in the Control Panel
Use the control-panel proxy test to confirm that your assigned proxies are online and responding.
If you need help using that tool, go to Testing Proxies in the Dashboard.
Use Browser Privacy Test for Browser Workflows
If your next step is browser setup or browser automation, use Browser Privacy Test to confirm what a destination sees from your browser session, including observed IP behavior and browser-level request details.
Check Network Status if You Suspect a Service Issue
If a request suddenly stops working after a previously good baseline, check the public network status page before assuming the issue is only local.
If the First Request Fails, Troubleshoot in This Order
Do not move into application-level debugging yet.
Check these in order:
- Are you using the correct proxy IP and port?
- Are you using the correct authentication method?
- If using IP whitelisting, is the current source IP actually authorized?
- If using username and password authentication, were the credentials copied exactly?
- Are you testing from the same machine or environment you intended to use?
- Does the minimal cURL test fail, or only your application code?
- Does the control-panel proxy test show the proxy online?
If the minimal cURL test fails, solve that before debugging Python, Node.js, Playwright, Puppeteer, Selenium, or any higher-level workflow.
For deeper diagnosis, continue to Connectivity Troubleshooting or Authentication and Allowlist Errors.
Common First-Setup Mistakes
The most common setup mistakes are:
- testing from a machine or environment that was never authorized for IP-based access
- using the wrong authentication method for the request
- copying the wrong proxy IP or port
- copying credentials incorrectly
- debugging framework code before proving the proxy path with a minimal cURL request
- changing multiple variables at once instead of testing one proxy on one machine with one request
The safest pattern is always the same: prove one working request first, then expand.
What to Do Next
Once your first request works, continue based on your use case.
I Want to Integrate InstantProxies into Code
Continue to the language guide for your stack, such as Python, Node.js, PHP, Java, Go, or .NET.
I Want to Use InstantProxies in a Browser
Continue to the browser setup guides and then validate the result with Browser Privacy Test.
I Want to Use InstantProxies in Browser Automation
Continue to the browser automation guides for Playwright, Puppeteer, or Selenium.
I Am Still Having Issues
Continue to:
Before Contacting Support
Before opening a support request, collect these details:
- the proxy IP you tested
- the port you used
- the authentication method you used
- the source IP you authorized, if using IP whitelisting
- the machine or environment you tested from
- whether the minimal cURL request succeeded or failed
- whether the control-panel proxy test reported the proxy online
This makes support much faster and reduces avoidable back-and-forth.
Recommended Next Step
If your first request worked, continue to Verify Your Connection.
If your first request failed, continue to Verify Your Connection before changing your code or broader runtime setup.