Connect Your Mobile Proxy over VLESS and Xray on Any Device
Every GlobalProxies line that runs on our rack hardware can be reached two ways: as a plain HTTP or SOCKS5 proxy with a username and password, or as a VLESS line served by Xray. The VLESS option wraps the same modem in an encrypted tunnel that looks like ordinary HTTPS to anyone watching the connection, and it lets a whole device or a whole machine use the line without configuring each application. This guide walks through the setup on each platform we support customers on, in the order we would do it ourselves, and ends with the checks we ask for when a ticket says it is not working.
Where the line is and what it contains
Sign in to the dashboard and open My proxies. On a line that supports it, the card shows a row labelled VLESS / Xray with a long string that starts with vless:// and a copy button beside it. That string is the whole credential. It carries the server address and port, a unique user id, the security mode (REALITY), the server name the tunnel imitates, a public key and a short id. You never need to type any of those into an app by hand; every client reads them from the link.
Treat the link like a password. Anyone who has it can use your line until the id is changed. If you share it with a teammate and later need to cut their access, use Revoke access on the card, which issues a new id and makes the old link useless.
Not every line offers VLESS. It is available on our server-based lines and not on handset-based lines, and some carriers on some racks do not run it. When you buy or move a line, tick VLESS / Xray in the filters so the dashboard only offers locations that provide it.
Windows with v2rayN
v2rayN is the client we recommend on Windows. It is a portable program, there is no installer, and it bundles the Xray core.
- Download the zip named v2rayN-windows-64-With-Core from the project's releases page and extract it to a folder such as C:\v2rayN.
- Run v2rayN.exe. If SmartScreen appears, choose More info and then Run anyway.
- Copy the vless:// link from the dashboard, then in v2rayN press Ctrl and V together. The server appears in the list with the name from the end of the link.
- Right-click the server and choose Set as active server.
- In the bottom bar, set System proxy to Set system proxy. Every program that respects Windows proxy settings now goes through the line.
- Right-click the server and choose Test real delay. A latency in milliseconds means the tunnel is up.
macOS and iPhone with V2Box
V2Box is a free App Store client that runs on both macOS and iOS, so the steps are the same on a MacBook and an iPhone. Streisand is a good alternative on iOS if you prefer it.
- Install V2Box from the App Store and open it.
- Copy the vless:// link from the dashboard. In V2Box open Configs, tap the plus button, then Import from clipboard.
- Tap the new entry so it is selected, then press the connect button.
- The system asks to add a VPN configuration the first time. Allow it. On iPhone confirm with Face ID or your passcode.
- A VPN badge appears in the menu bar or status bar. The device is now routed through the line.
Android with v2rayNG
v2rayNG is by the same maintainer as v2rayN and behaves the same way. It is on Google Play and also published as an APK for devices without Play services.
- Install v2rayNG and open it.
- Copy the vless:// link. Tap the plus button in the top corner and choose Import config from clipboard.
- Tap the server so it is highlighted.
- Tap the round V button at the bottom. Android asks for VPN permission; tap OK.
- A key icon in the status bar shows the tunnel is active. Long-press the server row to run a connection test.
Linux and servers with xray-core
On a server there is no GUI, so run the Xray core directly. The config below opens a SOCKS5 listener on port 1080 and an HTTP listener on 1081 on the local machine and sends everything through the line. Fill in the values from your link: the part before the at sign is the id, the host and port follow it, and sni, pbk, sid and fp are the query parameters.
{
"inbounds": [
{"listen": "127.0.0.1", "port": 1080, "protocol": "socks", "settings": {"udp": true}},
{"listen": "127.0.0.1", "port": 1081, "protocol": "http"}
],
"outbounds": [{
"protocol": "vless",
"settings": {"vnext": [{"address": "HOST", "port": PORT,
"users": [{"id": "UUID", "encryption": "none", "flow": "xtls-rprx-vision"}]}]},
"streamSettings": {"network": "tcp", "security": "reality",
"realitySettings": {"serverName": "SNI", "fingerprint": "chrome",
"publicKey": "PBK", "shortId": "SID"}}
}]
}
xray run -c config.json
curl -x socks5h://127.0.0.1:1080 https://ifconfig.me
Proving it works, and what to check when it does not
With the tunnel connected, open a browser and load an IP check site, or press the Status link on the dashboard card. The address shown should be the carrier IP of your line, not your own connection. Rotation is unchanged: press the rotation link or call the API exactly as before, and the tunnel keeps running while the modem takes a new address.
If the app connects but nothing loads, check the device clock. REALITY handshakes fail when the clock is more than a couple of minutes off. If the tunnel connects but you still see your own IP, the client is running without the system proxy or VPN mode switched on. If the client reports an invalid user id, the line was moved or its modem was switched since you copied the link; copy the current link from the dashboard again.
Frequently asked
Is the VLESS line a different proxy from my HTTP and SOCKS5 login?
No. It is the same modem and the same carrier IP reached through a different door. Rotation, sticky sessions and the status link all behave the same way.
Can several people on my team use one VLESS link?
Technically yes, since the link is the credential. Keep in mind that everyone sharing it shares the same connection limit, and that revoking access changes the link for everyone at once.
Why does my line have no VLESS row?
The line is on hardware or a carrier that does not run Xray. Move it to a location that does, ticking VLESS / Xray in the move filters, or buy a new line with that filter set.
Does the app need the SOCKS5 password as well?
No. The vless:// link already contains a unique id that identifies you. The username and password are only for the plain HTTP and SOCKS5 endpoints.