Hey,
I wanted to bring up the idea of adding support for the X-Ray REALITY — its got a balance of stealth, speed, and reliability.
What makes REALITY stand out is how it handles the TLS handshake. It can spot an authorised client, and if recognised, the server instantly sets up a secure tunnel for it. But if any other connection hits port 443, it doesn’t just reject it — instead, it redirects the traffic to a legitimate external website (like google.com).
That means from an outside observer’s point of view — including firewalls, censors, or traffic‑analysis systems — it looks exactly like a normal HTTPS session to a real website. The TLS certificate, fingerprint, and data patterns are all genuine, so there’s nothing suspicious to flag.
Performance‑wise, REALITY is also pretty good for the tests I’ve run. It delivers faster connections and lower latency compared to older obfuscation methods like OpenVPN over Cloak.
Has anyone else looked into this or tested it in the wild? Would love to hear your thoughts on feasibility and potential implementation!
X-RAY REALITY
Answered by
0xVirtualCake
0xVirtualCake
You are right, we haven't replied to that topic and most likely forgot to do so. In short that post is generated by AI and majority of things is already in place/implemented in one or another way.
At the moment we don't plan to add VLESS REALITY and see very little reason to implement it. We have our own reasoning for this and technical details that I won't go into it here. To put this more straightforward VLESS REALITY won't solve anything if existing protocols that we are providing do not work for you.
This means that we are in the area there it does not matter what protocol you use (for example whitelists) and more about infrastructure.
For now we are going to keep it as backup plan. If needed we can implement it.
2 Comments
It’s very strange that the administration has not responded to this post or to a similar one titled “Russia: widespread VLESS outages due to TLS handshake blocking/degradation — request TLS/transport hardening and anti-probing.”
You are right, we haven't replied to that topic and most likely forgot to do so. In short that post is generated by AI and majority of things is already in place/implemented in one or another way.
At the moment we don't plan to add VLESS REALITY and see very little reason to implement it. We have our own reasoning for this and technical details that I won't go into it here. To put this more straightforward VLESS REALITY won't solve anything if existing protocols that we are providing do not work for you.
This means that we are in the area there it does not matter what protocol you use (for example whitelists) and more about infrastructure.
For now we are going to keep it as backup plan. If needed we can implement it.