#1047 - [GH-ISSUE #2368] XRay connection is not working after installing version - 4.8.14.5 - amnezia-vpn/amnezia-client

bsakaguchi commented

2026-10-13 20:33:23 +00:00

Owner

Originally created by @IldarMurzenkov on GitHub (Mar 18, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2368

Describe the bug
The connection keeps disconnecting unexpectedly.

Steps to reproduce the behavior:
Connect using Xray
The connection drops after some time and not working

Additional Information

Issue occurs across all platforms: iOS, Android, Mac

Originally created by @IldarMurzenkov on GitHub (Mar 18, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2368 **Describe the bug** The connection keeps disconnecting unexpectedly. **Steps to reproduce the behavior:** Connect using Xray The connection drops after some time and not working **Additional Information** Issue occurs across all platforms: iOS, Android, Mac

bsakaguchi commented

2026-10-13 20:33:25 +00:00

Author

Owner

@abix5 commented on GitHub (Mar 18, 2026):

I am using Amnezia with Xray REALITY on my own server.
With client version 4.8.11.4, the connection works normally.
With the latest client version, the same server configuration fails with this log:
03-12 18:35:31.118Z 16544 17846 W Thread-16 libXray: 2026/03/12 18:35:31.118247 Error transport/internet/reality: REALITY: received real certificate (potential MITM or redirection)
The issue seems to appear only after updating the client, while the server side remained unchanged.
From my understanding, this error means the client receives the real TLS certificate of the masking site instead of the temporary certificate expected from REALITY, which may happen when REALITY falls back to the real destination because of a mismatch in parameters such as SNI/serverNames, shortId, or TLS fingerprint/uTLS behavior.
What I need to understand is which server-side parameters should be updated or regenerated to make the current server compatible with the latest Amnezia client.
In particular, I would like to know whether I should check or regenerate serverNames , dest , shortIds , REALITY keys, or fingerprint-related settings, because newer Xray-based clients appear to validate these parameters more strictly than older versions.

@abix5 commented on GitHub (Mar 18, 2026): I am using Amnezia with Xray REALITY on my own server. With client version 4.8.11.4, the connection works normally. With the latest client version, the same server configuration fails with this log: `03-12 18:35:31.118Z 16544 17846 W Thread-16 libXray: 2026/03/12 18:35:31.118247 Error transport/internet/reality: REALITY: received real certificate (potential MITM or redirection)` The issue seems to appear only after updating the client, while the server side remained unchanged. From my understanding, this error means the client receives the real TLS certificate of the masking site instead of the temporary certificate expected from REALITY, which may happen when REALITY falls back to the real destination because of a mismatch in parameters such as SNI/serverNames, shortId, or TLS fingerprint/uTLS behavior. What I need to understand is which server-side parameters should be updated or regenerated to make the current server compatible with the latest Amnezia client. In particular, I would like to know whether I should check or regenerate serverNames , dest , shortIds , REALITY keys, or fingerprint-related settings, because newer Xray-based clients appear to validate these parameters more strictly than older versions.

bsakaguchi commented

2026-10-13 20:33:25 +00:00

Author

Owner

@RedSynthez commented on GitHub (Mar 18, 2026):

Same thing. Noticed it couple of months ago when it updated to 4.8.12 version. Decided to stay on the 4.8.11.4 as it works just fine. Tried the new one 4.8.14.5 but it doesn't work for my xray config either. Do we have to delete it from our server and then install it again?
update: Ok I can confirm - after you delete amnezia software from your server and re-install it again, it does work on the latest version of the app 4.8.14.5.

@RedSynthez commented on GitHub (Mar 18, 2026): Same thing. Noticed it couple of months ago when it updated to 4.8.12 version. Decided to stay on the 4.8.11.4 as it works just fine. Tried the new one 4.8.14.5 but it doesn't work for my xray config either. Do we have to delete it from our server and then install it again? update: Ok I can confirm - after you delete amnezia software from your server and re-install it again, it does work on the latest version of the app 4.8.14.5.

bsakaguchi commented

2026-10-13 20:33:25 +00:00

Author

Owner

@vladimir-bushuev commented on GitHub (Mar 19, 2026):

I ran into the same issue. I am still using 4.8.11.4, but this isn't convinient if you need to manage WG2 protocol simultaneously on the same server.

@vladimir-bushuev commented on GitHub (Mar 19, 2026): I ran into the same issue. I am still using 4.8.11.4, but this isn't convinient if you need to manage WG2 protocol simultaneously on the same server.

bsakaguchi commented

2026-10-13 20:33:25 +00:00

Author

Owner

@klpx commented on GitHub (Mar 20, 2026):

@RedSynthez but do old client work with the updated server?

@klpx commented on GitHub (Mar 20, 2026): @RedSynthez but do old client work with the updated server?

bsakaguchi commented

2026-10-13 20:33:26 +00:00

Author

Owner

@AlexGo14 commented on GitHub (Mar 23, 2026):

I have the exact same problem.
The new client cannot connect to the old server.
There aren't any major issues with the Android and Windows clients-you can simply install an older version -but iOS is a problem, as you cannot select a specific app version on that platform.

@AlexGo14 commented on GitHub (Mar 23, 2026): I have the exact same problem. The new client cannot connect to the old server. There aren't any major issues with the Android and Windows clients-you can simply install an older version -but iOS is a problem, as you cannot select a specific app version on that platform.

bsakaguchi commented

2026-10-13 20:33:26 +00:00

Author

Owner

@RedSynthez commented on GitHub (Mar 23, 2026):

@RedSynthez but do old client work with the updated server?

It does. 4.8.11.4 worked with updated server files without any issues.

@RedSynthez commented on GitHub (Mar 23, 2026): > [@RedSynthez](https://github.com/RedSynthez) but do old client work with the updated server? It does. 4.8.11.4 worked with updated server files without any issues.

bsakaguchi commented

2026-10-13 20:33:26 +00:00

Author

Owner

@annndruha commented on GitHub (Mar 26, 2026):

Same problem:

New versions of client app says "Connected" to old xray self-hosted installation, but it not. No websites open even temporarily.
In android logs: transport/internet/reality: REALITY: received real certificate (potential MITM or redirection)
In windows logs: [WARNING] Amnezia : VpnConnection::addSitesRoutes: Failed to flush DNS
Old app versions works fine with same server.

My old server docker images versions:

amnezia-xray a4e66db7dd64   15 months ago   64.1MB
amnezia-dns 387fcf7b066c   20 months ago   227MB
amnezia-awg 941bb021aef8   20 months ago   26.8MB

App versions with notice xray problems:

4.8.14.5 (Mar 10 2026, 477afb9) Android from Google Play
4.8.14.5 (Feb 26 2026, 477afb9) Winodws app from GitHub exe

App versions without notice xray problems:

4.8.9.2 (5be44f95) Winodws app from GitHub exe
4.8.11.5 (0b89051) Android from Google Play
4.8.11.4 From GitHub apk: AmneziaVPN_4.8.11.4_android9+_arm64-v8a.apk

Xray settings:

www.googletagmanager.com, port: 443
Configs for new apps versions was restored from backup-file

Fresh self-hosted xray installation on another server works fine with 4.8.14.5 clients

Logs with hide my ip's:

AmneziaVPN_android.log
AmneziaVPN_windows.log

@annndruha commented on GitHub (Mar 26, 2026): **Same problem:** * New versions of client app says "Connected" to old xray self-hosted installation, but it not. No websites open even temporarily. * In android logs: `transport/internet/reality: REALITY: received real certificate (potential MITM or redirection)` * In windows logs: `[WARNING] Amnezia : VpnConnection::addSitesRoutes: Failed to flush DNS` * Old app versions works fine with same server. **My old server docker images versions:** ``` amnezia-xray a4e66db7dd64 15 months ago 64.1MB amnezia-dns 387fcf7b066c 20 months ago 227MB amnezia-awg 941bb021aef8 20 months ago 26.8MB ``` **App versions with notice xray problems:** * 4.8.14.5 (Mar 10 2026, 477afb9) Android from Google Play * 4.8.14.5 (Feb 26 2026, 477afb9) Winodws app from GitHub exe **App versions without notice xray problems:** * 4.8.9.2 (5be44f95) Winodws app from GitHub exe * 4.8.11.5 (0b89051) Android from Google Play * 4.8.11.4 From GitHub apk: AmneziaVPN_4.8.11.4_android9+_arm64-v8a.apk **Xray settings:** * www.googletagmanager.com, port: 443 * Configs for new apps versions was restored from backup-file **Fresh self-hosted xray installation on another server works fine with 4.8.14.5 clients** Logs with hide my ip's: [AmneziaVPN_android.log](https://github.com/user-attachments/files/26272655/AmneziaVPN_android.log) [AmneziaVPN_windows.log](https://github.com/user-attachments/files/26272654/AmneziaVPN_windows.log)

bsakaguchi commented

2026-10-13 20:33:27 +00:00

Author

Owner

@wer1st commented on GitHub (Mar 30, 2026):

@NickVs2015 @vkamn please revert ios release to previous. It is not so easy to downgrade ios app by ourselves

@wer1st commented on GitHub (Mar 30, 2026): @NickVs2015 @vkamn please revert ios release to previous. It is not so easy to downgrade ios app by ourselves

bsakaguchi commented

2026-10-13 20:33:27 +00:00

Author

Owner

@ya-pekatoros commented on GitHub (Apr 3, 2026):

The same problem, pls, help, fix the issue.

@ya-pekatoros commented on GitHub (Apr 3, 2026): The same problem, pls, help, fix the issue.

bsakaguchi commented

2026-10-13 20:33:27 +00:00

Author

Owner

@atchekho commented on GitHub (Apr 4, 2026):

Try using an IP address for the server instead of domain name (e.g., 123.123.123.123 instead of xyz.com). After I switched to using the IP address for the server instead of domain name, the latest version started to connect without any problems.

@atchekho commented on GitHub (Apr 4, 2026): Try using an IP address for the server instead of domain name (e.g., 123.123.123.123 instead of xyz.com). After I switched to using the IP address for the server instead of domain name, the latest version started to connect without any problems.

bsakaguchi commented

2026-10-13 20:33:27 +00:00

Author

Owner

@levihimeart commented on GitHub (Apr 8, 2026):

When using the randomization feature for Target / SNI / Short ID / Public + Private Key, everything works correctly.
However, when I manually enter the required server values, I consistently get the following error: REALITY: received real certificate (potential MITM or redirection)
This behavior suggests that the issue only occurs with manually configured parameters, while auto-generated settings function as expected.

@levihimeart commented on GitHub (Apr 8, 2026): When using the randomization feature for Target / SNI / Short ID / Public + Private Key, everything works correctly. However, when I manually enter the required server values, I consistently get the following error: REALITY: received real certificate (potential MITM or redirection) This behavior suggests that the issue only occurs with manually configured parameters, while auto-generated settings function as expected.

bsakaguchi commented

2026-10-13 20:33:28 +00:00

Author

Owner

@mehrzadjahani2020-dot commented on GitHub (Apr 10, 2026):

Hello, good morning. My problem is that the Amnesia X-Ray VPN does not open anything even though it is connected and has input and output.please help me
I am Iranian and there is a national internet in my country and I work with Android ears

@mehrzadjahani2020-dot commented on GitHub (Apr 10, 2026): Hello, good morning. My problem is that the Amnesia X-Ray VPN does not open anything even though it is connected and has input and output.please help me I am Iranian and there is a national internet in my country and I work with Android ears

bsakaguchi commented

2026-10-13 20:33:28 +00:00

Author

Owner

@ClayRabbit commented on GitHub (May 2, 2026):

Got the same error when I tried to use HAPP 2.9.0 with my VLESS config. ChatGPT-5.3 suggested using "fingerprint": "firefox" instead of "fingerprint": "chrome", and it worked for me.

@ClayRabbit commented on GitHub (May 2, 2026): Got the same error when I tried to use HAPP 2.9.0 with my VLESS config. ChatGPT-5.3 suggested using `"fingerprint": "firefox"` instead of `"fingerprint": "chrome"`, and it worked for me.

bsakaguchi commented

2026-10-13 20:33:29 +00:00

Author

Owner

@georgyshamteev commented on GitHub (Jun 3, 2026):

Got the same error when I tried to use HAPP 2.9.0 with my VLESS config. ChatGPT-5.3 suggested using "fingerprint": "firefox" instead of "fingerprint": "chrome", and it worked for me.

worked for me, thx

@georgyshamteev commented on GitHub (Jun 3, 2026): > Got the same error when I tried to use HAPP 2.9.0 with my VLESS config. ChatGPT-5.3 suggested using `"fingerprint": "firefox"` instead of `"fingerprint": "chrome"`, and it worked for me. worked for me, thx

Rows
Columns

[GH-ISSUE #2368] XRay connection is not working after installing version - 4.8.14.5 #1047