Project

General

Profile

Actions

Regression #16513

closed

WireGuard service show status stopped but peers can still connect

Added by Bart Schapendonk 27 days ago. Updated 13 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
WireGuard
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
25.11
Release Notes:
Force Exclusion
Affected Version:
2.9.0
Affected Architecture:

Description

  • On the services page, WireGuard show status stopped, starting it doesn't work and I can't find anything in the logs. Peers can still connect and WireGuard seems to work.
  • The ServiceWatchdog plugin keeps trying to start WireGiard.

This is on pfSense+ 25.11.b.20251028.1838


Related issues

Has duplicate Regression #16519: The service show not running but client can connect to wireguard serverDuplicate

Actions
Actions #1

Updated by Bart Schapendonk 27 days ago

Re-installing the wireguard plugin did not work.

Actions #2

Updated by Marcos M 25 days ago

  • Has duplicate Regression #16519: The service show not running but client can connect to wireguard server added
Actions #3

Updated by Christian McDonald 25 days ago

  • Assignee changed from Christian McDonald to Marcos M
  • Priority changed from Low to Normal
  • Target version set to 2.9.0
  • Plus Target Version set to 25.11
  • Release Notes changed from Default to Force Exclusion

Marcos and I investigated this earlier today and he has the fix to commit at some point.

Actions #4

Updated by Marcos M 25 days ago

  • Status changed from New to Feedback

Fixed with d569b16238046272ba2ef58552743e41e800df3d

Make sure to delete /var/run/wireguardd.pid after applying the patch.

Actions #5

Updated by Marcos M 25 days ago

  • Affected Version set to 2.9.0
Actions #6

Updated by Marcos M 25 days ago

  • % Done changed from 0 to 100
Actions #7

Updated by Marcos M 25 days ago

  • Subject changed from WireGuard service show status stopped, but peers can stil connect to WireGuard service show status stopped but peers can still connect
Actions #8

Updated by → luckman212 20 days ago

just in case anyone wants to patch early using System Patches...

you have to remove the references to the Makefile since that won't be present on a normal system

add commit ID https://github.com/pfsense/FreeBSD-ports/commit/d569b16238046272ba2ef58552743e41e800df3d.patch

set Path strip count to 4

Use this Patch Content

--- a/net/pfSense-pkg-WireGuard/files/usr/local/pkg/wireguard/includes/wg_service.inc
+++ b/net/pfSense-pkg-WireGuard/files/usr/local/pkg/wireguard/includes/wg_service.inc
@@ -326,7 +326,8 @@ function wg_restart_extra_services($force = false) {

     // TODO: This is where we will add facilities for users to pick what services to restart

-    return true;
+    // 0 means success
+    return 0;
 }

 // Main WireGuard service loop

Actions #9

Updated by Marcos M 13 days ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF