Dashboard

Other Software

Configuration guides for browsers and common proxy tools. Every tool uses the same details: host proxy.eproxies.net, port 23333, username USERNAME-pool-flow (targeting/session parameters optional), password unchanged.

Browsers

Chrome / Edge

A system-level proxy affects all traffic, so an extension (a SwitchyOmega-style proxy switcher) is recommended for on-demand switching:

  1. Create a new profile; choose HTTP or SOCKS5 as the protocol.
  2. Server proxy.eproxies.net, port 23333.
  3. On your first page visit an authentication prompt appears — enter your username and password.

Firefox

Firefox has its own independent proxy settings:

  1. Go to Settings → Network Settings → Manual proxy configuration.
  2. Enter proxy.eproxies.net as the HTTP/HTTPS proxy or SOCKS host, port 23333; for SOCKS choose v5.
  3. Enter your username and password when prompted while browsing.

The dashboard's Code Examples page includes step-by-step, screenshot-based guides for Chrome (Windows/Mac), Edge, Firefox, Safari, Android, and iOS — with your credentials filled in automatically.

Proxifier

Force software without native proxy settings through the proxy:

  1. Profile → Proxy Servers → Add.
  2. Address proxy.eproxies.net, Port 23333, Protocol SOCKS5.
  3. Enable Authentication and enter your username (including -pool-flow and any parameters) and password.
  4. Once Check passes, save, then configure Rules to choose which programs go through the proxy.

Clash / ClashX

Add a node to your configuration file:

proxies:
  - name: "EProxies-US"
    type: socks5
    server: proxy.eproxies.net
    port: 23333
    username: USERNAME-pool-flow-region-US
    password: PASSWORD

Telegram

  1. Go to Settings → Data and Storage → Proxy → Add Proxy.
  2. Choose SOCKS5 and enter server proxy.eproxies.net, port 23333, username, and password.
  3. Save and connect.

Universal troubleshooting rule: whenever configuration fails in any software, first verify credential connectivity with cURL on the same machine. If cURL works, the problem is in how the software was filled in (nine times out of ten it is a username parameter typo); if cURL fails, check your account status and local network.