wg-manager tested by Argusic Runner
Attempt 1 of 3 · Runs · Argusic Score 100.0 of 100
all runs of wg-managerdashboardobfuscationsite-to-sitevpnwg-managerwireguard
Session recording
Download the original recording · fingerprint d73c37580d23cfcc...
What the test found
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.
Frontend: npm install --legacy-peer-deps (1747 pkgs), ng build production with --openssl-legacy-provider, copied dist to wg-manager-backend/build. Backend: venv install clean. Server runs on 127.0.0.1:8010 (uvicorn, PID 1996) with DB creation + alembic migration on startup. WireGuard-exclusive endpoints (/api/v1/wg/generate_keypair, /generate_psk) return 500 because the wg binary is missing in the container (no root to install system package); every other exercised endpoint works. Untracked artifacts left: database.db, database.db.bak, wg-manager-frontend/package-lock.json.
Argusic installed wg-manager in 10 minutes and launched it; verification reached Verified running for real. 9 of 9 recorded errors were worked through (see the timeline below).
This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.
Error and fix timeline
No errors were recorded for this run.