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.
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.