IP authentication

Using a proxy without a username and password

By default, every connection to a ProxyGuys proxy carries a username and password. The IP whitelist adds a second way in. You list the public IPv4 addresses you connect from, and connections from those addresses are let in on a separate whitelist port with no login at all.

That's handy when a program or device has nowhere to type proxy credentials, or when you'd rather not keep a password inside a script on a server. The username and password on the normal ports carry on working at the same time, so switching the whitelist on doesn't disturb anything you've already set up.

Before you start

  • Know the addresses. You need the public IPv4 address of each machine that will connect. For the computer you're on right now, the dashboard can fill it in for you. For a server or another computer, open https://api.ipify.org?format=json on that machine, without the proxy, and note the address it returns.
  • Pick a protocol. Decide whether your program will connect over HTTP or SOCKS5. Each proxy gets one whitelist port, and it speaks the protocol you choose.

Set up the whitelist

  1. In My Proxies, find the proxy and press IPs in the Whitelist column. Another route is the proxy's ⋮ menu (More actions on smaller screens) → IP whitelist. A window titled IPv4 whitelist opens.

  2. Enter an IPv4 address and press Add. Addresses go in one at a time, up to 15 in total. The + your IPv4 chip adds the address you're browsing from.

  3. Under Protocol, select HTTP or SOCKS5.

  4. Press Enable IP auth, which saves the whitelist. Every save replaces the whole list with whatever is in the window, so when you edit it later, leave in every address you still want.

  5. Once it is on, the window shows the whitelist endpoint. Press Copy endpoint to copy the host and whitelist port.

Point your program at it

In the program's proxy settings, enter the host and port you copied, choose the same protocol you picked in the window, and leave the username and password empty. If a program won't accept empty credentials, skip the whitelist for that one and use the normal HTTP or SOCKS5 port with your username and password instead.

To confirm it works, open https://api.ipify.org?format=json or https://httpbin.org/ip through the proxy from a whitelisted machine. You should see the proxy's mobile IP rather than your own address.

When it won't connect

  • Your own address changed. Many home and office connections receive a new public IP now and then, and a VPN gives you a different one. Check your current address at https://api.ipify.org?format=json and add it if it no longer matches.
  • The protocol doesn't match. The whitelist port speaks only the protocol you selected. A SOCKS5 setting aimed at an HTTP whitelist port fails, and so does the reverse.
  • You used a normal port. The HTTP and SOCKS5 ports shown on the proxy still expect a username and password, whitelisted or not. For a login-free connection, use the port from Copy endpoint.
  • An address dropped off. Because saving replaces the list, an address missing from the window when you saved is no longer allowed. Add it again.
  • The host moved. Pressing Change gateway IP moves all of your proxies to a new host IP. Copy the endpoint again afterwards.

Managing it from code

With many proxies, the API is quicker than the dashboard. A call to PUT /proxies/{id}/ip-auth sets the protocol and up to 15 addresses (replacing the old list), and {"enabled": false} turns the whitelist off. To change which IP the proxy sends traffic from, see Changing and rotating IPs.