Android proxy setup

Android's Wi-Fi proxy has no login fields, and Chrome is the app that asks for one. For other apps and mobile data, use a proxy app that stores the login.

Protocols
HTTP proxy in Wi-Fi settings; HTTP or SOCKS5 with a login through a proxy app
Login and password
No fields in Android: Chrome asks in a sign-in window, most apps cannot
UDP
No, not through the Wi-Fi setting
Where the setting is
Settings → Network & internet → Internet → your network → Edit → Advanced options → Proxy
Works with
Residential and mobile proxies

Before you start

  • A Pixel or another phone with stock Android (the menu names below are Pixel's). Samsung and other brands put the same options in a slightly different place.
  • Your proxy login and password from the Residential or Mobile page of the dashboard, and traffic on that product.
  • Decide what you need: Chrome on one Wi-Fi network (the steps below), or every app and mobile data (a proxy app, further down).
Connection details
Host
gate.aeonproxy.com
Port (HTTP / HTTPS)
7000
Login
your proxy login, with targeting keys if you need them: LOGIN-cc-us-sid-abc123
Password
your proxy password

Copy the login and password from the Residential or Mobile page of the dashboard; the generator there also writes ready lines. Key syntax: targeting and sessions.

Add the proxy to a Wi-Fi network

  1. Open Settings → Network & internet → Internet and tap the Wi-Fi network you are connected to.
  2. Tap Edit (the pencil icon) and open Advanced options.
  3. Under Proxy, tap the down arrow and choose Manual.
  4. Proxy hostname: gate.aeonproxy.com. Proxy port: 7000. Leave the list of excluded hosts empty. Tap Save.
  5. Open Chrome and load a page. Chrome opens a Sign in window for the proxy: enter your login (with keys, see below) and your password.

On Samsung Galaxy phones go to Settings → Connections → Wi-Fi, open the settings of the connected network and expand its advanced options to find Proxy.

Which apps use it

Android warns under the proxy fields that the browser uses the HTTP proxy but other apps may not. In practice:

  • Chrome follows it and asks for the login in its sign-in window.
  • Most other apps either ignore the proxy and connect directly, or follow it but cannot send a login and fail.
  • Mobile data never uses it: the setting belongs to one Wi-Fi network.
  • UDP traffic (calls, games) goes direct.

Every app and mobile data: a proxy app

A proxy app runs as a local VPN on the phone, keeps your login and sends every app through the gateway over HTTP or SOCKS5, on Wi-Fi and on mobile data. Step-by-step setup for one such app: NekoBox for Android. Android shows a VPN icon in the status bar while it runs. Set the Wi-Fi proxy back to None when you use an app, so you know which one is in effect. Telegram has its own setting: Telegram.

Check the proxy

Open the IP checker in Chrome. It should show the exit IP and the country you targeted. With a proxy app, check on both Wi-Fi and mobile data.

Rotating or sticky

In the Chrome sign-in window and in a proxy app, use a sticky login such as LOGIN-cc-de-sid-pixel1-ttl-60: apps and sites that keep you signed in expect one address. The IP is kept for up to 60 minutes, then the same login gets a new IP in the same country. For a new IP sooner, use a new key (-sid-pixel2). Chrome keeps the old login until it restarts, so force-stop it first.

If it does not work

What you seeWhat to check
Chrome keeps asking for the loginThe login, the password or a key in the login is wrong (407).
Chrome: ERR_PROXY_CONNECTION_FAILEDThe hostname or port is wrong. Use port 7000 in the Wi-Fi setting.
Chrome: ERR_TUNNEL_CONNECTION_FAILEDThe gateway refused the tunnel: no traffic left (402), a site blocked by default (403) or a failed exit (502). Check the dashboard, then retry.
Chrome works, other apps lose the connectionThose apps cannot send a login. Use a proxy app.
The IP checker shows your own IPThe phone is on mobile data or another Wi-Fi network, or a VPN app is on.

Questions

No. The Wi-Fi proxy has hostname and port fields only. The Username and Password in the mobile network's APN settings belong to the carrier's network, not to a proxy. Chrome asks for the login itself; for other apps use a proxy app.

No. It belongs to one Wi-Fi network. Use a proxy app such as NekoBox for Android for mobile data.

Proxy questions? Ask support in the live chat.