Repository navigation
v1.0.49
What's fixed
Peer creation no longer hangs the request on the WireGuard kernel apply — and a retry can no longer create a duplicate peer.
Creating a peer committed the row, then pushed the whole server state to wg-helper before answering. On a slow apply the browser or proxy timed out first: Safari showed Load failed for a peer that was already in the console, and clicking Create again inserted a second peer.
- Peer / server / claim / user-suspend mutations now commit and answer immediately. The kernel apply runs in a coalesced per-server background queue (one pass per server at a time, re-reading the newest state; a deleted server's interface teardown is ordered after any in-flight apply).
POST /api/peersaccepts an optionalrequest_ididempotency key, auto-migrated on the first API boot (metadata-only column + partial unique index). A retry replays the original peer (200{"status":"exists"}) instead of inserting or emailing again; overlapping duplicate requests collapse to one row.- Add Peer UI: one stable request id per dialog (reused by retries), a truthful "the request got no response — the peer may already have been created; retrying is safe" hint instead of the raw browser error, an automatic peers-list refresh, and success shown as a notice rather than the red error line.
Measured with a deliberately slow 3 s apply: POST /api/peers 3.004 s → 1.1 ms, and a retry that previously created 2 DB rows now returns the original peer (1 row).
Upgrade with the usual installer (console rebuild; migration 027 is applied automatically on API start):
curl -fsSL https://raw.githubusercontent.com/garyhooi/wireguard-console/main/install.sh | sudo bashVerified: backend build/vet/unit + full E2E suite (twice, including slow-apply latency, idempotent retry, overlapping duplicates and async teardown), -race on the backend and E2E, frontend 140/140 tests + production build, installer/firewall/TLS/AdGuard shell suites.