wireguard_webadmin

wireguard_webadmin is an intuitive web interface for WireGuard VPN management, designed to simplify the configuration and oversight of VPNs. It supports multi-user access and multiple WireGuard instances. Built on open-source principles and Ideal for administrators seeking an efficient and user-friendly VPN management solution.

Runssource: GitHubJavaScriptMITcommit f33cf9775315

JavaScript, MIT licensed. The project labels itself: webadmintool, wireguard and wireguard web.

wireguard_webadmin runs. An Argusic agent installed it in 22 minutes and hit 11 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Django web application builds with venv install, migrations run successfully, all 10 tests pass (5 Django + 5 auth-gateway), and gunicorn serves the full user flow: create-first-user, login (302 to /), and /status/ dashboard returning HTTP 200 with 'WireGuard Status | wireguard-webadmin' title.

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.34 (measured)
recorded runs
1
last tested
stars
290
forks
29
open issues
13
watchers
3
size
34 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 wireguard_webadmin, 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.

  • wireguard_webadmin/production_settings.py missing (entrypoint.sh normally generates it in Docker)4 minutes
  • Django api_v2 tests: test_put_upserts_missing_record_as_create expected 201 without create_if_missing; test_put_upserts_existing_record failed because transaction.on_commit does not fire in TestCase4 minutes
  • auth-gateway tests failed: caddy/config_files/ directory missing3 minutes
  • rrdtool-bindings==0.5.0 failed to build: needs Python.h (python3-dev) and librrd headers, unavailable without root2 minutes
  • auth-gateway test_invalid_oidc_provider_fails_loudly failed: load_runtime_config did not raise ValueError for invalid OIDC provider URL2 minutes
  • pip install blocked by PEP 668 externally-managed-environment on Ubuntu 24.041 minute
Install time
22 minutes
Cold machine to finish
23 minutes
Errors hit and fixed
11 hit, 11 fixed with no human help
How the result was proved
.venv/bin/python manage.py test --noinput ran 5 tests, all OK; .venv/bin/python -m unittest discover -s tests -p 'test_*.py' ran 5 tests, all OK; gunicorn served login at HTTP 200 (GET /accounts/login/), POST /accounts/login/ returned 302 redirecting to /, GET / followed redirects to /status/ returned HTTP 200 with title 'WireGuard Status | wireguard-webadmin'
Model tokens used
509,901
Exact commit tested
f33cf9775315
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

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

- Started at 04:17 (from the process listing)
- The most recent test verification ran around 04:37-04:38
That's about 20 minutes of work. Let me be generous and say 22 minutes.
Final answer:
tokens used
509,901
Right - the auth-gateway tests are standalone `unittest` tests, not Django tests. They need to be r…
Let me now compile the final result. Let me count the minutes more carefully. Looking at the sessio…
- Started at 04:17 (from the process listing)
- The most recent test verification ran around 04:37-04:38
That's about 20 minutes of work. Let me be generous and say 22 minutes.
Final answer:

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 22 minutes.
  • Recovered from all 11 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.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.34

Topics (from GitHub)

webadmintoolwireguardwireguard-web

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/wireguard_webadmin.svg)](https://argusic.com/subject/wireguard-webadmin)

Questions

Does wireguard_webadmin run?
Yes. wireguard_webadmin runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 11 errors on the way, and recorded the session.
How did Argusic test wireguard_webadmin?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f33cf9775315. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test wireguard_webadmin?
The run that produced this verdict cost $0.34: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does wireguard_webadmin take to install?
22 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 wireguard_webadmin need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing wireguard_webadmin?
11 things broke in the recorded run, and 11 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for wireguard_webadmin?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion