HTTP and SOCKS5 proxy setup for every device and app

Copy your access point details from the Build dashboard and use them in Windows, macOS, Android, iPhone, browsers, Proxifier, antidetect browsers and code.

Windows & macOSAndroid & iPhoneBrowsers, tools & code
Proxy access point
HOSTyour-endpoint
PORTHTTP or SOCKS5
USERNAMEper access point
PASSWORD••••••••••
The pairing PIN only links the phone. Each access point has its own login.

Find your proxy details

In the dashboard, open your connection and go to Proxy. Each access point shows four values:

HostThe hostname on the access point, for example k3x9q2m7ab.nd.jpxdx.net
PortThe port number of that access point
UsernameThe access point login, not your account email
PasswordThe access point password, not your account password or PIN

Each access point is either HTTP or SOCKS5. Keep the phone online with Proxy ON while you use it.

Windows 10 and 11

01

Open proxy settings

Settings → Network & internet → Proxy → Use a proxy server → Set up.

02

Enter host and port

Turn on Use a proxy server, enter the host and port of an HTTP access point and save.

03

Sign in when asked

Edge and Chrome ask for the username and password the first time. Windows’ own settings don’t support SOCKS5 with a password, so for SOCKS5 use Proxifier or a setting inside the app.

macOS

01

Open network details

System Settings → Network → your Wi-Fi or Ethernet → Details… → Proxies.

02

Fill in the proxy

For an HTTP access point, turn on Web proxy (HTTP) and Secure web proxy (HTTPS). For SOCKS5, turn on SOCKS proxy. Enter the host and port, enable Proxy server requires password and add the username and password.

03

Apply

Click OK. Safari, Chrome and other apps that follow system settings now use the proxy.

Android (a second phone or tablet)

01

Open the Wi-Fi network

Settings → Wi-Fi → tap the gear (or long-press) on your current network → Edit or Advanced.

02

Set a manual proxy

Proxy → Manual. Enter the host and port of an HTTP access point and save.

03

Authenticate

Android’s Wi-Fi proxy setting has no password field. The browser will ask for the username and password; for other apps, use an app with its own proxy settings.

This is for a second device using your proxy. The phone running the JesusProxy app is the proxy itself and needs no proxy settings.

iPhone and iPad

01

Open Wi-Fi details

Settings → Wi-Fi → tap ⓘ next to your network → Configure Proxy.

02

Choose Manual

Enter the host and port of an HTTP access point, turn on Authentication, enter the username and password, and tap Save.

Chrome, Edge and Firefox

Firefox has its own setting: Settings → General → Network Settings → Manual proxy configuration. Enter an HTTP proxy, or a SOCKS host with SOCKS v5 and tick Proxy DNS when using SOCKS v5. Firefox asks for the username and password when you first browse.

Chrome and Edge follow the system proxy. To use the proxy only in the browser, or to switch quickly between access points, use a proxy extension such as FoxyProxy: add a proxy, choose HTTP or SOCKS5, enter host, port, username and password, and pick it from the toolbar.

Proxifier: route any desktop app

01

Add the proxy

Profile → Proxy Servers → Add. Enter host and port, choose HTTPS or SOCKS Version 5 to match the access point, enable authentication and enter the username and password. Click Check to test it.

02

Create a rule

Profile → Proxification Rules → Add. Pick the applications (or keep Any) and set the action to your new proxy.

03

Send DNS through the proxy

Profile → Name Resolution → Resolve hostnames through proxy, so DNS lookups don’t leave from your own connection.

Antidetect browsers

AdsPower, GoLogin, Dolphin Anty, Multilogin, Octo Browser and similar tools have a proxy section in every browser profile. Choose HTTP or SOCKS5, then enter the host, port, username and password (many accept host:port:username:password on one line). Use the built-in Check proxy button before launching the profile. Giving each profile its own access point makes traffic easy to tell apart.

curl, Python, Node.js and Playwright

curl -x http://USERNAME:PASSWORD@HOST:PORT https://api.ipify.org curl -x socks5h://USERNAME:PASSWORD@HOST:PORT https://api.ipify.org
import requests proxy = "http://USERNAME:PASSWORD@HOST:PORT" print(requests.get("https://api.ipify.org", proxies={"http": proxy, "https": proxy}, timeout=30).text)
// npm i undici import { fetch, ProxyAgent } from "undici"; const res = await fetch("https://api.ipify.org", { dispatcher: new ProxyAgent("http://USERNAME:PASSWORD@HOST:PORT") }); console.log(await res.text());
import { chromium } from "playwright"; const browser = await chromium.launch({ proxy: { server: "http://HOST:PORT", username: "USERNAME", password: "PASSWORD" }, }); const page = await browser.newPage(); await page.goto("https://api.ipify.org"); console.log(await page.textContent("body")); await browser.close();

If the password contains characters like @ or :, URL-encode it in proxy URLs (@ becomes %40).

Check that it works

  • Open api.ipify.org through the proxy. You should see the phone’s mobile IP, not your home or office IP.
  • The dashboard’s Proxy test checks the access point and measures speed and latency.
  • A 407 error or repeated password prompts mean the username or password is wrong, or the PIN was used by mistake.
  • Timeouts: confirm the Android app shows Connected and that the protocol matches the access point.

Common questions

Should I choose HTTP or SOCKS5?

Use HTTP for browsers, scrapers and most tools that ask for a web proxy. Use SOCKS5 for apps that support it, for non-web traffic, or when you want DNS resolved on the proxy side with socks5h.

Why does my browser keep asking for a password?

Chrome and Edge use the system proxy and prompt for credentials. To skip the prompt, use a proxy extension that stores credentials, Proxifier, or an antidetect browser profile.

Can I use the pairing PIN as the proxy password?

No. The PIN only pairs the Android phone. Your apps need the access point username and password from the dashboard.

Build your first mobile proxy

Start with one Android phone and a 48-hour free trial. No server setup, no coding, and no shared proxy pool.