Oxylabs' ISP Proxies, available through the user-friendly self-service platform, provide unparalleled flexibility and control over your proxy IP address usage. These proxies feature unlimited-duration sessions, ensuring uninterrupted data collection from even the most complex targets.
Explore this quick guide to grasp the basics and promptly kick-start your operations with Self-Service ISP Proxies.
Setting up Self-Service ISP Proxies
1. Register and purchase IPs
Start by accessing the Oxylabs dashboard and creating an account. Choose the quantity of IPs you wish to purchase, specify the proxy locations if necessary, and complete the transaction.
2. Set up a proxy user
To begin using Self-Service ISP Proxies, you'll need to set up a proxy user. Enter your chosen username and password, then click on Create proxy user. Be sure to save these credentials for future access. Proxy user credentials are your access to the IPs.
3. Run a request
Once setup is complete, you can now create and execute your first cURL request in a terminal or any other environment to test the ISP Proxies. Send a query to https://ip.oxylabs.io/location using the command below, specifying port 8001 and your proxy credentials:
curl -x isp.oxylabs.io:8001 -U "user-USERNAME:PASSWORD" https://ip.oxylabs.io/locationUpon executing this command, the output will display the IP address with your request. When connecting through port 8001, the same IP address assigned to this port will always be used. To switch to another IP, change the port to 8002, 8003, and so forth. Retrieve your proxy list.
Access your proxy list in the dashboard by navigating to the My Products section, clicking on ISP Proxies, and selecting Proxy List.
What's included in a proxy list?
| Entry point | A gateway for connecting to your proxies |
|---|---|
| Port | A designated port to access a specific proxy from your list |
| Country | The geographic location of your proxies |
| Assigned IP | A specific proxy IP assigned to the chosen port |
Location settings
ISP proxy network offers country targeting via additional parameters in the username.
IPs get chosen from the specified country pool if a country parameter is provided. Below is a sample credentials structure with the country parameter performed from a random IP address in France:
curl -x isp.oxylabs.io:8000 -U 'user-USERNAME-country-FR:PASSWORD' https://ip.oxylabs.io/locationProtocols
Self-Service ISP Proxies support HTTP, HTTPS, and SOCKS5 protocols. For instance, to connect through an HTTPS protocol, you must specify this in your request by adding https:// to your entry point:
https://pr.oxylabs.io:7777Make sure that the libraries or third-party tools you intend to use are compatible with HTTPS and SOCKS5 protocols.
Here’s a code example with the SOCKS5 protocol:
curl -x socks5h://pr.oxylabs.io:7777 -U "customer-USERNAME:PASSWORD" ip.oxylabs.io/locationResponse codes
When using ISP Proxies, you may receive response codes that indicate specific reasons for success or failure. Here are the most common ones:
| Response code | Error message | Description |
|---|---|---|
| 400 | Bad Request | This error code can be returned by a proxy server if the request did not specify a host to connect to or if there was a general error in parsing the HTTP request. Ensure that the request is correctly formed, including the URL, and try again. |
| 407 | Proxy Authentication Required | This response indicates that the request lacks proxy authentication information or the username or password is invalid. Include the Proxy-Authorization header in your request, verify that your username and password are correct, and then try again. |
| 500 | Internal Server Error | The proxy server has encountered an internal error. Retry the request at a later time. |
| 502 | Bad Gateway | This response signifies that the IP assigned to your session ID is no longer available or there are no exit nodes meeting your specified parameters (e.g., city, ASN) at the given time. To resolve this issue, you can wait for one minute for the system to assign a new IP address to your session ID or switch to a new session ID (i.e., change the sessid parameter) to receive a new IP address. |
| 522 | Timeout | The proxy server did not get a response from the upstream server in time. Retry the request. |
| 525 | No Exit Found | This custom HTTP status code means that the proxy could not find an exit node that satisfies the request. Adjust the request filter parameters or try again later. |
Important: When sending a request, ensure you connect to your proxy server by specifying the port number rather than the IP address.
Usage statistics
You can view your usage statistics for ISP proxies by visiting the Oxylabs dashboard. Under the Statistics section, you will find detailed information about your traffic usage, the number of requests, and the number of errors received each day. Additionally, there is an option to filter the statistics and view metrics for a specific time period. Here’s what the dashboard looks like:
1. The statistics page:
You can filter the information by targets, subnets, and IPs. Additionally, you may refine the data further by date range, IP, subnet, target, or user. On this page, you will also be able to see the number of errors you’ve received.
Additional resources
If you have any further questions, please reach out to our Support Team via live chat or email. Also, if you're interested in other proxy types, check them out and find the best proxy server for your needs.
We offer a wealth of content to address most queries and provide new learning opportunities, so feel free to explore:
About the author
Maryia Stsiopkina
Senior Content Manager
Maryia Stsiopkina is a Senior Content Manager at Oxylabs. As her passion for writing was developing, she was writing either creepy detective stories or fairy tales at different points in time. Eventually, she found herself in the tech wonderland with numerous hidden corners to explore. At leisure, she does birdwatching with binoculars (some people mistake it for stalking), makes flower jewelry, and eats pickles.
All information on Oxylabs Blog is provided on an "as is" basis and for informational purposes only. We make no representation and disclaim all liability with respect to your use of any information contained on Oxylabs Blog or any third-party websites that may be linked therein. Before engaging in scraping activities of any kind you should consult your legal advisors and carefully read the particular website's terms of service or receive a scraping license.
Related articles
What Is Fetch API in JavaScript? Definition, Use Cases, & Examples
Yelyzaveta Nechytailo
2024-12-09
How to Make HTTP Requests in Node.js With Fetch API
Augustas Pelakauskas
2024-12-09
Get the latest news from data gathering world
Scale up your business with Oxylabs®