wg-manager

A easy to use WireGuard dashboard and management tool

Runssource: GitHubPythonMITcommit e70ba4bdc288

Python, MIT licensed. The project labels itself: dashboard, obfuscation, site to site, vpn, wg manager, wireguard, wireguard dashboard and wireguard tunnel.

wg-manager runs. An Argusic agent installed it in 10 minutes and hit 9 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The wg-manager web app installs and builds; its uvicorn server starts on 127.0.0.1:8010, serves the Angular frontend and answers the login/logout/server/api-key endpoints, and its pytest suite passes 6/6; only the WireGuard tool endpoints fail because the wg binary is absent from the container.

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.03 (measured)
recorded runs
1
last tested
stars
630
forks
74
open issues
49
watchers
30
size
4 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 wg-manager, 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.

  • wg endpoints return 500 (FileNotFoundError: 'wg'); wireguard-tools not installed in container and no root to apt install5 minutes
  • tests hit non-existent /api/* paths and wrong login content type (5 failures)3 minutes
  • starting server from repo root failed: relative alembic.ini/migrations and build/ paths3 minutes
  • angular build failed on Node 18 (ERR_OSSL_EVP_UNSUPPORTED) and npm peer conflict3 minutes
  • pydantic v2 removed pydantic.typing.List and GenericModel (import of main crashed)2 minutes
  • database/__init__.py empty so tests could not import SessionLocal2 minutes
Install time
10 minutes
Cold machine to finish
17 minutes
Errors hit and fixed
9 hit, 9 fixed with no human help
How the result was proved
curl/http GET / returned 200 (index.html serving built frontend); POST /api/v1/login form returned 200 with bearer token; GET /api/v1/logout 401 unauthenticated then 200 authenticated; GET /api/v1/server/all 200 []; GET /api/v1/users/api-key/add and /list 200 (64-char key, X-API-Key auth 200); pytest tests/test_pytest.py reports 6 passed; wg endpoints 500 FileNotFoundError 'wg'
Model tokens used
1,344,389
Exact commit tested
e70ba4bdc288
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.

1,344,389
All verified. Final state: backend installed, frontend built, server running, tests green.
**Fixes applied (all worked)**
- Pinned `pydantic<2` / `fastapi<0.100` in `requirements.txt` — v2 Pydantic broke `pydantic.typing.…
- Pinned `bcrypt==4.0.1` — passlib 1.7.4 crashes with bcrypt ≥ 4.1.
- Added `setuptools` to the venv — `pkg_resources` is gone on Python 3.12.
- Re-exported `SessionLocal` from `database/__init__.py` — test module import fix.
- Fixed the test file to the real API: `/api/v1/*` paths and form-data login.
- Made `main.py` resolve `build/` and `database/util.py` resolve `alembic.ini`/`migrations` relativ…
- Dropped hardcoded `sudo` on `wg` commands when sudo isn't installed, and made `is_running()` degr…
**Could not fix**
- WireGuard tools (`wg`, `wg-quick`) are not in the container and system packages can't be installe…

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.
  • Recovered from all 9 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

  • Took 10 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 8 dashboard projects Argusic has installed and timed, wg-manager was the 5th fastest to reach a running state, and 6 of 8 reached one at all.

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 10 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 Runner1/3Runs100.000.03

Topics (from GitHub)

dashboardobfuscationsite-to-sitevpnwg-managerwireguardwireguard-dashboardwireguard-tunnelwireguard-vpnwireguard-vpn-setup

Embed the badge

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

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

Questions

Does wg-manager run?
Yes. wg-manager runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 9 errors on the way, and recorded the session.
How did Argusic test wg-manager?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit e70ba4bdc288. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test wg-manager?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does wg-manager take to install?
10 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 wg-manager need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing wg-manager?
9 things broke in the recorded run, and 9 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does wg-manager compare with the alternatives?
Of the 8 dashboard projects Argusic has installed and timed, wg-manager was the 5th fastest to reach a running state, and 6 of 8 reached one at all.
Where is the evidence for wg-manager?
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