AmneziaWG 3.1 and 3.0 on your own server: what you get and how to go back to 2.0

Short answer: since version 6.0.0 a new install gets AmneziaWG 3.1, with header encryption and extra padding on top of the 2.0 obfuscation. On ARM and on kernels older than 6.7 the installer picks 2.0 by itself, and for routers and old apps you choose 2.0 with one flag. A server that already runs keeps its version.

See what is running on your server

Two questions with different answers: which profile the server issues to clients, and which module line runs in the kernel. None of them changes the VPN configuration; manage show only writes to its own log.

Which profile the server issues, 3.1 or 2.0:

sudo bash /root/awg/manage_amneziawg.sh show   # the line "Installation protocol generation"
grep AWG_PROTOCOL /root/awg/awgsetup_cfg.init   # the same marker, read directly

The installer also prints the generation in its final report. A server installed before version 6.0.0 runs the 2.0 profile: its AWG_PROTOCOL marker reads 2.0 or is missing, and a missing marker counts as 2.0. A 3.1 server carries HeaderProtectionKey in the [Interface] section of awg0.conf.

Which module and tools the server runs:

cat /sys/module/amneziawg/version   # version of the loaded module
awg --version                      # version of the userspace tools

The first command reads the version attribute of the module running in the kernel right now, not of a file on disk. If the module is not loaded there will be no output - then modinfo amneziawg | grep ^version shows what sits on disk. Why not modinfo by default: if two module trees with the same name ended up on the host, which happens on ARM, it names the wrong one.

⚠️ The apt package version does not answer this question. dpkg -l amneziawg-dkms prints a string starting with 1.0.0 - that is the packaging version, not the protocol one. Ask the module itself with the command above.

What a new install gets

Without --protocol the installer decides from the architecture and the running kernel.

Your serverProfile for clientsKernel module
x86_64, kernel 6.7 or newer3.1third line from the Amnezia team's PPA
Kernel older than 6.7 (a stock Debian 12 with 6.1)2.0, automaticallypinned 2.0 module built from source, tag v1.0.20260725
ARM64 or armhf, a prebuilt package matches your kernel2.0, automaticallythe project's prebuilt package, pinned to the same 2.0 tag
ARM64 or armhf, no prebuilt match, kernel 6.7 or newer2.0, automatically: ARM has not been measured for 3.1third line from the PPA

A third-line module is necessary for 3.1 but not enough. After the reboots the installer also checks the awg tools and the loaded module: it applies the profile to a temporary interface and reads it back. If they do not understand the third line, it switches to 2.0 by itself before any keys are created, as long as the 2.0 set passes the same check, and says why in the log and in the final report; if the module refuses that set too, the install stops without touching the settings file. An explicit --protocol=3.1 on such a machine stops the install and names the reason.

On kernels older than 6.7 the 2.0 module is chosen deliberately. The third line builds there today, but it has the least mileage precisely on older kernels, while the pinned module is verified against an immutable commit. The pinned path receives no updates: upstream has frozen the 1.0.x line. The per-system table, with reason codes, is in ADVANCED.en.md.

Switching between 3.1 and 2.0

The generation is chosen at install time. Updates never change it, so switching takes a reinstall.

A server that already runs

Updating the scripts and --force keep its generation, and so does everyday client management: a 2.0 server stays on 2.0, and client configs you handed out keep working. Only manage restore of a backup made on the other generation changes it, with a warning first. The kernel module is a separate matter: on the PPA path new builds arrive with apt upgrade, and the pinned 2.0 module does not change.

Moving to 3.1

Run --uninstall and then a new install: it gets 3.1 if the machine fits (x86_64, kernel 6.7 or newer; on Debian 12 that means a backports kernel). Every client gets a new profile, and each app has to support 3.1. On ARM the 3.1 profile is not issued for now.

Back to 2.0

The same way round: --uninstall (it removes the server and its 3.1 profiles and by default tries to save a backup archive; check that it was created), then an install with --protocol=2.0 and new profiles for every client. If a router or an old app is in the picture, choose 2.0 before installing: it is cheaper than switching later.

🔴 One thing ARM owners should know about: the module line can change by itself after a reboot. If the amneziawg-dkms package ends up alongside a prebuilt module, then once kernel headers appear DKMS builds, displaces the prebuilt file, and after a reboot that build is what loads. The tunnel does not go down, and dpkg still reports the prebuilt package as installed. The installer prints a warning for this case with exact commands for removing the DKMS package and putting it back under hold; stop after the removal and the new kernel can end up with no working module. Checking the version after a reboot is worth doing anyway.

What happens to client configs

Configs of a server that already runs keep working without a single edit: updating the installer does not touch the generation. A new 3.1 install issues 3.1 profiles. They differ from 2.0 in four places: HeaderProtectionKey (one random key per install, shared by the server and all of its clients), ContentPaddingAddition = 32-128, H1-H4 set to 1-4, and S3/S4 starting at 12. Junk packets Jc, Jmin, Jmax, S1/S2 and the I1 concealment packet stay as before.

An app without 3.1 support does not accept a 3.1 profile: there is no handshake and often no error message either. Routers whose firmware does not support 3.1 yet (stable KeeneticOS, for one), Hiddify and apps that have not been updated for a long time are in this group. Which clients understand 3.1 and from which version: client table. Which app to pick: on Android WG Tunnel or AmneziaWG, on iPhone, Mac and Windows AmneziaWG (why).

Why H1-H4 are 1-4: the key encrypts the header, so the message type is no longer visible on the wire whatever H is, and random ranges add nothing. Two consequences of the key. Changing it means reissuing every client profile. And it has to be identical on both sides: a client without it, or with a different one, cannot complete a handshake. A server installed on 2.0 has no key at all; adding it by hand to one side cuts that side off from the rest.

What the third line adds, and what the 3.1 profile turns on

The short version, without byte-level detail. The full breakdown lives in the advanced docs.

What was addedWhat it is forIn the 3.1 profile
Header encryption (HeaderProtectionKey)Fields that stayed in the clear in the second line stop being a ready-made structure for an observer. WireGuard's own cryptography was left untouched. Must be identical on both sides.on
Extra padding inside the encrypted part (ContentPaddingAddition)Set as a range, with the length drawn from it at random, which blurs the predictable packet-length alignment. Does not have to match between sides.on, 32-128
Timings as rangesRekey, handshake and keepalive intervals are drawn from a range on every use instead of being fixed. Act only on the side where they are set.off
RandomTrailers, DisableCookies (3.1)The first must match on both sides and, together with the rest of the obfuscation, cuts throughput many times over. The second drops the protection against handshake floods along with the cookie-reply signature.off, not even written as off

While none of these is set, a third-line engine puts the same format on the wire as the second one, which is why 2.0 configs keep working on a third-line module. Measurements and the reasoning behind each choice: the 3.1 profile in ADVANCED.en.md.

FAQ

Which AmneziaWG version does the installer put on a server?
Since version 6.0.0 a new install gets AmneziaWG 3.1 on x86_64 with kernel 6.7 or newer: header encryption (HeaderProtectionKey) and extra padding on top of the 2.0 obfuscation. On a kernel older than 6.7, such as a stock Debian 12 with 6.1, and on ARM the installer picks 2.0 by itself and says why. It also switches to 2.0 when the installed awg tools or the loaded module do not understand the third line, as long as the 2.0 set passes the check; otherwise it stops and names the reason. --protocol=2.0 gives a new install the 2.0 profile on any supported system.
How do I check which AmneziaWG version runs on my server?
For the profile the server issues, run sudo bash /root/awg/manage_amneziawg.sh show: it prints the installation protocol generation, 3.1 or 2.0. The same marker is AWG_PROTOCOL in /root/awg/awgsetup_cfg.init. For the module, run cat /sys/module/amneziawg/version - it reads the module loaded into the kernel, not a file on disk; for the tools, awg --version. Do not use modinfo for this: if two module trees with the same name ended up on the host, it may name the one that is not running.
Do I need to move my running server to 3.1?
Nothing forces it. A running server keeps its generation through script updates, --force and everyday client management, and its clients keep working. To move to 3.1, run --uninstall and a new install on a machine that fits (x86_64, kernel 6.7 or newer), then give every client a new profile in an app that supports 3.1. If some of your devices are routers without 3.1 support, Hiddify or old apps, staying on 2.0 is the right call.
Will my existing client configs stop working?
No, not because of an update: the installer keeps the generation of a running server, and the configs you handed out keep working without a single edit. They stop only when you change the server: a reinstall on the other generation, or a reinstall with --preset, --jc, --jmin or --jmax. Then the installer regenerates the obfuscation set and warns that the configs you handed out have to be replaced. --no-cps on its own only removes I1 and keeps the rest, though the installer still suggests reissuing profiles that carry I1.
What does the third AmneziaWG line add over the second?
The main addition is header encryption for the packet fields that stayed in the clear in the second line. It also adds extra padding inside the encrypted part and timings given as a range, with the value drawn from it at random on every use. Each of these is set separately, and while none of them is set a third-line engine puts the same format on the wire as the second. The 3.1 profile turns on the first two; the timings, RandomTrailers and DisableCookies stay off.
Why is there no HeaderProtectionKey in my config?
Because the server runs the 2.0 profile: it was installed before version 6.0.0, with --protocol=2.0, or on ARM or a kernel older than 6.7, where the installer picks 2.0. The key is set for the whole server, and it has to be identical on both sides: a client without it, or with a different one, cannot complete a handshake. So it cannot be added to one client or to the server alone. Moving a server to 3.1 means --uninstall, a new install and new profiles for every client.
Can the module version change by itself after a reboot?
On ARM the module line can. If the amneziawg-dkms package ends up alongside a prebuilt module, then once kernel headers appear DKMS builds, displaces the prebuilt module file, and after a reboot that build is what loads. The tunnel does not go down, and dpkg still reports the prebuilt package as installed. The installer prints a warning for this case with exact commands for removing the DKMS package and putting it back under hold. The profile the server issues stays the same: a module change does not touch it.
Why does Debian 12 get 2.0 instead of 3.1?
That is a deliberate choice, not a technical limit. Its stock kernel 6.1 is older than 6.7, so the installer builds the pinned 2.0 module and issues the 2.0 profile. The third line builds on kernel 6.1 today, but it has the least mileage precisely on older kernels, while the pinned module is verified against an immutable commit. With a backports kernel 6.7 or newer, a new install on Debian 12 can get 3.1, as long as the module and the tools pass the installer's check.

Where to look next

Parameter reference

What changes on the wire, which parameters were added and what has to match between server and client - see ADVANCED.en.md.

Install from scratch

A step-by-step guide for a clean VPS is in INSTALL_VPS.md. The installer picks the module and the profile for you.

Managing clients

Adding, removing and reissuing clients after the install is covered on the client management page.