VLESS Reality not working: 7 causes and the fix for each
VLESS with Reality stops working for one of seven reasons, and the error text in the app tells you which. The most common three are a client older than Xray core 1.8, a key copied with a wrong sni or pbk value, and a network that interrupts the TLS handshake. Work through the list below in order; each check takes under a minute.
1. The client is too old
Reality needs Xray core 1.8.0 or newer, or sing-box 1.3 or newer. The 404 VPN apps, Happ, v2rayTun and other current clients include it. If the app shows an error like unknown security: reality or invalid transport, update the app. Very old clients can also be refused by servers running a current Xray core, which rejects outdated client versions on purpose.
2. A field in the key is wrong
A Reality link has four values that must match the server exactly: sni, pbk (the public key), sid (the short ID) and fp (the browser fingerprint). Open the entry in the app and compare each with the key in the VPN tab of your dashboard. The typical damage is a chat app that turned the link into a preview and dropped a character. Delete the entry and import the key again by QR code, which cannot be altered in transit.
3. The device clock is off
Reality verifies a TLS certificate chain for the camouflage site, and a clock that drifts by more than a few minutes makes verification fail. The app shows certificate has expired or x509: certificate is not yet valid. Enable automatic time in the system settings and reconnect.
4. The network interrupts the handshake
Some corporate and campus networks inspect the TLS Client Hello and reset connections to unknown destinations. Reality fails with EOF or connection reset by peer right after Connect. Switch to the WebSocket entry of the same location in the server list: it is an ordinary TLS connection on port 443 through a web server. If that works, the network is the cause, and Reality will keep failing there.
5. The Reality port is blocked
Some guest and office networks allow outbound connections only to ports 80 and 443, while Reality entries often run on another port. The app shows dial tcp: i/o timeout on the Reality entry. Use the WebSocket entry, which runs on port 443.
6. Another VPN is holding the tunnel
On iOS and Android only one VPN profile can be active. If a second app still has its profile installed, the first connects and then immediately disconnects. Remove the other app's profile: iOS Settings, General, VPN & Device Management; Android Settings, Network & internet, VPN.
7. The server is actually down
Our backend checks the servers every few minutes and the team is alerted if one stops answering, so this is the least likely cause, but the quickest to rule out: switch to another entry or another location. If that connects, the first one is the problem and we are already on it.
Reading the error text
| App shows | Cause | Fix |
|---|---|---|
unknown security: reality | old client | update the app |
certificate has expired | clock drift | enable automatic time |
EOF right after connect | handshake filtered | use the WebSocket entry |
connection reset by peer | handshake filtered | use the WebSocket entry |
dial tcp: i/o timeout | Reality port blocked | use the WebSocket entry |
| connects, then disconnects | another VPN profile | remove the other profile |
invalid short id | key altered in transit | re-import by QR |
FAQ
Does Reality work on mobile data?
Yes. Reality runs over TCP, so carriers that drop UDP do not affect it. If a carrier blocks the Reality port, the WebSocket entry on port 443 still works.
Can I set the SNI to anything?
No. The server is configured for a specific camouflage site, and the sni in your key must match it. Changing it breaks the handshake.
Why does it work at home but not at the office?
The office network filters TLS handshakes to unknown destinations or allows only port 443. See causes 4 and 5 and use the WebSocket entry there.
Is Reality slower than the WebSocket entry?
Usually not. Both add one TLS handshake when connecting; WebSocket adds a little framing overhead per packet, which is rarely noticeable.