Use the SOCKS5 line from My assets. A rotating residential credential works over both protocols on proxy.proxy302.com, HTTP on port 2222 and SOCKS5 on port 3333, so you only match the type to the port. A per-IP lease is shown with the protocol you bought, and it also answers on the other port with the same username and password, as tested on 4 November 2026.
Test it first with curl and socks5h, which also sends the DNS lookup through the proxy. If curl fails, a TUN adapter will not fix it.
Test the proxy with curl using the first command below. You should see the proxy exit in the ipinfo.io answer.
Step 2
Get tun2socks for Windows and the wintun driver library, and put wintun.dll in the tun2socks folder or on the PATH. Open a Command Prompt as administrator.
Step 3
Start tun2socks with --device wintun, your proxy URL and --interface set to the name of your real adapter, so the program's own connection to the proxy does not loop back into the tunnel.
Before continuing Never point --proxy at an address that itself goes through the tunnel; the wiki warns this causes a routing loop.
Step 4
In a second administrator window give the wintun adapter an address, set its DNS server, then add the default route through it. The three commands are in the code block below.
Step 5
Run curl https://ipinfo.io/json without -x. The answer should now show the proxy exit. Then open an app that ignores the system proxy and check its IP too.
Expected result The IP and country are those of the proxy, not your home line.
Step 6: undo
Close the tun2socks window. If the network still looks stuck, remove the default route you added through wintun or restart the adapter, then check that Windows is on its normal route again.
tun2socks on Windows: commands
REM Run in an administrator Command Prompt. Placeholders: HOST, PORT, LOGIN, PASSWORD,
REM and "Ethernet" = the name of your real network adapter (see ncpa.cpl).
REM wintun.dll must sit next to tun2socks.exe.
tun2socks.exe --device wintun --proxy socks5://LOGIN:PASSWORD@HOST:PORT --interface "Ethernet"
REM In a second administrator window:
netsh interface ipv4 set address name="wintun" source=static addr=192.168.123.1 mask=255.255.255.0
netsh interface ipv4 set dnsservers name="wintun" static address=8.8.8.8 register=none validate=no
netsh interface ipv4 add route 0.0.0.0/0 "wintun" 192.168.123.1 metric=1
Example: commands follow the tun2socks wiki and have not been run by us on a Windows machine here; replace the placeholders with your own values and the adapter name from ncpa.cpl.
curl -x socks5h://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/json
REM After the TUN is up, a plain request should show the proxy exit, with no -x:
curl https://ipinfo.io/json
Example only: replace the placeholders. The first line goes through the proxy explicitly, the second relies on the adapter.
When something goes wrong
No internet at all after the route is added.
Check Is tun2socks still running, and does curl -x with the same proxy URL work? A routing loop appears when the connection to the proxy itself goes into the tunnel.
Fix Check that --interface names the real adapter, close tun2socks, remove the route and test the proxy again outside the tunnel.
Stop when If curl -x fails outside the tunnel too, the problem is the proxy details, not tun2socks.
Websites open by IP but not by name.
Check The DNS server on the wintun adapter. The wiki notes Windows usually needs it set by hand.
Fix Run the netsh dnsservers command again with a resolver you can reach.
One app still shows your real IP.
Check Whether that app has its own network path, such as its own VPN or proxy setting, and whether it starts before the tunnel is up.
Fix Restart the app after the tunnel is up and check again; if it still goes direct, use the app's own proxy field.
Windows SOCKS5 FAQ
Does the Windows proxy page support SOCKS5 with a login?
Its manual setup asks for an address and a port, with no username or password fields. For a SOCKS5 login use Proxifier or tun2socks.
SOCKS5 on all three lines: rotating residential from US$1.50/GB, static ISP and datacenter IPs per IP and term. Port 3333 with username and password, and the errors you see when a setting is wrong.
Check the exit IP, country and ISP your proxy really gives you in 30 seconds — and why IP databases disagree on the city. With our own test of three lookup services.
Reference links
5
Proxy302 product facts and price list
Product observation · Confirmed on:
Product facts file of the site (values checked against the console, the backend and the price table in October and November 2026): products, prices in US$ (1 PTC = US$1), lease terms, protocols and ports, renewal rules, no free trial.
Read on 17 November 2026: Settings, Network & internet, Proxy; manual setup asks for the proxy IP address and port and an exception list; the page does not list which apps use it.
Read on 17 November 2026: Windows steps with wintun, the --device, --proxy and --interface flags, and the netsh commands for address, DNS and the default route; a warning that a proxy running locally can cause a routing loop.
Read on 17 November 2026: supported protocols SOCKS4, SOCKS4A, SOCKS5, HTTPS and HTTP; SOCKS5 username and password among the authentication methods; separate pages for proxy server settings and proxification rules.
The page did not describe the menu steps, so this guide does not either.
Ready to try it?
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.