Reel opens but stalls; same server works in v2rayNG #1491

New issue

Open

opened 2026-10-13 20:43:45 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-13 20:43:45 +00:00

Owner

Originally created by @skooterking5 on GitHub (Sep 26, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/3221

Describe the bug
With AmneziaVPN 5.0.3.0 connected in Android full-tunnel Xray mode, tapping a shared Facebook Reel URL of the form https://www.facebook.com/share/r/<token>/ launches the Facebook app and opens the Reel viewer, but the Reel remains indefinitely on a loading spinner. The URL token is omitted here. General Facebook app functions, including comments, Stories, and Reels reached inside the app, work.

The client profile already uses "flow": "xtls-rprx-vision-udp443" and "fingerprint": "firefox". This is a narrower failure than the earlier standard-Vision UDP/443 behavior.

To Reproduce

Connect AmneziaVPN's Xray full-device VPN using a VLESS + REALITY server with TCP transport and the client settings above.
Tap a Facebook /share/r/<token>/ link in Android.
Observe that Android opens the Facebook app and the Reel viewer, but playback stays on a spinner.
Disconnect Amnezia and tap the exact same link: the Reel loads immediately.
Configure the same VLESS + REALITY server manually in v2rayNG and tap the same link: it works.

Expected behavior
The Reel should load after the link is handed to the Facebook app, as it does disconnected and through v2rayNG on the same server.

Log files
A clean sanitized log was not captured during the initial A/B tests. None is attached.

Screenshots
None.

Desktop (please complete the following information):

Not applicable.

Smartphone (please complete the following information):

Device: Samsung Galaxy S24 Ultra (SM-S928U)
OS: Android 16, One UI 8.5 (build BP4A.251205.006.S928USQS6DZH3)
AmneziaVPN: 5.0.3.0
v2rayNG control: 2.2.6
Facebook: 573.0.0.37.74
Chrome: 153.0.8010.52

Server (please complete the following information):

OS: Debian 13 on a self-hosted VPS
Protocol/transport: VLESS + REALITY over TCP, port 443

Additional context

The Android App Links routing issue was corrected before this test. The link enters the Facebook app; the failure occurs while loading the Reel.
Chrome through Amnezia Xray loads Facebook web content.
v2rayNG returned HTTP/2 during the working control, so this specific failure is not dependent on HTTP/3 or QUIC.
Related: #2704 involved Android Xray/REALITY and a Chrome fingerprint problem resolved by switching to Firefox. Here the fingerprint was already Firefox, general traffic works, and the same server succeeds through v2rayNG.
Android VPNService/TUN, tun2socks, TUN-to-Xray forwarding, TCP packet handling, and PMTU/MSS are possible areas to investigate, not established causes.
No credentials, server address, private link token, or configuration file is included.

Originally created by @skooterking5 on GitHub (Sep 26, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/3221 **Describe the bug** With AmneziaVPN 5.0.3.0 connected in Android full-tunnel Xray mode, tapping a shared Facebook Reel URL of the form `https://www.facebook.com/share/r/<token>/` launches the Facebook app and opens the Reel viewer, but the Reel remains indefinitely on a loading spinner. The URL token is omitted here. General Facebook app functions, including comments, Stories, and Reels reached inside the app, work. The client profile already uses `"flow": "xtls-rprx-vision-udp443"` and `"fingerprint": "firefox"`. This is a narrower failure than the earlier standard-Vision UDP/443 behavior. **To Reproduce** 1. Connect AmneziaVPN's Xray full-device VPN using a VLESS + REALITY server with TCP transport and the client settings above. 2. Tap a Facebook `/share/r/<token>/` link in Android. 3. Observe that Android opens the Facebook app and the Reel viewer, but playback stays on a spinner. 4. Disconnect Amnezia and tap the exact same link: the Reel loads immediately. 5. Configure the same VLESS + REALITY server manually in v2rayNG and tap the same link: it works. **Expected behavior** The Reel should load after the link is handed to the Facebook app, as it does disconnected and through v2rayNG on the same server. **Log files** A clean sanitized log was not captured during the initial A/B tests. None is attached. **Screenshots** None. **Desktop (please complete the following information):** - Not applicable. **Smartphone (please complete the following information):** - Device: Samsung Galaxy S24 Ultra (SM-S928U) - OS: Android 16, One UI 8.5 (build BP4A.251205.006.S928USQS6DZH3) - AmneziaVPN: 5.0.3.0 - v2rayNG control: 2.2.6 - Facebook: 573.0.0.37.74 - Chrome: 153.0.8010.52 **Server (please complete the following information):** - OS: Debian 13 on a self-hosted VPS - Protocol/transport: VLESS + REALITY over TCP, port 443 **Additional context** - The Android App Links routing issue was corrected before this test. The link enters the Facebook app; the failure occurs while loading the Reel. - Chrome through Amnezia Xray loads Facebook web content. - v2rayNG returned HTTP/2 during the working control, so this specific failure is not dependent on HTTP/3 or QUIC. - Related: #2704 involved Android Xray/REALITY and a Chrome fingerprint problem resolved by switching to Firefox. Here the fingerprint was already Firefox, general traffic works, and the same server succeeds through v2rayNG. - Android VPNService/TUN, tun2socks, TUN-to-Xray forwarding, TCP packet handling, and PMTU/MSS are possible areas to investigate, not established causes. - No credentials, server address, private link token, or configuration file is included.

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

amnezia-vpn/amnezia-client#1491

No description provided.

Rows
Columns