IP Authentication (Passwordless)
Whitelist the source IPs you control and connect to Proxio Residential with no username or password. Learn how per-binding geo and session defaults work, the 50-IP limit, the IP conflict rules, and the security tradeoff.
IP authentication lets a machine at a known, fixed IP address use your Residential proxies without sending a username or password. You whitelist the source IP once; after that, connections from it are recognized and authorized automatically. This runs alongside username/password auth, so turning it on does not disable your credentials.
How it works
Whitelist your source IP
In your Residential service's Sub-users tab, add the public IP address of the machine that will connect. This creates a binding between that IP and the credential.
Connect with no credentials
From that IP, point any client at the gateway with the username and password left out entirely:
curl -x http://geo.proxio.cc:16666 https://ipinfo.ioTargeting comes from the binding
Because there is no username to carry -region- or -sessid- segments, each binding
stores its own defaults and applies them automatically.
Per-binding defaults
Every binding remembers a small set of defaults that are applied to connections from that IP:
| Default | Values |
|---|---|
| Country / state / city | Any target you would otherwise put in the username |
| Sticky | On or off |
Session length (sesstime) | 1 to 90 minutes |
This means two different whitelisted IPs on the same credential can behave differently (one pinned to Germany with a 30-minute sticky session, another rotating freely in the US) without either one sending a username.
Limits and rules
- Up to 50 whitelisted source IPs per credential.
- Binding an IP that's already whitelisted on one of your own credentials fails
with an
IP_ALREADY_BOUNDerror; the dashboard tells you which credential holds it, so you can remove it there first if you meant to move it. - Binding an IP that isn't available for some other reason is rejected neutrally
(an
IP_UNAVAILABLEerror), without disclosing why. - Only public addresses are allowed. Private, CGNAT and reserved ranges are rejected, because they are not globally unique and cannot identify you safely.
- Whitelist additions are rate limited to 30 per minute per account. Adding IPs in a tight loop past that gets a rate-limit error; wait and retry.
The security tradeoff
IP auth trades a password for trust in an address, so the address has to be one you truly control.
Only whitelist an IP you control
Anyone connecting from a whitelisted IP uses your quota with no password. On a shared or NAT'd IP (office network, mobile carrier / CGNAT), everyone behind that IP can spend your data. Only whitelist a static, dedicated IP you control.
Password auth keeps working
Adding an IP binding never turns off username/password authentication. Both work in parallel, so a whitelisted server and a laptop using credentials can hit the same credential at once.
Removing a binding
Delete the IP from the Sub-users tab and connections from it stop being authorized within about 30 seconds while the change propagates; a connection opened during that window can still succeed. The same window applies to setting a credential inactive or deleting it.
Revoking a compromised IP is not instant
Treat the 30-second window as real. If an IP is compromised, remove the binding and then confirm the traffic has actually stopped rather than assuming the cut-off landed the moment you clicked.
Protocols & Ports
Proxio Residential serves HTTP/HTTPS and SOCKS5 on a single endpoint, geo.proxio.cc:16666. Learn when to use socks5h:// versus socks5://, why SOCKS5 is CONNECT-only, and how the gateway handles your TLS.
ISP & Datacenter Proxies
Proxio ISP and Datacenter proxies are dedicated IPs delivered per order, each with its own host, port and credentials. They are built for flat-rate, unlimited-bandwidth workloads and do not use the Residential username-targeting grammar.