Access to blocked sites by disguising traffic as ordinary HTTPS.

Prosvetech Proxy

What it is

Prosvetech Proxy over the VLESS Reality protocol. Reality disguises your traffic as an ordinary HTTPS connection to a large, popular website — from the outside it’s indistinguishable from a normal visit to a big site. Practically impossible to tell apart from legitimate HTTPS traffic.

Only the apps you pick go through Reality. It takes a bit more setup, but for resilience in tough network conditions it’s today’s best option.

How to set it up

  1. Send a direct message in the channel. The administrator exports a VLESS URL (vless://...) and sends it over a private channel or as a QR.
  2. Install a client with VLESS Reality support:
  3. Import the URL or QR into the client → turn the connection on. The client will show a list of apps you can route through the tunnel.
  4. Also recommended: set up Prosvetech DNS on the device. Reality hides the contents of your traffic, but DNS queries leak straight to your ISP by default — see the FAQ below.

FAQ

Does UDP traffic go through the proxy? No, Reality proxy is TCP-only. WebRTC video calls, online games, QUIC (HTTP/3), and other UDP-based applications don’t go through the proxy — they go directly through the device’s regular connection.

Why does the traffic look like ordinary HTTPS? Reality “borrows” the TLS handshake of a real, large website: to an outside observer the connection is indistinguishable from a normal visit to a big, popular site. Millions of devices hit such sites every second, so your request dissolves into the background noise of the network.

Can my ISP see what sites I open through Reality? Not fully. The traffic itself is encrypted and masqueraded as ordinary HTTPS to a large website — your ISP can’t see the contents. But there’s a catch: DNS queries (translating rutracker.org into an IP address) go from your device straight to your ISP’s DNS by default, bypassing Reality. Your ISP sees the list of domains you resolved, even if not what you did there.

To close this leak, set up our private DNS alongside Reality: Prosvetech DNS encrypts DNS queries with DoH/DoT and routes them through our server. Configured once per device, works regardless of whether Reality is on.

Can I use Reality together with MTProxy? Yes, they live on different layers: MTProxy is a setting inside Telegram itself, Reality (via Happ / Hiddify) is a system-wide tunnel over the VPN API. With both on in default mode, Telegram traffic gets wrapped twice (first through MTProxy, then again through Reality) — it works, with a bit of overhead. The optimal setup: in the Reality client’s routing settings, add Telegram to the exclude list so Telegram goes directly through MTProxy while everything else rides Reality. More detail on the MTProxy page FAQ.

Why do I need a separate client — why not just a system VPN? VLESS Reality runs on a client-proxy architecture: a local process accepts connections from apps and forwards them through the tunnel. The system VPN stack doesn’t speak this protocol.

Source code