Concepts
How the gateway works: rotating and sticky sessions, location targeting, proxy formats, UDP, WebRTC and the limits that apply to every account.
Sessions and targeting
Rotating vs sticky sessionsYour login decides how the exit IP changes: a new IP for every connection, or one IP shared by every connection with the same session key for up to 60 minutes.Location targetingCountry, region, city, ISP and carrier go into the login as keys. The gateway finds an exit that matches or refuses the login; it never widens the area on its own.Proxy formatsThe generator writes the same proxy line in five formats. Pick the one your tool reads, keep the login in one piece, and match the port to the protocol.
Protocols
SOCKS5 and UDPPort 7001 is a SOCKS5 proxy with a login and password, for TCP and for UDP. Use it for apps that are not web browsers, and for UDP, which the HTTP port cannot carry.WebRTC leaksWebRTC can show a site your own IP address while every page loads through the proxy. The gateway cannot stop it; a setting in the browser or the profile can.
Limits and errors
Gateway errorsWhen the gateway refuses a connection it says why: in an
X-Reason header on port 7000, in a SOCKS5 reply code on port 7001. Every answer is listed here with how your tool shows it and the fix.Default limitsA few targets are closed for every account, and a few rules protect the gateway. Everything else is open: bought traffic has no limit on threads or connections.