EQVPS

VPS for VLESS + Reality (bypass DPI)

Self-host a VLESS + Reality proxy on your own VPS — traffic looks like ordinary HTTPS to a real site, so deep packet inspection in Iran, China and Russia can't fingerprint it. Dedicated IP, crypto payment, no KYC. From $8/mo.

WireGuard and OpenVPN are excellent VPNs and terrible at hiding that they're VPNs. In Iran, China and Russia, deep packet inspection (DPI) recognises their handshakes and blocks them — often within minutes of first use. VLESS + Reality, from the Xray project, solves this differently: instead of encrypting a VPN handshake, it impersonates the TLS handshake of a real, popular HTTPS website. To DPI, your connection looks exactly like someone visiting an ordinary site on port 443. There is no VPN fingerprint to match.

Running it on a VPS you control — paid in crypto, no KYC — gives you a private, censorship-resistant endpoint that's yours alone.

What Reality needs

Honest scope

This is a censorship-resistant private endpoint you control — not anonymity. No-KYC means we don't ask who you are; it does not make traffic anonymous, and no single IP is guaranteed to survive forever in the most aggressive networks. Reality defeats DPI-based blocking; it is not protection against a global traffic-analysis adversary.

Set up VLESS + Reality (Ubuntu 24.04)

# dedicated-IP plan, root shell
bash -c "$(curl -L https://github.com/XTLS/Xray-install/raw/main/install-release.sh)" @ install

# generate a Reality key pair (save both keys)
xray x25519

# generate a short ID
openssl rand -hex 8

Edit /usr/local/etc/xray/config.json — a minimal VLESS + Reality inbound:

{
  "inbounds": [{
    "listen": "0.0.0.0",
    "port": 443,
    "protocol": "vless",
    "settings": { "clients": [{ "id": "PASTE-A-UUID", "flow": "xtls-rprx-vision" }], "decryption": "none" },
    "streamSettings": {
      "network": "tcp",
      "security": "reality",
      "realitySettings": {
        "dest": "www.microsoft.com:443",
        "serverNames": ["www.microsoft.com"],
        "privateKey": "PRIVATE-KEY-FROM-x25519",
        "shortIds": ["SHORT-ID"]
      }
    }
  }],
  "outbounds": [{ "protocol": "freedom" }]
}
xray uuid                       # generate the client UUID for the config above
systemctl enable --now xray
systemctl status xray

Build the VLESS link from your UUID, public key, dest and short ID, then import it into v2rayNG (Android), Nekoray (desktop) or sing-box (iOS/everywhere). Choose a dest that's a large, always-up HTTPS site not itself blocked in your region.

Why EQVPS for anti-censorship

Full step-by-step setup guide →

Ready to deploy? Pay with crypto, no KYC — live in about a minute.

Deploy now →

FAQ

VLESS + Reality vs WireGuard — which bypasses DPI?

Reality. WireGuard and OpenVPN have recognisable handshakes that deep packet inspection detects and blocks in Iran, China and Russia. A VLESS + Reality connection borrows the TLS handshake of a real, popular HTTPS site, so on the wire it looks like ordinary web traffic — there's no VPN signature to fingerprint.

How do I set up Reality on a VPS?

Install Xray, generate a Reality key pair, point the config at a real 'borrowed' site (dest), open port 443, and import the VLESS link into your client (v2rayNG, Nekoray, sing-box). The steps are below; you get root in about a minute. A dedicated IP is required so the server has its own inbound 443.

Why does Reality need a dedicated IP?

Reality answers inbound on port 443 with its own public address — it must own the IP:443 endpoint. Our NAT plans don't accept inbound web traffic, so take a dedicated-IPv4 plan (Nano-IP from $8/mo is enough for personal use).

Is this anonymity?

No — it's a censorship-resistant private endpoint you control. No-KYC means we don't ask for your identity; it does not make the connection anonymous. Honest scope: this defeats DPI-based blocking, not traffic analysis by a global adversary.

Do you ask for ID or a card?

No. Email to register, USDC or USDT to pay. No documents, no card, no KYC.

Comments

No comments yet. Be the first.

Leave a comment

Comments are moderated before they appear.