wg-portal tested by Argusic Runner

Attempt 2 of 3 · Runs with mocks · Argusic Score 92.0 of 100

all runs of wg-portalldapuiusermanagementvpnwebinterfacewireguard

Session recording

Loading recording...

Download the original recording · fingerprint 538ba905ff443b62...

What the test found

The wg-portal binary builds from source (Go + Vue frontend), all 34 Go packages pass tests and race detection, and the running application serves the embedded web frontend on port 8888 (301 redirect to /app, which serves index.html plus compiled JS/CSS assets with 200), provides REST API login returning admin user JSON on POST /api/v0/auth/login, and exposes Prometheus metrics on port 8788.

The app integrates with the host WireGuard kernel module via wgctrl; inside this container no WireGuard module is loaded, so the local controller returns empty interface lists. All HTTP endpoints (login API, static assets, metrics) respond correctly. The REST API login returns the authenticated user JSON. make build and all 34 go test packages (including race) pass. No third-party keys were needed; the local backend works without any external service. A mock WireGuard interface could not be inserted because the kernel module is absent, but the app handles that gracefully (it logs interface state restored with zero interfaces and keeps serving).

Argusic installed wg-portal in 15 minutes and launched it; verification reached Verified with mock services. 6 of 6 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of wg-portal

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.

Discussion