Set Up a Dedicated Mobile Proxy in Five Minutes

Your modem is ready the moment the payment clears. The rest is five minutes of copying values into the right boxes. This walk-through goes from the dashboard to a confirmed connection on a desktop browser, a phone and the command line, in that order. Read the part you need and skip the rest.

Minute one: the dashboard

Sign in at desk.dedicatedmobileproxies.com and open your line. The page shows five things you will need: the host, an HTTP port, a SOCKS5 port, a username and a password. It also shows the carrier, the city, the current public address, a rotate button and a rotation link you can call from scripts. Keep this page open; everything below copies from it.

If you bought more than one line, each has its own row and its own ports. The host is usually the same for lines in one city, the ports are not, so copy them per line.

Minute two: HTTP or SOCKS5

Both ports lead to the same modem and the same address. Use the HTTP port for browsers, browser extensions and most web tools; it is the one almost everything supports. Use the SOCKS5 port when the application speaks SOCKS, when you need UDP, or when you are tunnelling something that is not web traffic. Our SOCKS5 carries UDP, which matters for some apps and for tools that resolve DNS through the proxy.

Do not configure both in the same application. Pick one port per tool.

Minute three: a desktop browser

For a profile browser such as Undetectable.io or GoLogin, create a profile, open its proxy settings, choose HTTP or SOCKS5 to match the port, paste host, port, username and password, and press the built-in check. It should name a US carrier and your modem's metro. Then set the profile's time zone to that city and save.

For an ordinary browser, install a proxy extension, add a proxy entry with the same four values, and switch it on. Chrome itself has no per-profile proxy setting, so the extension is the simplest route. In Firefox you can type the values directly into the network settings. Either way, disable WebRTC or use the extension's WebRTC protection, otherwise a site can learn your home address through it.

Minute four: a phone

On an iPhone, Wi-Fi settings allow a manual HTTP proxy per network: open the current Wi-Fi network, scroll to HTTP Proxy, choose Manual, enter the host and HTTP port, turn on authentication and enter the username and password. Apps that respect system proxy settings, which is most of them, will now exit through your modem. For a whole-device tunnel including apps that ignore proxy settings, use the VLESS link from the dashboard in Shadowrocket instead.

On Android, long-press the Wi-Fi network, open advanced options, set Proxy to Manual, and enter host and port. Android's built-in setting has no field for a password, so either whitelist your home address in the dashboard so the line accepts you without credentials, or use a VLESS client such as Hiddify, which handles authentication itself.

Minute five: curl and a real check

On any computer with curl, run a request through the line and print the address it exits from. The form is: curl -x http://USERNAME:PASSWORD@HOST:HTTPPORT https://api.ipify.org and the response should be a single address that is not your own. For SOCKS5, replace http:// with socks5h://, with the SOCKS5 port. The h in socks5h makes the proxy resolve the hostname, which is what you want.

Then look the address up. Any public IP lookup will show a US mobile carrier as the owner and your modem's metro as the location. If it shows a different city within the same region, that is the carrier's gateway placement, not a fault; the carrier pages on this site explain the quirks per carrier.

Before you start working

Three settings save trouble later. Set the browser or device time zone to the modem's city. Set the language to US English unless the account expects otherwise. And decide your rotation habit now: rotate between sessions from the dashboard or by calling the rotation link, never while an account is signed in. If anything in these steps does not behave, write to [email protected] or message the Telegram bot and a person will check the line with you.

If something does not connect, check the three usual causes in order: the credentials were pasted with a trailing space, the tool is pointed at the HTTP port while set to SOCKS5 or the other way round, or a firewall on your side blocks outbound connections to the proxy port. Support can see from its side whether your modem has received a single connection attempt, so write to us with the time of the test and we will tell you where it stopped.

Frequently asked