Browsers
ProxyGuys proxies in VMLogin
VMLogin profiles can be shared with teammates and moved between computers. That puts weight on one choice you might otherwise skip: how the profile proves to the proxy that it may connect. ProxyGuys gives you two ways, and a proxy can use both at the same time.
Two ways to authenticate
- Username and password on the proxy's normal HTTP or SOCKS5 port. The login is stored in the profile, so it works on whatever network the profile is opened from.
- IP whitelist. You list the public IPv4 addresses allowed in, up to 15 of them. They connect to a separate whitelist port with no username or password, and nobody else can use that port. A teammate on another network gets nowhere until their address is added.
For profiles that travel between people, username and password is the easier choice. The whitelist suits a fixed office connection, or software that has nowhere to store a login.
Option A: username and password
In My Proxies, confirm the proxy is Running; press Start proxy if it is still Pending. Read the host and port off the "SOCKS5 proxy" line in the Connection column, then use Copy username and Copy password under Credentials.
In VMLogin (available from the VMLogin website), create a new browser profile.
Open the profile's proxy server settings, turn on Enable proxy server and select SOCKS5 as the proxy type.
Enter host, SOCKS5 port, username and password. VMLogin also takes them pasted in one go in the order IP:port:username:password, which is how the proxy's ⋮ → Details lists them (with the SOCKS5 port). Press Test Proxy, and save the profile once it passes.
Option B: IP whitelist
In My Proxies, press the "IPs" button in the Whitelist column, or choose ⋮ → IP whitelist. A window titled "IPv4 whitelist" opens.
Add each allowed address with Add. The "+ your IPv4" chip fills in the address you are on right now. Saving replaces the whole list, so include every address you want to keep.
Pick the Protocol, HTTP or SOCKS5 (each proxy has one whitelist port), and press Enable IP auth to save.
The whitelist endpoint then appears in the window. Copy endpoint copies the host and the whitelist port.
In the VMLogin profile, choose the same protocol you picked in ProxyGuys, enter the host and whitelist port, leave username and password empty, then test and save.
Check from inside the profile
Launch the profile and open httpbin.org/ip. The "origin" should be the proxy's US mobile IP rather than your own. When you share the profile, ask whoever receives it to run the same check from their computer. With the whitelist in use, that check tells you straight away whether their address is on the list.
Fixing a failed test
- Works for you, fails for a colleague. With the whitelist, their IPv4 address isn't on the list. Add it, or move the profile to Option A.
- Ports mixed up between the two options. The whitelist port goes without a login; the normal ports go with one. A profile pointed at the whitelist port from an address that isn't listed will be turned away.
- Port and protocol from different lines. SOCKS5 needs the SOCKS5 port, HTTP the HTTP port. For the whitelist, the profile's protocol must match the one chosen in the IPv4 whitelist window.
- Login rejected after a password change. A new password set with New password has to go into every profile that uses the proxy, shared copies included. In VMLogin, a sub-account can only edit the proxy on a profile shared by the main account once it has been given permission to change proxy IPs.
Something else? Open a ticket under Tickets or write to support@proxyguys.com.