Use curl on a computer or server to test a proxy separately from application configuration. Each example affects only that request.
1. Prepare proxy details
Find an active resource in Proxy management and check its protocol, host, port, proxy username and proxy password. These are proxy credentials, not your website sign-in. Menu names can vary by tool version.
| Field | What to enter |
|---|---|
| Protocol / Type | Choose HTTP or SOCKS5 to match the resource and its port. |
| Host / Address | Copy the IP or connection hostname from the resource; enter only the host. |
| Port | Copy the port from the same resource, rather than the tool’s default. |
| Username and password | Copy the proxy credentials into separate fields; check case and extra spaces. |
2. Configure the tool
- Open a terminal and run curl --version. In Windows PowerShell, use curl.exe --version.
- Choose the matching HTTP or SOCKS5 command below and replace the host, port and username.
- Run it and enter the proxy password at the prompt. Password characters are normally not displayed.
- On success, ipify returns the request’s public exit IP. Compare it with the expected exit before testing your real target.
HTTP proxy
curl --proxy "http://PROXY_HOST:PROXY_PORT" --proxy-user "PROXY_USERNAME" --connect-timeout 15 --max-time 30 https://api.ipify.orgSOCKS5 proxy with remote hostname resolution
curl --proxy "socks5h://PROXY_HOST:PROXY_PORT" --proxy-user "PROXY_USERNAME" --connect-timeout 15 --max-time 30 https://api.ipify.orgReplace PROXY_HOST, PROXY_PORT and PROXY_USERNAME with your actual dashboard details. Only the username is supplied, so curl prompts for the proxy password instead of placing it in command history. Use curl.exe explicitly in Windows PowerShell; use curl on macOS or Linux. Redact credentials from shared screenshots and logs.
socks5h asks the proxy to resolve the target hostname; socks5 resolves it locally. For HTTP 407, check proxy authentication. For timeouts or refused connections, check address, port and reachability. Check proxy credentials for SOCKS5 authentication errors too; disabling TLS certificate checks does not fix proxy authentication.
3. Verify the connection
Open an IP checker inside the configured app, browser profile or device, then test your target website. A successful connection check or latency value does not prove all requests use the intended route. Location differences can also come from lookup databases.
4. Troubleshooting
- Authentication fails: Check the proxy credentials and resource validity. Do not use your MantaProxy website account.
- Connection times out: Check host, port, protocol and network reachability, then consult the troubleshooting FAQ.
- Your local IP still appears: Check the selected proxy, matching rules and exclusions; avoid competing proxy extensions or clients controlling the same traffic.
5. Official documentation and related guides
curl: proxy options · curl: authentication · ipify
Proxy management · Protocols and configuration FAQ · Connection troubleshooting FAQ · IP checker