amnezia-vpn/amnezia-client

Fork 0

mirror of https://github.com/amnezia-vpn/amnezia-client.git synced 2026-10-15 05:42:07 +00:00

[GH-ISSUE #1402] AmneziaWG Server Subnet Change Lacks Backward Compatibility #578

New issue

Closed

opened 2026-10-13 20:24:26 +00:00 by bsakaguchi · 6 comments

bsakaguchi commented

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

Owner

Originally created by @AgNS61 on GitHub (Feb 6, 2025).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1402

Issue: Changing AmneziaWG server setting (subnetwork) doesn't have backward compatibility

Environment:
• Mac app version: 4.8.3.1
• OS: macOS Sequoia
• Version: 15.3

Steps to Reproduce the Issue:

Initial Setup:
0. A self-hosted VPN running AmneziaWG with the initial subnet 10.8.1.0.
1. Change the subnet to 10.8.2.0.
2. Connecting to the updated AmneziaWG server from this Mac works correctly.

Behavior on Different Devices:

a) Another Mac (same version, 4.8.3.1, OS 15.3)
4. Share full access to Mac2.
5. The AWG connection on Mac2 works correctly.

b) Another Mac (older version, 4.8.2.3, OS 15.3)
4. Share full access to Mac3.
5. The AWG connection on Mac3 appears to establish, but there is no actual connection.

c) iOS App (iOS 18.3, app v. 4.8.1.8)
4. Share full access to the iOS app.
5. The AWG connection on the mobile app appears to establish, but there is no actual connection.

Additional Findings for last case:
• If I import only the AWG connection (not full access) into the mobile app manually, it works as expected.
• The subnet is correctly set to 10.8.2.0 when imported manually.

Originally created by @AgNS61 on GitHub (Feb 6, 2025). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1402 Issue: Changing AmneziaWG server setting (subnetwork) doesn't have backward compatibility Environment: • Mac app version: 4.8.3.1 • OS: macOS Sequoia • Version: 15.3 Steps to Reproduce the Issue: Initial Setup: 0. A self-hosted VPN running AmneziaWG with the initial subnet 10.8.1.0. 1. Change the subnet to 10.8.2.0. 2. Connecting to the updated AmneziaWG server from this Mac works correctly. Behavior on Different Devices: a) Another Mac (same version, 4.8.3.1, OS 15.3) 4. Share full access to Mac2. 5. The AWG connection on Mac2 works correctly. b) Another Mac (older version, 4.8.2.3, OS 15.3) 4. Share full access to Mac3. 5. The AWG connection on Mac3 appears to establish, but there is no actual connection. c) iOS App (iOS 18.3, app v. 4.8.1.8) 4. Share full access to the iOS app. 5. The AWG connection on the mobile app appears to establish, but there is no actual connection. Additional Findings for last case: • If I import only the AWG connection (not full access) into the mobile app manually, it works as expected. • The subnet is correctly set to 10.8.2.0 when imported manually.

bsakaguchi closed this issue

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

bsakaguchi commented

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

Author

Owner

@Nethius commented on GitHub (Feb 6, 2025):

when saving the settings, a message is shown that says that all previous connections will stop working

@Nethius commented on GitHub (Feb 6, 2025): when saving the settings, a message is shown that says that all previous connections will stop working

bsakaguchi commented

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

Author

Owner

@AgNS61 commented on GitHub (Feb 6, 2025):

when saving the settings, a message is shown that says that all previous connections will stop working

Yes, it says about previous connections. But new connections on older versions of apps also don't work.

@AgNS61 commented on GitHub (Feb 6, 2025): > when saving the settings, a message is shown that says that all previous connections will stop working Yes, it says about previous connections. But new connections on older versions of apps also don't work.

bsakaguchi commented

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

Author

Owner

@Nethius commented on GitHub (Feb 6, 2025):

ahh, i see. You're right

@Nethius commented on GitHub (Feb 6, 2025): ahh, i see. You're right

bsakaguchi commented

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

Author

Owner

@AgNS61 commented on GitHub (Feb 6, 2025):

It's understandable that old connections will not work because subnet was changed. I expect that new connections will have modified subnet. It works when I share only an awg connection, but doesn't work for sharing full access to the server.

@AgNS61 commented on GitHub (Feb 6, 2025): It's understandable that old connections will not work because subnet was changed. I expect that new connections will have modified subnet. It works when I share only an awg connection, but doesn't work for sharing full access to the server.

bsakaguchi commented

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

Author

Owner

@Nethius commented on GitHub (Feb 6, 2025):

Yep, that's because the vpn configuration for the full access config is generated after importing to the device when you press the “Connect” button

@Nethius commented on GitHub (Feb 6, 2025): Yep, that's because the vpn configuration for the full access config is generated after importing to the device when you press the “Connect” button

bsakaguchi commented

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

Author

Owner

@AgNS61 commented on GitHub (Feb 6, 2025):

Understood, it means that after changing server config, the connection will work on at least 4.8.3.1 version

@AgNS61 commented on GitHub (Feb 6, 2025): Understood, it means that after changing server config, the connection will work on at least 4.8.3.1 version

bsakaguchi referenced this issue

2026-10-13 21:16:54 +00:00

[PR #578] [MERGED] bugfix/default-container-index #1933

bsakaguchi referenced this issue

2026-10-13 21:17:19 +00:00

[PR #627] [MERGED] Feature/new awg docker container #1977