Free tool · cURL
cURL proxy command generator
Paste a proxy the way your provider gave it to you, choose HTTP or SOCKS5, and copy a cURL command that tests it. The generator quotes the username and password so that characters such as $, ! or @ reach the proxy unchanged, writes curl.exe for Windows PowerShell, and gives the same setup as environment variables for tools that read them. It works with any proxy that takes a username and password, and it runs entirely in your browser: nothing you paste is sent to RoProxy or anywhere else.
Any common format. A RoProxy session's connection string from the dashboard works as it is. It runs in your browser: nothing you paste here is sent anywhere.
This is for an example proxy. Paste yours above.
curl -x 'http://proxy.example.com:8080' --proxy-user 'user:pass' 'https://api.ipify.org/?format=json'export https_proxy='http://user:pass@proxy.example.com:8080'
export http_proxy="$https_proxy"
curl 'https://api.ipify.org/?format=json'What the generator takes care of
Special characters in passwords
Inside double quotes, bash still expands $, backticks and, in an interactive shell, the exclamation mark. The command puts the username and password in single quotes instead, so they reach the proxy exactly as typed.
Windows PowerShell
There, plain curl runs a different command. The PowerShell version calls curl.exe and percent-encodes the credentials into the proxy address, where no quote character can be lost on the way.
SOCKS5 without local DNS
For SOCKS5 the command uses --socks5-hostname: the proxy looks up the website's name, and your own DNS server never sees it.
Any common format
host:port:user:pass, user:pass@host:port, user:pass:host:port and full proxy URLs are read as they are. An IPv6 address goes in square brackets.
Commands it writes for a RoProxy session
The session's connection string from the dashboard is all the generator needs. Each command prints the IP address that websites see.
curl -x 'http://GATEWAY_HOST:HTTP_PORT' --proxy-user 'USERNAME:PASSWORD' 'https://api.ipify.org/?format=json'When the command fails
curl: (97) Can't complete SOCKS5 connection
The proxy accepted the handshake but refused the request. On RoProxy, that is how a Free or Standard session answers on the SOCKS5 port: use the HTTP command.
Received HTTP code 407 from proxy after CONNECT
The proxy rejected the username or password. Paste the proxy string again; a missing character at either end is the usual cause.
Could not resolve proxy
The host part has a typo, or a line break was pasted with it. Compare it with what your provider shows.
Frequently asked questions
Is the proxy I paste sent anywhere?
No. The command is built by JavaScript in this page. The proxy, username and password stay in your browser, and the link that shares your settings never includes them.
Why are the username and password in single quotes?
Single quotes pass every character through as typed, while double quotes let the shell expand $, backticks and history references. A single quote inside the value is written as '\'' to close, escape and reopen the quoting.
Why does the PowerShell command put the password in the proxy URL?
Windows PowerShell 5.1 can drop quote characters from the arguments it passes to curl.exe. Percent-encoded credentials contain none, and cURL decodes them before it talks to the proxy.
Does it work with proxies from other providers?
Yes. Any HTTP or SOCKS5 proxy that takes a username and password works, in any of the formats the tool reads, and so does a proxy without credentials.
Should I pick HTTP or SOCKS5?
HTTP is enough for websites, HTTPS ones included, since cURL tunnels them through the proxy. Choose SOCKS5 when your provider or the tool you are testing needs it.