WireGuard
{{ overall }}Whether the private link that carries Jellyfin from the house to the VPS is working.
About this page
The link runs between the media server and the VPS. It carries Jellyfin to media.ameribrit.net, and it is the reason the media server needs no port open at the house.
When it fails it fails quietly. WireGuard has no connection to lose, so the interface stays up, the routes stay in place, and packets simply stop arriving. That is what this screen watches for.
Both ends report separately and are meant to disagree: the VPS knows the media server’s address because the media server dials out, and the media server does not know its own. The byte counters count from when the interface last came up, not from the last handshake.
A handshake older than about three minutes means the link is gone, whatever the interface says.
deploy/abp-wireguard.sh.{{ e.name }}
{{ e.iface }} readWho's connected
{{ mcNote }}Every client that reached Jellyfin through the tunnel in the last {{ mcWindow }}. What anyone watched is not recorded here.
About this count
This is the number the port forward at the house is waiting on: once everybody arrives this way rather than straight at the house, it can be closed and the home address stops being published.
Counted from the VPS access log, one minute behind at worst. Clients sharing an address and a browser merge into one, so this errs low; it will never make the old way in look emptier than it is.
media.ameribrit.net to count.