Proxy gateway

In a backconnect setup you do not see thousands of exit addresses. You connect to one gateway, and it picks an address from the pool and forwards the request.

That is why the address you connect to and the address the website sees are different. A proxy check shows the external IP, the one the website received.

The gateway understands parameters from the username: country, city, carrier, session number. The rotation mode is set by the port.

In Prokso there is one gateway for all types and countries: gw.prokso.com. You can check a connection line with the proxy checker tool.

What the gateway does with each connection

• accepts the connection on a port and uses the port to determine the protocol and mode;
• checks the username and password or your address on the IP whitelist;
• reads the geo parameters from the username, for example LOGIN__cr.de;city.berlin;
• picks an exit address and connects to the site through it;
• counts traffic in both directions and deducts it from the plan.

All of this happens before the site receives the first byte. So if something is wrong at one of these steps, the answer comes from the gateway, not from the site. For example, code 407 means the request stopped at the credentials check, and the site never learned about it.

Gateway responses and what to do about them

Code 503 shows up more often with narrow targeting: a city, ZIP or carrier. Details are on the 503 error page.

Limits and habits that help

One plan holds up to 1000 concurrent connections through the gateway. Keep the number of threads in your script within this limit and raise it gradually. If several scripts run on one plan, they share this limit.

Enter the host name gw.prokso.com in your settings, not the IP address you got from DNS: that way the program always connects where the name points right now. After setup, open the My IP page to see the exit address the gateway picked.