Default REALITY target www.microsoft.com can cause handshake failures

[zhujhz]

Summary

The one-click installer currently generates a VLESS + REALITY configuration that uses www.microsoft.com as the default REALITY target/SNI.

In my VPS deployment created from:

https://raw.githubusercontent.com/DanOps-1/Xray-VPN-OneClick/main/scripts/install.sh

this default target caused REALITY handshake failures on Xray-core 26.3.27.

Environment

• Installer: DanOps-1/Xray-VPN-OneClick raw install.sh
• Xray-core: 26.3.27
• Protocol: VLESS + REALITY + Vision
• Client: Clash/Mihomo
• Sensitive values: UUID, public key, private key, short ID, and server IP are redacted

Symptoms

• Clash/Mihomo failed to connect through the node, with EOF-style connection failures
• Xray logs showed REALITY invalid connection / TLS handshake failure messages, including:
  • handshake did not complete successfully
• VPS ports and services were reachable
• The local subscription/profile and the server-side subscription matched
• Rotating UUID/key/short-id did not fix the issue

Findings

The failure was target-specific:

• Using www.microsoft.com as REALITY target/SNI failed
• Changing only the REALITY target/serverName/SNI to another reachable target fixed the node
• After changing the target, the same VPS node worked through Mihomo:
  • api.ipify.org returned the VPS exit IP
  • www.google.com returned HTTP 200
  • api.openai.com/v1/models returned HTTP 401, which is expected without API authentication