amneziawg-installer

Install your own AmneziaWG 3.1 VPN server on a fresh Ubuntu or Debian VPS with one command. Made for networks that block WireGuard. No Docker, QR-code import, 2.0 on request for routers.

Runssource: GitHubhomepageShellMITcommit d05781226c81

Shell, MIT licensed. The project labels itself: amneziawg, anti censorship, arm64, automation, bash, debian, double vpn and dpi bypass.

amneziawg-installer runs. An Argusic agent installed it in 8 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 156 Bats test suites pass on Ubuntu 24.04. The AmneziaWG installer shell scripts (awg_common.sh, manage scripts, install scripts) are verified through isolated unit tests covering CIDR helpers, config validation, PPA key embedding, QR code generation (structural), all v5.x bugfixes, protocol markers, routing modes, IPv6 dual-stack, CPS tag safety, device parameter reversibility, restore/backup, and module probing...

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 85 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
85 / 100
cost of the verifying run
$0.13 (measured)
recorded runs
2
last tested
stars
1,593
forks
122
open issues
9
watchers
21
size
21 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing amneziawg-installer, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Test test_ppa_key_embedded.bats failed because gpg-agent was not running in the test's temp GNUPGHOME5 minutes
  • qrencode binary not available - 1 test skipped
Install time
8 minutes
Cold machine to finish
36 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
bats tests/*.bats - all 156 test files executed, all tests pass with exit code 0
Model tokens used
857,310
Exact commit tested
d05781226c81
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**Install:** bats installed via npm, gpg extracted from Ubuntu package, gpg-agent configured for of…
**Tests:** Ran all 156 `.bats` files. Every test passes. The one skipped test (`test_awg31_vpn_uri.…
**Fix applied:** Patched `tests/test_ppa_key_embedded.bats` to start a gpg-agent in the test's temp…
2026-10-08T17:53:55.608413Z ERROR codex_core::session: failed to record rollout items: thread 01a11…
2026-10-08T17:53:55.608438Z ERROR codex_core::session: failed to record rollout items: thread 01a11…
2026-10-08T17:53:55.608453Z ERROR codex_core::session: failed to record rollout items: thread 01a11…
tokens used
857,310
All 156 test files pass. The only issue was a missing `qrencode` binary (cannot be installed withou…
**Install:** bats installed via npm, gpg extracted from Ubuntu package, gpg-agent configured for of…
**Tests:** Ran all 156 `.bats` files. Every test passes. The one skipped test (`test_awg31_vpn_uri.…
**Fix applied:** Patched `tests/test_ppa_key_embedded.bats` to start a gpg-agent in the test's temp…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 8 minutes.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 8 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.13
Argusic Runner1/3Unverified70.000.20

Topics (from GitHub)

amneziawganti-censorshiparm64automationbashdebiandouble-vpndpi-bypassinstallerlinuxprivacyraspberry-pisecurityself-hostedsplit-tunnelingtraffic-obfuscationubuntuvpnvpn-serverwireguard

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/amneziawg-installer.svg)](https://argusic.com/subject/amneziawg-installer)

Questions

Does amneziawg-installer run?
Yes. amneziawg-installer runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test amneziawg-installer?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d05781226c81. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test amneziawg-installer?
The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does amneziawg-installer take to install?
8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does amneziawg-installer need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing amneziawg-installer?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for amneziawg-installer?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion