How to connect

Learning how to connect to a proxy with ColdProxy takes only a few minutes. Every plan connects through a dedicated per-service gateway host, a proxy server port in a fixed range, and your credentials: the same three values you plug into any app, browser, or HTTP client. This page walks through the gateway host, the port range, the two proxy-string formats, and the hostname-vs-IP toggle. For authentication options, see Authentication.

#Your gateway host

Each plan you purchase gets its own gateway host, gw-{service-id}.coldproxy.com, built from the numeric service/package ID. The examples in these docs use service ID 2312:

gw-2312.coldproxy.com

{service-id} is shown in your client area after purchase. You never have to construct the host manually; the exact hostname is displayed there.

#How to connect to a proxy: IP and port, hostname vs direct IP

By default the client area shows the hostname. If your tooling requires a fixed proxy IP and port endpoint, use the Use Hostname instead of IP toggle in the client area to switch between:

Both forms route to the same gateway. The hostname is the safer default for production integrations.

#Proxy server port range

ColdProxy gateways accept connections on proxy server ports from 30000 to 34999. The same range applies to all three protocols; there is no separate port range for HTTP versus SOCKS5.

Each plan can be provisioned with 1 to 5,000 unique ports within that range; connections work on the ports your plan is provisioned with. Plans currently ship with the standard full 30000–34999 range, so in practice any port in the range answers. The 5,000 figure is the configurable ceiling, not a default; provision the number of ports your workload needs. See Ports & SuperPorts for how to bind geo and session settings to port ranges.

Throughout these docs 30000 is used as the example port.

#Proxy-string anatomy

A ColdProxy proxy string is four colon-separated fields:

host : port : username : password

Colon-delimited form (used by many scraping and automation tools):

gw-2312.coldproxy.com:30000:USERNAME:PASSWORD

URL form (used by most HTTP client libraries):

http://USERNAME:PASSWORD@gw-2312.coldproxy.com:30000

Both forms are equivalent. Use whichever your client library expects.

#Connection examples

cURL

curl -x "http://USERNAME:PASSWORD@gw-2312.coldproxy.com:30000" \
  "https://api.vipv6proxy.com/api/checker/my-ip"

Python (requests)

import requests

proxy = "http://USERNAME:PASSWORD@gw-2312.coldproxy.com:30000"
proxies = {"http": proxy, "https": proxy}

resp = requests.get("https://api.vipv6proxy.com/api/checker/my-ip", proxies=proxies, timeout=30)
print(resp.status_code, resp.json())

JavaScript (Node.js, got + hpagent)

import got from 'got';
import { HttpProxyAgent } from 'hpagent';

const agent = new HttpProxyAgent({
  proxy: 'http://USERNAME:PASSWORD@gw-2312.coldproxy.com:30000',
});

const response = await got('https://api.vipv6proxy.com/api/checker/my-ip', { agent: { http: agent, https: agent } });
console.log(response.body);

Go

package main

import (
	"fmt"
	"io"
	"net/http"
	"net/url"
)

func main() {
	proxyURL, _ := url.Parse("http://USERNAME:PASSWORD@gw-2312.coldproxy.com:30000")
	client := &http.Client{Transport: &http.Transport{Proxy: http.ProxyURL(proxyURL)}}
	resp, _ := client.Get("https://api.vipv6proxy.com/api/checker/my-ip")
	defer resp.Body.Close()
	body, _ := io.ReadAll(resp.Body)
	fmt.Println(string(body))
}

#Next steps

• Authentication — User:Pass or IP whitelisting (or both).
• Protocols — HTTP, HTTPS, and SOCKS5 on the same port range.
• Ports & SuperPorts — bind geo and session settings to port ranges at the plan level.