Video summary

Каскадный ВПН на 3x-ui. Самый простой способ обхода ограничения трафика ВПН. Двойной ВПН сервер.

Main summary

Key takeaways

Technology

Key topic

Double / cascading VPN using 3x-ui (“cascade”): traffic first goes through an incoming server in Russia, and then non-Russian traffic is forwarded to an outgoing server abroad (example: Europe → final Internet).

Motivation / policy context (news)

The video references a proposed fee for traffic to foreign servers over 15 GB starting May 1 (Russia → foreign servers).

It argues this can be mitigated by:

  • Using a cascade so that:
    • Russian domains/IPs go directly
    • Foreign domains/IPs go via the “outgoing” VPN server
  • Optionally routing only selected traffic through the VPN at the client side (so not everything is tunneled), with the note that 15 GB is often not exceeded depending on usage.

Core technical concept (how the cascade works)

Setup roles

  • Incoming server (Russia): handles the “first hop”
  • Outgoing server (Europe/abroad): handles the “second hop” for foreign destinations

Routing logic (rule behavior)

  • Russian domains & Russian IPs → sent directly from the incoming server to Russian Internet
  • Non-Russian domains & non-Russian IPs → forwarded to the outgoing server, then to the external Internet

Performance note

Each additional hop increases ping and reduces speed, so the cascade can be extended to multiple servers if needed, but expect degradation.

Implementation guide: 3x-ui + server setup

Tools / access

  • Uses SSHTerminal Termius (multi-OS client) to connect to both VPS servers.

Servers required

  • Needs a Russian VPS for the incoming side
    • The author mentions using an inexpensive hosting provider (link in description).

Install 3x-ui

  1. Update packages (as described): bash apt update apt upgrade -y

  2. Install 3x-ui via the official GitHub quickstart script

  3. Panel SSL:
    • Script can enable SSL by domain / IP / custom cert
    • The author chooses SSL for IP (no domain/custom certificate)
  4. Important output:
    • Saves the panel URL + username/password
    • Recommendation: save it to a file

Repeat on the outgoing server

  • Run the same 3x-ui installation steps on the outgoing VPS.

Creating VPN nodes/connections in 3x-ui

You’ll configure two panels / two sides:

  • Incoming (Russia)
  • Outgoing (abroad)

On the outgoing server

  1. Create a connection using:
    • VLESS
    • port 443
    • TCP
    • Reality
  2. Configure:
    • A “foreign site not blocked” value (used as part of parameters)
    • Flow mode: XTS RPRX VISION
    • Sniffing kept off
  3. Generate and copy the connection link from this outgoing panel.

On the incoming server

  1. Create an outgoing connection that references the copied outgoing server link.
  2. Set up routing rules:
    • Network: TCP/UDP
    • Outbound tag: the created outgoing connection
  3. Add direct rules so Russian traffic bypasses the cascade:
    • “Direct IP addresses” → Russia
    • “Direct domains” → r.ru / r.f-style pattern (as written in subtitles; essentially Russian domain routing)
  4. Ensure rule order:
    • Russian domain/IP routing placed first
    • Outgoing forwarding rule placed appropriately after
  5. Apply and restart:
    • Save and restart X-Ray
    • (3x-ui uses X-Ray core)

Special step: selecting a “fake/cover” domain for Reality SNI

The setup uses “RealLS Scanner” (from the X-Ray ecosystem) to find websites near the server subnet to use as cover.

Procedure described

  • Download the tool via a GitHub releases command (subtitles show a WET-like command)
  • Make it executable:
    • chmod +X
  • Run it:
    • ./...
  • Choose a suitable domain from the scanned results
  • Set that domain in SNI / target fields for the incoming Reality connection

Alternative mentioned

  • Instead of using fake sites, you can create your own cover website on the VPN host machine (covered in a previous video).

Client configuration & testing (tutorial verification)

Connect and configure client

  • Connect using the generated configuration link/QR
  • Test routing using:
    • A browser/client “Global” mode
    • Enable system proxy
  • Check visible IP using 2ip.ru

Validation logic

  • On Russian domains (e.g., .ru, .c.ru as mentioned):
    • visible IP should be that of the incoming (Russian) server
  • On foreign domains (e.g., .com):
    • visible IP should be that of the outgoing server (abroad)

Outcome claimed

  • “Cascade of two VPN servers works correctly.”

Review / product analysis elements

The subtitles don’t include a comparative VPN product review. Instead, they act as a step-by-step tutorial for installing/configuring 3x-ui + X-Ray Reality cascade routing.

Main speakers / sources

  • Speaker: creator on the “Server Technologies” YouTube channel (not named in subtitles)
  • Software/project sources mentioned:
    • 3x-ui developers (official GitHub installation script)
    • X-Ray core / RealLS Scanner (utility referenced via GitHub)

Original video