IPv6 Proxies
IPv6 proxies provide IPv6 exit addresses. Scrapeless documents automatic IPv6 proxy rotation and HTTP, HTTPS, and SOCKS5 support for this proxy type.
Use IPv6 Proxies for workloads whose target services support IPv6 access. Choose the IPv6 channel explicitly when generating connection details.
When to use IPv6 proxies
Consider this type when your application needs IPv6 exits for data collection or automated requests. Check the target’s IPv6 compatibility before relying on this route.
The proxy protocol and exit address family describe different parts of the connection: HTTP or SOCKS5 is how your application talks to the proxy; IPv6 describes the exit address used toward the destination. Use the gateway details generated for the channel rather than substituting a guessed IPv6 gateway address.
Create an IPv6 channel
- Sign in to the Scrapeless dashboard and complete any required account verification.
- Ensure your wallet has sufficient balance.
- Open Proxy Solutions and select the IPv6 proxy type.
- Create a channel, set its password and limit, and save it.
- Select Start for that channel and generate the connection details or request example.
Scrapeless documents the same setup process for Residential, IPv6, and Datacenter Proxies. See Getting Started for the shared walkthrough.
Test the exit connection
Use the details generated for the IPv6 channel:
curl --proxy 'http://YOUR_PROXY_HOST:YOUR_PROXY_PORT' \
--proxy-user 'YOUR_PROXY_USERNAME:YOUR_PROXY_PASSWORD' \
'https://api.ipapi.is/'Replace the four placeholders with the connection details for this proxy type. YOUR_PROXY_USERNAME means the complete generated username, including any options already present. Use the proxy password from that channel.
This example makes an HTTPS request through an HTTP proxy. The response comes from the IP-check service and describes the exit connection it observed. Inspect your actual response; the exit address is not a fixed example value.
For IPv6 verification, use an IP-check destination that accepts IPv6 and confirm that it reports an IPv6 exit. If the test destination cannot be reached through IPv6, use an IPv6-capable test destination before diagnosing your target site.
A successful IP check does not prove that every target can be reached. Test the actual destination through the same channel before scaling the workload.
Rotation and channel options
The product documentation lists automatic IPv6 rotation. Use the rotation or session settings provided for the IPv6 channel, and retain the generated proxy-type identifier. Do not copy a Residential channel’s type identifier into an IPv6 connection string.
The shared documentation explains r_<sessionDuration> and s_<sessionId>. Follow Rotation and Sticky Sessions for the syntax of options exposed by your channel. The IPv6 product page does not specify a separate maximum sticky-session duration.
Use only locations offered for your IPv6 resource. A country listed in the general selector is not a guarantee that an IPv6 exit is currently available there.
Usage and troubleshooting
The IPv6 product description lists traffic-based, per-GB billing. Check the current offering and channel settings for rates and limits.
| Symptom | What to check |
|---|---|
HTTP 407 | Confirm channel credentials and available resources. |
HTTP 525 | Review location filters; no suitable exit was found. |
| Reported exit is not IPv6 | Confirm that the selected channel is IPv6 and that the application is using its proxy configuration. |
| IP check works but the target fails | Check the target’s IPv6 reachability and inspect its response. |
Related configuration
- Authentication and Endpoints: credentials, connection-string fields, and gateways.
- Integrations: connect your application or proxy client.
- Troubleshooting: diagnose authentication, connection, and upstream errors.