Using a US Mobile IP from Abroad with a VLESS Tunnel

Plenty of our customers are not in the United States. They are running US accounts, checking US search results or testing US apps from Europe, Asia or Latin America, over hotel Wi-Fi, office networks and foreign carriers. A plain proxy login works from anywhere, but it sends your credentials and your traffic across all of those networks in a form they can inspect. The VLESS option on a USAProx line wraps everything in a tunnel that looks like an ordinary HTTPS connection until it reaches our server in the US, where it exits on your carrier IP. This guide is written for that traveller, with the phone first and the laptop second.

Why the tunnel matters more from overseas

Between your device and our rack there may be a hotel network, a foreign carrier and a national network with its own filtering. A SOCKS5 login is visible to each of them: the destination, the port and the credentials. Some networks block proxy ports outright. A REALITY tunnel presents itself as a normal TLS session to a large public website, so it passes through networks that would block a proxy, and nothing between you and our server can read what is inside.

Once the tunnel reaches our server, traffic goes to your modem and leaves on a real US carrier IP. Websites see a US phone on a US network, not a connection from abroad.

There is also a practical side. Hotel and conference networks are often built to allow web browsing and little else, and a proxy port that works from home simply times out from a hotel room. Because the tunnel uses the same handshake as any secure website, it works on those networks without asking anyone to open a port for you.

Copy the line from your dashboard

Sign in to the USAProx dashboard, open My proxies, and press the copy button on the VLESS / Xray row of your line. That vless:// string is the entire credential: server, port, your id and the REALITY details. Keep it private and use Revoke access on the card to reissue it if needed. VLESS is available on our server-based lines; tick VLESS / Xray in the filters when ordering or moving so the dashboard shows only locations that provide it.

iPhone and Android

1. iPhone: install V2Box or Streisand from the App Store. In V2Box open Configs, tap the plus button, choose Import from clipboard, select the line and connect. Allow the VPN configuration.
2. Android: install v2rayNG from Google Play. Tap the plus button, Import config from clipboard, select the line and tap the V button. Allow the VPN request.
3. On either phone, open a browser and load an IP check site. The IP should be a US carrier address in the city you ordered.
4. Leave the tunnel connected while you work. Rotation from the dashboard link changes the US IP without disconnecting the phone.

• V2Box on the App Store
• Streisand on the App Store
• v2rayNG on Google Play

Windows and Mac

1. Windows: download the With-Core zip from the v2rayN releases page, extract it, run v2rayN.exe and press Ctrl and V to import the line. Right-click it, Set as active server, then set System proxy in the bottom bar.
2. Mac: install V2Box from the App Store and import from the clipboard exactly as on iPhone, then connect.
3. On either, load an IP check site to confirm a US carrier IP. On Windows, Test real delay on the line gives the round trip to our US server, which from overseas will be higher than a local proxy and is expected.

• v2rayN releases

Settings that give away the location anyway

The tunnel fixes the network path. It does not touch what your device says about itself. If the goal is to appear as a US user, align these before you start:

• Time zone: set the device to the time zone of the line's city, not your local one.
• Language and region: US English, US region format.
• Browser WebRTC: on a laptop, use a browser or extension that disables WebRTC leaks, or the site can learn your local address.
• Location services: switch them off for the apps you are testing, or the GPS position overrides the IP.

When it will not connect from where you are

If the tunnel connects on one network and not on another, the failing network is blocking the port in your link; ask support for a line served on port 443, which is the same port every HTTPS site uses. If nothing connects anywhere, check the device clock against real time, since the REALITY handshake needs an accurate date and travellers often carry a clock set to the wrong zone with automatic time off. If the client reports an invalid user id, the line was moved or switched since you copied it; copy the current link from the dashboard.

Frequently asked