A SOCKS5 proxy routes traffic through a separate IP for any app that supports it. Below are short, practical setups for the most common cases, and it works with a proxy from any provider, with examples on the IPrazon pool.
Get the proxy details from your dashboard: host (IP), port, login and password. SOCKS5 works at the connection level, so it covers most apps, not just the browser.
Open Settings, Network and Internet, Proxy. Under manual setup enter the host and port. For login and password authentication use the app you are connecting (Windows itself prefers SOCKS without auth), or a client like Proxifier that sends every app through the proxy.
Chrome uses the system proxy, so a tool such as FoxyProxy or a separate profile is the clean way to scope it to the browser. In Firefox open Settings, Network Settings, Manual, pick SOCKS5, enter host and port, and enable remote DNS.
Stock Wi-Fi settings only take HTTP proxies, so for SOCKS5 use an app like Proxydroid or a client that accepts host, port, login and password. Enter the credentials, enable it, and traffic from supported apps goes through the proxy.
Keenetic does not take a SOCKS5 upstream in the stock interface; route through it with the Shadowsocks or a proxy-client component from the app store, pointing it at your host and port. This sends the whole network through one IP.
Open Settings, Data and Storage, Proxy, Add Proxy, choose SOCKS5. Enter host, port, login and password, then save. Telegram shows a shield icon when the proxy is active.
Open any IP-check site through the proxied app and confirm it shows the proxy IP, not your own. If the address is unchanged, recheck the port and that the app actually routes through the proxy.
SOCKS5 covers far more than a browser. Enter host, port and credentials in the right place for each device, then verify with an IP check. Support is on 24/7 if a setup gives trouble.
A private datacenter pool of IPv4 and SOCKS5 with rotation: unlimited traffic, IP:PORT and IP:PORT:LOGIN:PASS formats, and a free test of up to 2 hours. Check the setup on your own task before you pay.
Four values: IP address (host), port, login and password. They are issued in your dashboard as IP:PORT or IP:PORT:LOGIN:PASS. Make sure the proxy type is set to SOCKS5.
The fields are the same (IP, port, login, password), but in the proxy type list you pick SOCKS5 instead of HTTP. SOCKS5 passes any traffic and DNS requests without leaks. More on this in the article about SOCKS5 proxies.
Open any IP checking service, it should show the proxy address, not your real one. If the address has not changed, check the proxy type (SOCKS5), the port and the IP binding in your dashboard.
The usual causes: HTTP is selected instead of SOCKS5, a wrong port, or your IP is not bound in the dashboard (for the format without a login). Less often it is a typo in the login or password.