In the latest version of the client, we added support for AmneziaWG 3.1, brought back config files, and fixed split tunneling.
The new release also contains security updates and is mandatory for all users.
Updates may not be available on all systems at once — it depends on the moderators on the app stores’ side. We’re doing everything we can to speed up the process
What We Improved in Amnezia VPN 5.0.1.5
Added AmneziaWG 3.0 and 3.1
The latest version of the protocol was already supported back in Amnezia VPN 5.0.0.5, but with the new release the setup is working at full strength. We’ll cover the new version in detail separately.
Amnezia Self-hosted users still have access to AmneziaWG 2.0, but we strongly recommend updating. To do this, remove the old container, install the new one, and run the latter under AmneziaWG 3.1.
Amnezia Premium users have access to AmneziaWG 3.0 — we’re also working on rolling it out in Amnezia Free.
Added Import of AmneziaWG 3.1 Config Files
Amnezia VPN 5.0.1.5 supports the extended parameters of the updated protocol version when you upload AmneziaWG config files.
Fixed Split Tunneling
We fixed a bug that caused subnets to be truncated when added to split tunneling by address.
Split tunneling distributes traffic so that specific sites or apps open through the VPN tunnel
Restored Support for Some Linux Versions
Amnezia VPN 5.0.1.5 is available for the Ubuntu 22.04.x and Debian 12 distributions.
Highlighted Outdated AmneziaWG Versions on Self-hosted
In Amnezia Self-hosted configurations, previous versions of the AmneziaWG protocol are highlighted in yellow so it’s easier for you to spot them and switch to the current AmneziaWG 3.1.
Leveled Up the Languages
We updated and expanded the interface translations for all supported languages:
- Arabic,
- Burmese,
- Farsi,
- Hindi,
- Korean,
- Russian
- Simplified Chinese,
- Spanish,
- Ukrainian,
- Urdu.
How to Update Amnezia VPN to the Latest Version
Get the latest builds of our app:
If you have any questions about installing or running Amnezia VPN 5.0.1.5, look for the answer in the project documentation or in our communities:






