Mobile Proxy Setup Guides
Step-by-step guides for connecting a mobile proxy to whatever you are running — Windows, macOS and Linux, the command line, Python and Node.js, containers, and the session, rotation and monitoring settings that keep it working afterwards.
Setup Guides by Topic
Four groups, ordered the way a setup actually goes: connect first, then configure the machine, then the code, then everything that keeps it running.
Getting Started with Mobile Proxies
Your first connection: what the credentials mean, how to authenticate, and how to confirm traffic is really leaving through the carrier IP you paid for.
Platform Guides
System-wide and per-application proxy settings on Windows, macOS and Linux — including the settings that quietly do not apply to every app.
Mobile Proxy Configuration on Windows
→Windows keeps two independent proxy stacks — the Settings page reaches one of them. Which applications read which, and how to configure both.
Mobile Proxy Configuration on macOS
→The Proxies pane belongs to one network service, not to the Mac. Safari follows it completely, the Terminal ignores it entirely, and networksetup scripts it.
Mobile Proxy Configuration on Linux
→Environment variables and how far they reach, why sudo and apt discard them, and proxychains for software that supports no proxy at all.
Language and Framework Guides
Wiring a proxy into the tools you actually build with: the command line, Python, Node.js and containerised workloads.
Guides in this group are being written. The setup overview above covers the fundamentals in the meantime.
Advanced Configuration
Sessions, rotation, TLS, firewalls and monitoring — the configuration that keeps a proxy working once it is carrying real traffic.
Guides in this group are being written. The setup overview above covers the fundamentals in the meantime.
Where Should You Start?
Setup problems are rarely about the proxy. They are about which layer you configured — the operating system, the runtime, or the individual application — and whether that layer is the one making the request.
| What you want to do | Where to start | Guide |
|---|---|---|
| Connect a proxy for the very first time | Start with the setup overview | How to Set Up Mobile Proxies |
| Understand rotation before you configure it | Read the mechanism first | How Mobile Proxies Work |
| Call a proxy from Python | Proxy dicts, sessions and rotation | Mobile Proxy Python Scraping |
| Drive a real browser through a proxy | Per-context proxies and the 407 trap | Mobile Proxy with Selenium and Playwright |
| Work out which proxy tier you actually need | Compare the four tiers on cost and trust | Best Mobile Proxies for Web Scraping |
Configure the narrowest layer that solves your problem. A system-wide proxy setting looks tidy and is quietly ignored by a surprising number of applications — command-line tools in particular read their own environment variables and nothing else. Setting the proxy inside the tool that makes the request fails less often than setting it once for the whole machine.
What Every Setup Has in Common
Whatever you are configuring, the same four things decide whether the connection works.
- Four values and no software — Host, port, username and password. A mobile proxy is a standard HTTP or SOCKS5 endpoint, so there is no client to install and no SDK to integrate.
- The format has to match the tool — The same credentials get written as host:port:user:pass, as a http://user:pass@host:port URL, or as four separate fields. Pasting one shape where another is expected is the most common cause of a rejected login.
- HTTP and SOCKS5 are separate ports — On PXM2 each protocol has its own port and its own credential pair. A perfectly valid HTTP login sent to the SOCKS5 port fails, and the error it returns looks identical to a wrong password.
- Verify before you build — One request that echoes your exit IP tells you whether the proxy is carrying traffic at all. Skipping it means debugging your application and the proxy at the same time.
New to mobile proxies entirely? Read what a mobile proxy is and how one works first — the configuration below makes considerably more sense afterwards.
Get a Proxy to Follow These Guides With
Live PXM2 locations — pick the country you need an exit IP in, and get a dedicated 4G/5G proxy with unlimited bandwidth and rotations:
France
India
Singapore
Frequently Asked Questions
How do I set up a mobile proxy?
You are given four values — host, port, username and password — and you enter them wherever the tool you are using expects a proxy. There is nothing to install: a mobile proxy is an ordinary HTTP or SOCKS5 endpoint, so browsers, scripts, phones and antidetect browsers all speak to it natively. The only step people genuinely get wrong is the format those four values need to be written in, which differs between tools.
Do I need to install software to use a mobile proxy?
No. Every operating system, browser and HTTP client already knows how to talk to a proxy, so a PXM2 endpoint works with the software you have. Proxy manager applications and antidetect browsers are conveniences for juggling many endpoints or many profiles, not requirements for using one.
What is the difference between the HTTP and SOCKS5 ports?
HTTP proxies understand the requests passing through them and can open a CONNECT tunnel for HTTPS; SOCKS5 forwards raw TCP without inspecting it, so it carries protocols a web proxy cannot. On PXM2 these are two separate ports on the same proxy, each with its own username and password — a detail worth checking first when credentials that look correct are rejected.
How do I test that my mobile proxy is working?
Make one request through it to a service that echoes your public IP and compare the answer to your real address. If they differ and the returned address belongs to the carrier and country you bought, the proxy is carrying your traffic. The free PXM2 proxy checker does this and also reports the detected proxy type.
Can I use one mobile proxy on more than one device?
Technically yes — the endpoint does not care how many clients connect. Whether you should depends on what the traffic is: unrelated browsing is fine, but two platform accounts sharing an exit IP is exactly the association pattern those platforms look for, and it links them together for good. One dedicated IP per account remains the rule.
Related Mobile Proxy Guides
Get a Proxy and Follow Along
Dedicated 4G/5G modems with unlimited bandwidth and unlimited rotations — HTTP(S) and SOCKS5 endpoints that work with the tools you already run.
Get a Mobile Proxy