Buyer proxy protocol
HTTP CONNECT and SOCKS5 only — absolute-URI forward proxy is not supported.
ProxyHubb’s buyer-facing edge (proxy.proxyhubb.com:8090) is an HTTP CONNECT (and SOCKS5) proxy — not a classic absolute-URI forward proxy.
Supported
| Protocol | Port | Notes |
|---|---|---|
| HTTP CONNECT | 8090 | Tunnel TLS via CONNECT host:port — what curl -x and HTTPS clients use |
| SOCKS5 | same listener | Username/password or session-intent auth |
Not supported
Plain HTTP forward-proxy requests (GET http://example.com/… with an absolute URI, no CONNECT) return 501 with:
Only CONNECT supported; use HTTP CONNECT or SOCKS5
Configure clients for HTTPS proxy / CONNECT, not “HTTP proxy that rewrites absolute URLs.”
Auth
| Mode | Username | Password |
|---|---|---|
| Marketplace order | from proxy_credentials.username | from proxy_credentials.password |
| Session intent | session-intent | intent token string |
Host/port are always proxy.proxyhubb.com:8090 unless you override with PROXYHUBB_PROXY_ENDPOINT.
Examples
# Marketplace credentials
curl -x "http://USER:[email protected]:8090" https://httpbin.org/ip
# Session intent (Connect)
curl -x "http://session-intent:[email protected]:8090" https://httpbin.org/ip
# SOCKS5 (same auth forms)
curl --socks5 "USER:[email protected]:8090" https://httpbin.org/ip
Python / Node / Go helpers build these URLs for you — see SDKs.
Common errors
| Symptom | Meaning | Fix |
|---|---|---|
501 + “Only CONNECT supported” | Client used absolute-URI HTTP proxy mode | Switch to CONNECT (curl -x against HTTPS targets) or SOCKS5 |
407 Proxy Authentication Required | Missing or invalid credentials | Check username/password; re-mint intent or re-fetch credentials |
| Timeout / connection refused | Wrong host/port or local firewall | Confirm :8090, not :443 or :8080 |
| TLS errors to destination | Destination site issue, not proxy auth | Test with https://httpbin.org/ip first |
| Works in curl, fails in library | Library defaulting to HTTP forward proxy | Pass an explicit HTTPS proxy URL / CONNECT agent |
See also Session intents and Order credentials.