VLESS for an Illinois Line on Your Phone and Laptop

Every Illinois Proxies line can be reached over HTTP(S) and SOCKS5, and for many customers that is all they need. VLESS is the third option, and it is the one to use when you want the whole device, phone or laptop, to leave through your Illinois line rather than a single browser profile. The protocol is carried by Xray-based clients on every common platform, the link is shown on the line's page in your dashboard, and the setup takes a few minutes. This guide shows the link format with placeholders, gives a minimal Xray configuration for people who prefer a file, walks through the client setup on phone and laptop, and lists the checks to run before you trust it.

What VLESS gives you that a proxy setting does not

A browser proxy setting routes that browser. A system proxy setting routes applications that honour it, which on a phone is not all of them. A VLESS client installs a local tunnel and routes the device's traffic through it, so a mobile app, a desktop tool and a browser all leave through the Illinois line at once, with the same carrier address and the same Illinois reading. That is useful when the work involves an app that has no proxy setting of its own, or when you want a laptop to behave, from the network's point of view, like a device tethered to an Illinois phone.

VLESS carries UDP as well as TCP, so the tunnel also suits applications that use UDP, within the same fair-use understanding that applies to the whole line.

The link from your dashboard

Open the line in the dashboard at il.illinoisproxies.com and copy the VLESS link. It has the shape shown below, with your real values in place of the placeholders. Keep it private: the link is a credential.

The fragment after the hash is only a display name for the client. The uuid, host and port are what matter, and the remaining parameters tell the client how to reach the endpoint. Use the link exactly as the dashboard shows it; do not edit parameters unless support asks you to.

vless://<uuid>@<host>:<port>?encryption=none&security=none&type=tcp#Illinois-line

Phone setup: Android and iOS

On Android, v2rayNG is the usual choice; on iOS, any App Store client that supports VLESS and Xray will do. Both accept the link by paste or by scanning a QR code shown in the dashboard. Before you start, set the phone's time zone to Central and its language to English (United States) if the work depends on consistency.

1. Install a VLESS-capable client from the official app store for your phone.
2. Copy the VLESS link from the dashboard, open the client, and choose the option to import from clipboard, or scan the dashboard's QR code.
3. Select the imported profile and start the tunnel; accept the system prompt to create a VPN connection, which is how the client captures the device's traffic.
4. Open a page that shows your public address and confirm it is a carrier address resolving to Chicago, Illinois.
5. If the client offers per-app routing, leave it off for now so the whole phone uses the line; restrict it later once everything works.

Laptop setup: Windows, macOS and Linux

On Windows, v2rayN imports the same link and provides a system proxy or a tunnel mode. On macOS and Linux you can use a graphical client or run Xray core directly with a configuration file. The file below is the minimum for a local SOCKS5 listener on your laptop that forwards everything to the Illinois line; applications then point at 127.0.0.1 on the local port.

Replace the placeholders with the values from your link. The local port is yours to choose; the remote host, port and uuid are the line's.

1. Install the client or Xray core for your operating system from its official source.
2. Import the VLESS link, or save the configuration above as a file with your values filled in and start Xray with it.
3. Point your browser or system proxy at 127.0.0.1 and the local port you chose, or enable the client's tunnel mode to route the whole machine.
4. Load an address-lookup page and confirm the carrier, region and city.
5. Set the laptop's clock to Central time so the address and the device agree.

{

  "inbounds": [{

    "port": <local-port>, "listen": "127.0.0.1", "protocol": "socks",

    "settings": { "udp": true }

  }],

  "outbounds": [{

    "protocol": "vless",

    "settings": { "vnext": [{

      "address": "<host>", "port": <port>,

      "users": [{ "id": "<uuid>", "encryption": "none" }]

    }] },

    "streamSettings": { "network": "tcp", "security": "none" }

  }]

}

Checks before you rely on it

A tunnel that is almost working is worse than one that is clearly broken, because traffic can leak around it without any error. Run these checks on first setup and after any client update.

• Public address is an AT&T, T-Mobile or Verizon mobile address reading Chicago, Illinois.
• DNS lookups go through the tunnel: a DNS leak test shows resolvers belonging to the proxy path, not your home ISP.
• WebRTC in the browser shows no address or the proxy address.
• Time zone reported by the browser is America/Chicago.
• Stopping the tunnel makes pages fail or show your home address, which proves the tunnel was carrying them.
• Rotating from the dashboard changes the address shown, and the tunnel reconnects on its own.

Rotation, sticky sessions and support

VLESS does not change how the line's address behaves. It stays sticky as long as the carrier keeps the session, and you rotate from the dashboard, the rotation link, the API or a timer exactly as with HTTP or SOCKS5. If the tunnel drops after a rotation, most clients reconnect within seconds; if yours does not, toggle it off and on.

If something does not match the checks above, write to [email protected] or message @IllinoisProxiesBot with the client you used, your operating system and what the lookup page showed. We answer around the clock, and a VLESS problem is usually a mistyped value or an outdated client.

Frequently asked