amnezia-vpn/amnezia-client

Fork 0

mirror of https://github.com/amnezia-vpn/amnezia-client.git synced 2026-10-14 13:52:12 +00:00

[GH-ISSUE #2902] Android 5.0.0.5: ErrorCode 1000 after update, while 4.8.21.0 connects successfully using the same configuration #1318

New issue

Open

opened 2026-10-13 20:40:08 +00:00 by bsakaguchi · 7 comments

bsakaguchi commented

2026-10-13 20:40:08 +00:00

Owner

Originally created by @bridge-user on GitHub (Jul 29, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2902

Describe the bug

After updating the Android client from AmneziaVPN 4.8.21.0 to 5.0.0.5, all Android devices stopped connecting to my AmneziaWG server.

The client immediately returns ErrorCode: 1000.

Downgrading the same devices back to AmneziaVPN 4.8.21.0 immediately restores connectivity using exactly the same server, configuration, keys, endpoint and port.

No server-side changes were made.

The same configuration continues to work correctly with:

Windows client 4.8.10.0
iOS client 4.8.21.0
Android client 4.8.21.0

Only Android 5.0.0.5 fails.

To Reproduce

Install AmneziaVPN Android 5.0.0.5.
Import an existing AmneziaWG configuration that works with Android 4.8.21.0.
Tap Connect.
The client immediately returns ErrorCode: 1000.

Expected behavior

The VPN should connect successfully, exactly as it does with Android 4.8.21.0, Windows 4.8.10.0 and iOS 4.8.21.0 using the same configuration.

Log files

I do not currently have Android application logs.

I checked the server using:

tcpdump -ni any udp port 51830

During connection attempts from Android 5.0.0.5, no UDP packets reach the server at all.

After downgrading only the Android application to 4.8.21.0, the same configuration immediately starts sending UDP packets and the VPN connects successfully.

Screenshots

I can provide a screenshot of ErrorCode: 1000 if needed.

Desktop

OS: Windows 11
AmneziaVPN: 4.8.10.0
Status: Works correctly

Smartphone

Android device #1

OS: Android
AmneziaVPN 5.0.0.5 → ErrorCode: 1000
AmneziaVPN 4.8.21.0 → Works correctly

Android device #2

OS: Android
AmneziaVPN 5.0.0.5 → ErrorCode: 1000
AmneziaVPN 4.8.21.0 → Works correctly

Additional verification

iPhone
AmneziaVPN 4.8.21.0
Works correctly

Server

OS: Ubuntu 24.04
Linux kernel: 6.8.0-136
AmneziaWG bridge (wg-bridge via awg-quick)
amneziawg kernel module: 1.0.20251009
amneziawg-tools: v1.0.20210914

Additional context

No changes were made to the server.

The same endpoint, port, keys and configuration were used in every test.

The only change between successful and failed tests was the Android client version:

Android 4.8.21.0 → Works
Android 5.0.0.5 → ErrorCode: 1000

This issue was reproduced on two different Android devices.

An additional observation:

Android 5.0.0.5 does not appear to send any UDP packets to the server during connection attempts (verified with tcpdump), while Android 4.8.21.0 immediately starts sending packets using the same configuration.

Originally created by @bridge-user on GitHub (Jul 29, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2902 ## Describe the bug After updating the Android client from **AmneziaVPN 4.8.21.0** to **5.0.0.5**, all Android devices stopped connecting to my AmneziaWG server. The client immediately returns **ErrorCode: 1000**. Downgrading the **same devices** back to **AmneziaVPN 4.8.21.0** immediately restores connectivity using **exactly the same server, configuration, keys, endpoint and port**. No server-side changes were made. The same configuration continues to work correctly with: - Windows client 4.8.10.0 - iOS client 4.8.21.0 - Android client 4.8.21.0 Only Android 5.0.0.5 fails. --- ## To Reproduce 1. Install AmneziaVPN Android 5.0.0.5. 2. Import an existing AmneziaWG configuration that works with Android 4.8.21.0. 3. Tap **Connect**. 4. The client immediately returns **ErrorCode: 1000**. --- ## Expected behavior The VPN should connect successfully, exactly as it does with Android 4.8.21.0, Windows 4.8.10.0 and iOS 4.8.21.0 using the same configuration. --- ## Log files I do not currently have Android application logs. I checked the server using: ```bash tcpdump -ni any udp port 51830 ``` During connection attempts from **Android 5.0.0.5**, **no UDP packets reach the server at all**. After downgrading **only** the Android application to **4.8.21.0**, the same configuration immediately starts sending UDP packets and the VPN connects successfully. --- ## Screenshots I can provide a screenshot of **ErrorCode: 1000** if needed. --- ## Desktop - OS: Windows 11 - AmneziaVPN: 4.8.10.0 - Status: Works correctly --- ## Smartphone ### Android device #1 - OS: Android - AmneziaVPN 5.0.0.5 → ErrorCode: 1000 - AmneziaVPN 4.8.21.0 → Works correctly ### Android device #2 - OS: Android - AmneziaVPN 5.0.0.5 → ErrorCode: 1000 - AmneziaVPN 4.8.21.0 → Works correctly ### Additional verification - iPhone - AmneziaVPN 4.8.21.0 - Works correctly --- ## Server - OS: Ubuntu 24.04 - Linux kernel: 6.8.0-136 - AmneziaWG bridge (wg-bridge via awg-quick) - amneziawg kernel module: 1.0.20251009 - amneziawg-tools: v1.0.20210914 --- ## Additional context No changes were made to the server. The same endpoint, port, keys and configuration were used in every test. The **only** change between successful and failed tests was the Android client version: - Android 4.8.21.0 → Works - Android 5.0.0.5 → ErrorCode: 1000 This issue was reproduced on two different Android devices. An additional observation: Android 5.0.0.5 does not appear to send any UDP packets to the server during connection attempts (verified with `tcpdump`), while Android 4.8.21.0 immediately starts sending packets using the same configuration.

bsakaguchi commented

2026-10-13 20:40:09 +00:00

Author

Owner

@iolpltuisciaoln commented on GitHub (Jul 30, 2026):

Same
Android 15

@iolpltuisciaoln commented on GitHub (Jul 30, 2026): Same Android 15

bsakaguchi commented

2026-10-13 20:40:10 +00:00

Author

Owner

@lopatinas commented on GitHub (Jul 30, 2026):

Have same problem on S26 with Android 16 and Amnezia 5.0.0.5 while try to connect over Wireguard.

@lopatinas commented on GitHub (Jul 30, 2026): Have same problem on S26 with Android 16 and Amnezia 5.0.0.5 while try to connect over Wireguard.

bsakaguchi commented

2026-10-13 20:40:10 +00:00

Author

Owner

@Exboom commented on GitHub (Jul 30, 2026):

Pixel 10, Android 17, Wireguard – similar problem. AmneziaWG is working correctly.

@Exboom commented on GitHub (Jul 30, 2026): Pixel 10, Android 17, Wireguard – similar problem. AmneziaWG is working correctly.

bsakaguchi commented

2026-10-13 20:40:10 +00:00

Author

Owner

@Skisliy commented on GitHub (Jul 31, 2026):

Такая же проблема, после обновления на 5.0.0.5 на двух андройдах - 13 и 16

@Skisliy commented on GitHub (Jul 31, 2026): Такая же проблема, после обновления на 5.0.0.5 на двух андройдах - 13 и 16

bsakaguchi commented

2026-10-13 20:40:11 +00:00

Author

Owner

@squanoe commented on GitHub (Jul 31, 2026):

Same problem

@squanoe commented on GitHub (Jul 31, 2026): Same problem

bsakaguchi commented

2026-10-13 20:40:11 +00:00

Author

Owner

@iolpltuisciaoln commented on GitHub (Aug 5, 2026):

any progress?

@iolpltuisciaoln commented on GitHub (Aug 5, 2026): any progress?

bsakaguchi commented

2026-10-13 20:40:11 +00:00

Author

Owner

@pablobagdal commented on GitHub (Aug 16, 2026):

thanks for the issue, successfully fixed problem by downgrading to 4.8.21.0. Will wait until better updates! And anyway thanks to all team who works on it!

@pablobagdal commented on GitHub (Aug 16, 2026): thanks for the issue, successfully fixed problem by downgrading to 4.8.21.0. Will wait until better updates! And anyway thanks to all team who works on it!

bsakaguchi referenced this issue

2026-10-13 21:20:47 +00:00

[PR #1318] [MERGED] Improve XRay protocol child process handling #2312