Proxy Protocols
TrueProxies supports HTTP/CONNECT and SOCKS5, but the public transport depends on the product. Copy the protocol, host, and port together from the dashboard.
Residential IPv4 protocols
Section titled “Residential IPv4 protocols”Residential IPv4 publishes four ports on the subscription’s own host, two of them encrypted to the proxy edge:
- HTTP and CONNECT:
http://YOUR_HOST:YOUR_HTTP_PORT - HTTP and CONNECT over TLS:
https://YOUR_HOST:YOUR_HTTPS_PORT - SOCKS5:
socks5://YOUR_HOST:YOUR_SOCKS_PORT - SOCKS5 over TLS:
socks5+tls://YOUR_HOST:YOUR_SOCKS_TLS_PORT
The HTTP endpoint accepts normal proxy requests and CONNECT tunnels. The SOCKS5 endpoint supports authenticated TCP proxying with clients that implement SOCKS5. Both billing options use this Residential IPv4 transport; compare current Unlimited and GB-Based commercial terms on their canonical product pages.
Dedicated IPv6 protocols
Section titled “Dedicated IPv6 protocols”Datacenter IPv6 and Residential IPv6 use subscription-specific encrypted endpoints:
| Dashboard protocol | Public connection | Important behavior |
|---|---|---|
https | Exact assigned host on :443 | TLS is terminated at the proxy edge and routing depends on the hostname/SNI |
socks5+tls | Exact assigned host on its dedicated dashboard port | Establish TLS first, then speak authenticated SOCKS5 inside it |
Plain SOCKS5 clients cannot connect directly to socks5+tls. Use the supported
localhost adapter or a validating TLS wrapper. A TCP-only wrapper supports SOCKS
CONNECT only; it does not carry SOCKS UDP.
Direct public UDP ASSOCIATE is rejected. The supported adapter can carry UDP
inside its authenticated encrypted tunnel when that capability is provided for
the subscription.
Comparison
Section titled “Comparison”| Feature | Residential IPv4 HTTP | Residential IPv4 SOCKS5 | Dedicated IPv6 HTTPS | Dedicated IPv6 SOCKS5+TLS |
|---|---|---|---|---|
| Proxy-edge encryption | No; encrypt target traffic with HTTPS | No; encrypt application traffic where supported | Yes | Yes |
| Default public port | 8080 | 1080 | 443 | Dashboard-assigned dedicated port |
| Standard client support | Broad | Requires SOCKS5 support | Requires HTTPS-proxy support | Requires a TLS wrapper/adapter |
| Direct public UDP | No | Product/client dependent; validate before use | No | No |
Product-specific controls
Section titled “Product-specific controls”- Residential IPv4 supports the documented country and sticky-session username forms. Its exits cannot reach IPv6-only destinations.
- Residential IPv6 and Datacenter IPv6 use assigned city endpoints. Do not copy Residential IPv4 username suffixes onto their credentials.
- Endpoint inventory and authentication mode in the dashboard are authoritative.
See How to Connect for safe examples and the exact username grammar.