VLESS Over Your Dedicated Modem: Setup Guide

Every line comes with HTTP and SOCKS5 ports, and for browsers and scripts those are enough. Some work needs more: a whole phone tunnelled, apps that ignore proxy settings, a network that interferes with plain proxy ports, or simply encryption between you and the modem. For that, each line can also be used through VLESS. This guide explains what VLESS is, when it is the better choice, and how to set it up in three common clients.

What VLESS is

VLESS is a lightweight proxy protocol from the Xray and V2Ray family. A client on your device opens one encrypted connection to a VLESS server, and everything the device sends, TCP and UDP alike, travels inside that connection and exits at the far end. In our case the far end is your modem, so the exit address is the same carrier address your HTTP and SOCKS5 ports use. The difference is on your side: instead of configuring a proxy in each application, the client captures all traffic at the system level.

The protocol itself has no built-in encryption, so it is run over TLS. Your credentials are a UUID in the link rather than a username and password.

When to use it instead of HTTP or SOCKS5

Use VLESS when you want the entire device on the modem: a phone whose apps do not honour proxy settings, a laptop where you would rather not configure every tool, a test of how an app behaves on a cellular network. Use it when the network you are on blocks or inspects plain proxy ports, since VLESS over TLS looks like ordinary HTTPS. Use it when you want encryption to the modem on a network you do not trust.

Keep using HTTP or SOCKS5 when the proxy is going into a profile browser, a script or a single tool, when you want per-application control, or when the tool simply has a proxy field. For most desktop account work the plain ports are the simpler choice.

Getting the link from the dashboard

Open your line at desk.dedicatedmobileproxies.com. Alongside the HTTP and SOCKS5 details there is a VLESS link beginning with vless:// and a QR code of the same link. The link encodes the server, the port, your UUID and the transport settings. Copy it on a computer, or scan the QR on a phone. Treat it like a password: anyone with the link can use your modem.

v2rayN on Windows

Install v2rayN and open it. Use the servers menu to import from clipboard after copying the vless:// link, or scan the QR from the screen. The new server appears in the list; select it and set it as active. In the bottom bar choose the system proxy mode, which sets Windows to route through v2rayN. Then open a browser and load an IP lookup page; it should show a US mobile carrier in your modem's metro. If it shows your own address, the system proxy mode is not on, or another proxy tool is taking precedence.

v2rayN also exposes a local SOCKS and HTTP port, so tools that want a proxy field can point at localhost and still exit through the modem.

Shadowrocket on iPhone

Open Shadowrocket, tap the add button, and choose scan QR code, pointing the camera at the dashboard, or paste the link from the clipboard. The server appears in the list. Tap it to select it, then switch the connection toggle on; iOS will ask once to add a VPN configuration, which is how the app captures all traffic. Set the routing mode to proxy everything if you want the whole phone on the modem, or use the config rules for a split. Open Safari and check the address. Every app now exits through your modem, including those with no proxy setting.

Hiddify on Android and elsewhere

Hiddify runs on Android, Windows, macOS and Linux. Install it, tap the add profile button, and either scan the QR or paste the vless:// link. Select the profile and press connect. On Android it registers as a VPN, so the system shows a key icon while it is active and every app is tunnelled. Check the address in a browser. Hiddify also shows a latency figure per profile; a few tens of milliseconds more than your direct connection is normal, because the traffic is going to the modem's city first.

Checking speed

Run a speed test through the tunnel and compare it with the HTTP port from the same place. Expect the same ceiling, which is the modem's radio: 4G lines usually run 20 to 45 Mbps, 5G 50 Mbps and up. Expect a little extra latency from the TLS layer and from any distance between you and the modem's city. If VLESS is far slower than the plain port, the client is probably routing DNS or part of the traffic somewhere else; check the routing mode. If both are slow, the modem's signal is the limit, and support can look at the device.

Frequently asked