SOCKS5 Configurator: Username and Password, Setup and Fixes

No. The extension stores a host and a port only, and Chrome's own SOCKS5 client offers no login method, so a proxy that asks for one refuses the connection. The Chromium documentation says: "No authentication methods are supported for SOCKSv5 in Chrome (although some do exist for the protocol)" (Chromium proxy docs).

# socks5_greetings.py: print the login methods a SOCKS5 client offers (RFC 1928, section 3)
import socket, sys, threading

def handle(c):
    ver, n = c.recv(2)
    methods = " ".join("X'%02X'" % m for m in c.recv(n))
    sys.stdout.write(f"greeting: methods {methods}\n"); sys.stdout.flush()
    c.sendall(b"\x05\xff")  # "no acceptable methods": log the greeting, then close
    c.close()

s = socket.socket()
s.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
s.bind(("127.0.0.1", 18080))
s.listen()
print("listening on 127.0.0.1:18080", flush=True)
while True:
    threading.Thread(target=handle, args=(s.accept()[0],), daemon=True).start()

google-chrome --user-data-dir=/tmp/socks-test --proxy-server="socks5://gate.proxyfield.io:<port>" https://api.ipify.org

SOCKS5 Configurator is a small, open-source extension by txthinking, under the MIT License, for Chrome and Edge (source on GitHub). Its source declares "manifest_version": 3, so it is built on Manifest V3, the extension format current Chrome runs.

1. Find your public IP. With no proxy on, open https://api.ipify.org. You see your own network's IP; note it.
2. Allowlist it. In your ProxyField account, add that IP to the allowlist. You see it in the allowlist. The extension sends no username, so it cannot pick a country or city: with allowlist access, the product, location and session are set per port in the dashboard. For a city per entry, use HTTP with a login.
3. Test the gateway from a terminal first. Run curl -x socks5h://gate.proxyfield.io:<port> https://api.ipify.org, where <port> is the port you set up in the dashboard for your allowlisted IP. You see one IP that is not the one from step 1. If this works, any later failure is in the extension, not the proxy.
4. Install SOCKS5 Configurator from the Chrome Web Store (publisher: txthinking) and pin its icon. You see Chrome's warning "Read and change all your data on all websites" before you confirm; the icon then opens the settings page.

5. Enter the server. Check that Socks5 Proxy is on and type gate.proxyfield.io:<port> in the server field, host and port together, with the port you set up in the dashboard. You see the value stay in the field; a missing port shows "Invalid socks5 proxy address" and nothing is saved.

6. Check the Bypass List, then save. You see the switch on, with cn and apple.com in the box. Delete them if you want those sites through the proxy as well. Then select Save.

7. Confirm. Reload https://api.ipify.org: you see a proxy IP, not the one from step 1 (it may differ from step 3, since without a session in a username the gateway gives a new IP on every request). https://ipinfo.io/json shows the proxy's city and country. What you see (example values):

   Copy code

   198.51.100.73
   {"ip": "198.51.100.73", "city": "…", "region": "…", "country": "US", …}

8. Turn it off when you are done. Switch Socks5 Proxy off and save. Chrome goes back to the system proxy settings, and ipify shows your own IP again. You can also disable the extension in chrome://extensions.

The allowlist holds only on that network. On another Wi-Fi network your public IP changes, the gateway refuses it, and pages fail until you add the new IP or turn the proxy off.

Use HTTP when you need a login or a location per entry, such as a US city for a residential IP. Chrome sends HTTP proxy credentials, and for web pages an HTTP proxy carries the same traffic as SOCKS5.

The working HTTP entry, in any switcher with login fields:

Test the same entry from a terminal first:

curl -x gate.proxyfield.io:7000 -U "<login>-country-us-city-new_york:<password>" https://api.ipify.org

Region, session and session time go in the same username; every part after the login is optional, names are lowercase with underscores for spaces, and the country is its two-letter code:

<login>-country-us                                   a US IP, new on every request
<login>-country-us-region-new_york                   New York State
<login>-country-us-city-new_york                     New York City
<login>-country-us-city-new_york-session-he9f2qga    one IP for 20 minutes (the default)
<login>-country-au-region-australian_capital_territory-city-canberra-session-he9f2qga-ttl-60
                                                     one Canberra IP for 60 seconds

Residential is the default; add -mobile after the login for mobile IPs: <login>-mobile-country-us.

The extension itself sends no username, so these settings work in the HTTP entry above and in the desktop apps below, not in SOCKS5 Configurator.

The same gateway, gate.proxyfield.io, works in a browser extension and in desktop apps, on residential and mobile IPs. What changes is how you log in, and with it the port: Chrome extensions need the allowlist and the port you set up in the dashboard, and most desktop tools take a username and password on port 7000. Plans and protocols are on SOCKS5 proxies.

# Any tool that reads a URL
socks5h://<login>:<password>@gate.proxyfield.io:7000

# proxychains: last line of /etc/proxychains.conf, with the gateway's IP (dig +short gate.proxyfield.io)
socks5 <gateway IP> 7000 <login> <password>

1. Turn the extension on and load https://api.ipify.org: the exit IP, not yours.
2. Turn it off and reload: your own IP again.
3. To test a SOCKS5 line before you use it, run it through the proxy checker: up to 100 proxies per check, and your list and results are not stored.

Chromium's error texts: net_error_list.h. Gateway error messages: 407 Proxy Authentication Required for a wrong login or password, an IP not on the allowlist or a malformed location, 402 Payment Required when no traffic is left and 502 Bad Gateway when no exit could be connected; a restricted site gets no separate response, and a 403 comes from the site itself. Status codes are explained in proxy errors, and an extension controlling the proxy has its own guide. Our 24/7 live chat helps with setup and integration.

Residential and mobile share one balance and run over HTTP, HTTPS and SOCKS5. A SOCKS5 proxy changes the IP and location that sites see; it is not a VPN and does not encrypt traffic by itself (proxy vs VPN). Use ProxyField for lawful work within our acceptable use policy.

Start with the Easy Trial: 1 GB for $2.95, with no minimum purchase and no subscription. The traffic never expires and all purchases are final. See pricing per GB.