Local Proxy Forwarder: gost and 3proxy for Proxy Login

When a local forwarder helps

Some tools only have two proxy fields, host and port. Others take a SOCKS5 address but never send the username and password. Chrome is a familiar case: its documentation says no authentication methods are supported for SOCKSv5. A proxy that needs a login cannot be used there directly.

A forwarder fixes this without touching the tool. It listens on your own machine, accepts connections with no login, and opens the real connection to the proxy with the login you wrote into it. The tool never sees the password.

• SOCKS5 login in Chrome

• Sources:
• Chromium notes on proxy settings

Check first whether you need one

If the tool accepts a proxy URL, try http://LOGIN:PASSWORD@HOST:PORT before adding a forwarder. A per-IP static lease on Proxy302 also connects over the other protocol on that protocol's port, so an HTTP address on port 2222 is often enough for tools that dislike SOCKS5 logins.

Use a forwarder when the tool has no place for the login at all, when it ignores it, or when you want the password kept out of the tool's settings file.

• Sources:
• Proxy302 product facts and price list

gost: one command

gost takes a local listener with -L and the next proxy with -F. A user:pass@ in the -F address is how the login is passed on. Bind the listener to 127.0.0.1 so only programs on your own computer can use it; an empty host listens on every interface.

If the password contains @ : / or #, percent-encode them in the URL, for example @ becomes %40.

• Sources:
• gost documentation: SOCKS (go-gost/docs)
• gost documentation: proxy concept (go-gost/docs)

gost commands

# HTTP listener on the loopback address, forwarding to a SOCKS5 proxy that needs a login
gost -L http://127.0.0.1:8080 -F socks5://LOGIN:PASSWORD@HOST:3333

# Same idea, but the local port speaks SOCKS5 and the next hop is an HTTP proxy
gost -L socks5://127.0.0.1:1080 -F http://LOGIN:PASSWORD@HOST:2222

Example only: replace HOST, LOGIN and PASSWORD with the values from My assets. Use port 3333 for a SOCKS5 IP and 2222 for an HTTP IP.

3proxy: a config file

3proxy reads a config file in order. auth iponly checks clients by the access list instead of a login, allow limits who may connect, parent names the next proxy with its login and password, and the proxy line starts the local service. The parent line must come after the allow rule it belongs to, and -i127.0.0.1 keeps the service on the loopback address.

For several local ports with different logins, repeat the allow, parent and proxy lines for each port. Starting a second block with flush clears the earlier rules, so each port keeps its own next hop.

• Sources:
• 3proxy configuration manual (3proxy.cfg)
• 3proxy how-to examples

3proxy config for one local port

auth iponly
allow * 127.0.0.1
parent 1000 socks5 HOST 3333 LOGIN PASSWORD
proxy -p8080 -i127.0.0.1

Example only: save as 3proxy.cfg and start with 3proxy 3proxy.cfg. Replace HOST, LOGIN and PASSWORD.

3proxy config for two local ports

auth iponly
allow * 127.0.0.1
parent 1000 socks5 HOST1 3333 LOGIN1 PASSWORD1
proxy -p8080 -i127.0.0.1

flush
allow * 127.0.0.1
parent 1000 socks5 HOST2 3333 LOGIN2 PASSWORD2
proxy -p8081 -i127.0.0.1

Example only: port 8080 goes to one IP and port 8081 to another.

gost or 3proxy

Based on the gost and 3proxy documentation read on 13 November 2026; the choice is about convenience, both do the same job.

• Sources:
• gost documentation: SOCKS (go-gost/docs)
• 3proxy configuration manual (3proxy.cfg)

Use it with a Proxy302 IP

1. Step 1

   Open My assets, click the IP and copy the host, port, username and password. The protocol badge tells you whether the port is HTTP (2222) or SOCKS5 (3333).

   • Static ISP proxies

2. Step 2

   Start gost or 3proxy with those values, as in the examples above, bound to 127.0.0.1.

3. Step 3

   In the tool, set the proxy to 127.0.0.1 and the local port (8080 in the examples), with the type that matches the listener: HTTP for -L http://, SOCKS5 for -L socks5://. Leave username and password empty.

   Expected result The tool connects without a login prompt.

4. Step 4

   Check the exit with the command below. The country and network should be the ones you bought.

Check the exit through the forwarder

curl -x http://127.0.0.1:8080 https://ipinfo.io/json

Example only. It should print the IP details of the proxy, not of your own connection.

When it does not work

Keep the forwarder private

Bind it to 127.0.0.1 and not to every interface. A forwarder reachable from the network would let other people send traffic through your login. On a server, also close the local port in the firewall.

Do not leave the password in shared shell history or in a script others can read. A 3proxy config file with limited permissions is easier to protect than a long command line.

FAQ

Further reading

SOCKS5 login in Chrome

Chrome has no SOCKS5 login, but a static ISP per-IP lease also works on HTTP port 2222 with the same login.

Proxy address, port, username and password

Every working proxy is described by five basic fields: protocol, host address, port, login, and password.

Fix ERR_PROXY_CONNECTION_FAILED

The ERR_PROXY_CONNECTION_FAILED error appears in Chrome and Edge when the browser cannot establish a connection with a proxy server.

ISP proxies (static residential)

Fixed static ISP proxies: a residential-grade IP that stays the same for the whole term. For social accounts, stores and AI tools. HTTP and SOCKS5.

View options and pricing