Proxy formats
The generator writes the same proxy line in five formats. Pick the one your tool reads, keep the login in one piece, and match the port to the protocol.
The four parts
| Part | Value | Notes |
|---|---|---|
| host | gate.aeonproxy.com | One host for residential and mobile; the login decides the product |
| port | 7000 or 7001 | 7000 for HTTP (HTTPS sites included), 7001 for SOCKS5 |
| user | Your login with its keys, such as LOGIN-cc-us-sid-k3f9a2b1-ttl-30 | The dashes belong to the user name: keep the whole string together |
| pass | PASSWORD | Letters and digits only, so no format needs escaping |
The five formats
| Format | Example |
|---|---|
host:port:user:pass | gate.aeonproxy.com:7000:LOGIN-cc-us:PASSWORD |
host:port@user:pass | gate.aeonproxy.com:7000@LOGIN-cc-us:PASSWORD |
user:pass:host:port | LOGIN-cc-us:PASSWORD:gate.aeonproxy.com:7000 |
user:pass@host:port | LOGIN-cc-us:[email protected]:7000 |
protocol://user:pass@host:port | http://LOGIN-cc-us:[email protected]:7000 or socks5://LOGIN-cc-us:[email protected]:7001 |
Only the last format names the protocol. With the other four, the tool's own setting decides, and it has to match the port: HTTP for 7000, SOCKS5 for 7001.
In the generator, the Protocol switch sets the port in every line and the scheme in the fifth format. Format in the Proxy list card shows the same lines joined another way, with the same session keys. Export saves the list as TXT, CSV or JSON, and Copy all puts it on the clipboard. The proxy list API takes the same five formats in its format parameter.
Which tools read which
| Tool | What it expects | Format to use |
|---|---|---|
| Python requests and httpx, Node.js, Go, PHP with Guzzle | A proxy URL | protocol://user:pass@host:port |
| curl | A URL in -x, or the address in -x and the login in -U | protocol://user:pass@host:port; without a scheme curl treats the line as HTTP |
HTTP_PROXY, HTTPS_PROXY and ALL_PROXY variables | A proxy URL | protocol://user:pass@host:port |
| Java, C#, Selenium, Playwright and Puppeteer | The address in one place, the user name and password in another | Split the line as the Java, C#, Selenium, Playwright and Puppeteer guides show |
| Antidetect browsers and proxy managers | Separate fields, often with a paste or bulk-import box | The pattern the import box shows; the app's setup guide has the fields |
| Our proxy tester | Any of the five | Paste the list as generated |
When an import screen shows a pattern such as IP:PORT:LOGIN:PASSWORD or login:password@ip:port, pick the matching format in the generator and put the host name where it says IP. For a tool with four separate fields, any format works: copy the parts one by one.
# the fifth format works as is in curl and in proxy variables
curl -x "http://LOGIN-cc-us:[email protected]:7000" https://api.ipify.org
export HTTPS_PROXY="http://LOGIN-cc-us:[email protected]:7000"
curl https://api.ipify.orgCommon mistakes
| What happens | Why | Fix |
|---|---|---|
| The tool hangs for 30 seconds, then reports an SSL or connection error | The proxy type is HTTPS, or the URL starts with https://: the tool tries TLS to the proxy, and port 7000 speaks plain HTTP. HTTPS sites work over an HTTP proxy through CONNECT | Choose HTTP, or write http:// |
| A hang, then a closed connection, on port 7000 | The tool sends SOCKS5 to the HTTP port | SOCKS5 goes to 7001 |
| The connection closes at once on port 7001 | The tool sends HTTP to the SOCKS5 port | HTTP goes to 7000 |
| 407 with the right password | The import swapped the columns, or the tool cut the login at a dash | Check that the user field holds the whole login, keys included |
| Names are looked up on your own computer | Some clients resolve the host locally with socks5:// | Use socks5h:// where the client knows it; see the SOCKS5 guide |
One line per session
With Session set to Sticky, each generated line carries its own -sid- key, so each line is a separate IP: give one line to each profile, thread or task. Session time sets how long each line keeps its IP (-ttl-, up to 60 minutes); it starts at 1 minute, so raise it when a tool should keep the address longer. With Rotating, all lines are the same login and one line is enough; every connection through it gets a new IP. More on this in rotating vs sticky sessions.
Questions
protocol://user:pass@host:port. It is the only one that names the protocol, and every library that takes a proxy URL reads it.
Yes. Change Format in the Proxy list card. The same lines appear in the new format, with the same session keys, so nothing has to be generated again.