Documentation
Test a Proxy with cURL
Use cURL to confirm Thunderproxy connection settings before adding proxies to an app, scraper, or browser profile.
cURL is the fastest way to test whether your Thunderproxy connection settings work outside the dashboard. Test with cURL before changing application code or importing a large proxy list.
Quick answer: copy the dashboard-generated cURL command when available. If the cURL test works, your Thunderproxy credentials and gateway are valid; any remaining issue is usually app format, protocol, or import configuration.
Test with user:pass
Use this shape when your subscription uses username and password authentication:
curl --proxy "http://username:password@host:port" "https://api.ipify.org?format=json"
Replace the placeholder values with the current dashboard values:
| Placeholder | Use this Thunderproxy value |
|---|---|
username | Generated rotating username or Static ISP row username |
password | Proxy password |
host | Gateway host |
port | Gateway port for the selected protocol |
For rotating products, choose geotargeting and rotating or sticky mode before copying the username.
Test SOCKS5 with cURL
If the dashboard shows SOCKS5 for your subscription, use the SOCKS5 port and a SOCKS5 proxy URL:
curl --socks5 "username:password@host:port" "https://api.ipify.org?format=json"
If your app is set to SOCKS5 but your cURL test uses the HTTP port, the results will not match. Keep protocol and port together.
Test IP authentication
Use IP authentication only after the connecting machine's source IP has been added in the dashboard.
curl --proxy "http://host:port" "https://api.ipify.org?format=json"
If IP authentication fails:
- Confirm you are testing from the same network or server you added.
- Remove stale trusted IPs when your home, office, or server IP changes.
- For rotating products, confirm the saved cloud settings match the location and session behavior you expect.
Read the result
A successful request returns the exit IP seen by the target service. That IP is different from the Thunderproxy gateway host.
If the command returns an authentication error, check credentials, subscription activity, remaining usage, and username format.
If the command works but an app fails, compare:
- Protocol: HTTP vs SOCKS5.
- Port.
- Proxy string format.
- Whether the app requires separate host, port, username, and password fields.
- Whether the app imported stale proxy-list lines.
Use cURL as your baseline
When troubleshooting, test one current proxy line with cURL first. After that line works, copy the same values into your app in the format the app expects.