Your proxy is one address and one port. What differs is where you type it — and a few places where the obvious way does not work.
Your account page shows a host and a port. Together with the username and password shown in the Mproxies app on your phone, that is everything:
Host 45.76.179.249
Port 20001
Username (shown in the app)
Password (shown in the app)
The same address works as SOCKS5 and as HTTP. Which one to use is not a preference — some software only supports one, and one of them has a trap worth knowing about before you meet it:
user:pass@ in
front of a SOCKS5 address and it fails silently, with no error to tell you why.
In Chrome-based tools, use HTTP — or use SOCKS5 with IP whitelisting
instead of a password.
AdsPower, Dolphin Anty, GoLogin, Undetectable, Incogniton. All of them take the same four fields.
If your browser profile presents itself as a phone — a mobile user agent, a phone screen size, touch events — then the IP it arrives from should belong to a mobile network. Real phones do not browse from data-centre or fixed-line addresses, and a profile claiming to be a phone on a fixed-line IP is describing something that does not exist. Matching them is the whole reason to use a mobile proxy for this rather than a cheaper kind.
The reverse is also true, and worth saying: if your profile presents as a desktop, a mobile IP is the mismatch. Use the right tool for the profile.
45.76.179.249 Port: 20001Dolphin will not let you finish a proxy without this field. Paste the rotation link from your account page — it changes the phone's mobile IP when opened, and Dolphin calls it when you ask for a new IP.
LDPlayer, BlueStacks, NoxPlayer, MuMu. One proxy per instance is the point — each instance looks like a separate device on a separate connection.
Neither exposes a per-instance proxy in the interface. Two ways round it:
To use the proxy on another phone — for messaging apps, or to check what a Malaysian visitor sees — install a tun2socks app on it:
curl -x socks5h://USER:PASS@45.76.179.249:20001 https://ipinfo.io/json
Note socks5h, not socks5: the h makes
DNS resolve at the proxy. Without it your own resolver looks up every domain you
visit, which both leaks where you are and can send you to a different server than
a Malaysian visitor would reach.
pip install requests[socks]
proxies = {
"http": "socks5h://USER:PASS@45.76.179.249:20001",
"https": "socks5h://USER:PASS@45.76.179.249:20001",
}
requests.get("https://ipinfo.io/json", proxies=proxies)
Use the HTTP port. Chromium will not send credentials over SOCKS5 — this is the limitation described at the top, and it fails without an error message.
browser = playwright.chromium.launch(proxy={
"server": "http://45.76.179.249:20001",
"username": "USER",
"password": "PASS",
})
Scrapy does not support SOCKS at all. Use the HTTP endpoint with
HttpProxyMiddleware.
Three ways, all doing the same thing — asking the phone to reconnect to the mobile network so the operator hands it a new address:
Something is bypassing it — usually DNS. Use socks5h rather than
socks5, and in a browser turn off "secure DNS" / DNS-over-HTTPS,
which routes lookups around the proxy by design.
Switch from SOCKS5 to HTTP. Chromium does not send proxy credentials over SOCKS5 and gives no error saying so — it simply does not connect.
A mobile proxy is slower than a fixed line, and honestly so: your traffic travels to our relay, through the tunnel to your phone, and out over 4G. Signal strength on the phone matters more than anything else — a phone by a window with three bars will beat one in a drawer with one. If it is unusably slow, tell us the speed you measured and we will look at it with you rather than explain it away.
Check the traffic figure on your account page. At the monthly limit a port pauses until the 1st, and your other ports keep running. Email us and we will raise the limit — we would rather change a number than have you stuck.