pfSense

pfSense Version: 2.9.0 (Upgraded from 2.8.1, issue originally observed since 2.7.2)
Description:
Navigating to Status > WireGuard shows a red banner at the top of the page:

The WireGuard service is not running.

This issue has persisted across versions, present since pfSense 2.7.2, continuing through 2.8.1, and still existing on 2.9.0.

Despite the warning message, all WireGuard tunnels and peers listed below the banner are active and working properly. Latest handshakes continue to update, endpoints remain connected, and traffic counters (RX/TX) increase normally.

The status check logic (e.g., is_service_running('wireguard') or the daemon status checking routine called by status_wireguard.php) incorrectly returns false while the underlying WireGuard module/daemon is fully operational.

Steps to Reproduce:

Configure and enable WireGuard on pfSense 2.7.2, 2.8.1, or 2.9.0.

Ensure WireGuard tunnels and peers are active, connected, and passing traffic.

Navigate to Status > WireGuard (or /status_wireguard.php).

Observe the banner warning stating that the WireGuard service is not running.

Expected Behavior:
The banner "The WireGuard service is not running" should NOT appear when the WireGuard service is active and tunnels/peers are actively communicating.

Actual Behavior:
The top banner displays The WireGuard service is not running, contradicting the active status, active handshakes, and traffic statistics shown in the status table directly below.