Project

General

Profile

Actions

Bug #15968

closed

Updating to development versions with pfBlockerNG-devel installed causes 50x error on GUI (Dashboard)

Added by dylan mendez about 1 month ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Dashboard
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Force Exclusion
Affected Plus Version:
25.03
Affected Architecture:

Description

pfBlockerNG-devel-3.2.1_20
pfSense 25.03.a.20241231.1206

This has been happening consistently on the last two updates.
It does not break the firewall, just causes the Dashboard to show 50x error, all other parts of the firewall are still accessible.

Uninstalling pfBlocker fixes the issue immediatly without a restart.


Files

Actions #1

Updated by dylan mendez about 1 month ago

  • Subject changed from Updating to development versions with pfBlockerNG-devel installed causes 50x error on GUI. to Updating to development versions with pfBlockerNG-devel installed causes 50x error on GUI (Dashboard)
Actions #2

Updated by dylan mendez about 1 month ago

I'm running HA, also.

Actions #3

Updated by Danilo Zrenjanin about 1 month ago

I tested the update from version 24.11 with pfBlocker-devel running to version 25.03.a.20250103.1624 and was unable to reproduce the issue.

High Availability (HA) was not configured during the test.

Actions #4

Updated by dylan mendez about 1 month ago

It seems like just by installing pfBlockerNG-devel causes the crash report


Actions #5

Updated by dylan mendez about 1 month ago

Tested on standalone pfSense with 0 custom settings, was able to reproduce. Just installing pfBlockerNG-devel causes 50x error

This machine has MiM Controller enabled ONLY, no other services.

Actions #6

Updated by dylan mendez about 1 month ago

Installed KVM VM completely from scratch with factory default settings and 25.03.a.20250103.1624 ONLY installed pfBlockerNG-devel, same issue.
Installed KVM VM completely from scratch with factory default settings and 25.03.a.20250103.1624 ONLY installed pfBlockerNG (NON DEVELOPMENT), same issue.

Not an issue with custom configurations.

Went through the available BEs I had with different versions.

Rolled back KVM VM via Boot Environment to 25.01.a.20241206.2132 installed pfBlockerNG-devel, no issue.
Rolled back KVM VM via Boot Environment to 25.03.a.20241210.0600 installed pfBlockerNG-devel, no issue.
Rolled back KVM VM via Boot Environment to 25.03.a.20241220.0600 installed pfBlockerNG-devel, 50x error on dashboard, same issue.

Some snapshot between 2024-12-10 and 2024-12-20 caused this issue. It doesn't seem to affect my 2100.

Booted up 2100 with version 25.03.a.20250103.1624, installed pfBlockerNG-devel, no issue.

Actions #7

Updated by Chris W about 1 month ago

Maybe it's the HA component but which I didn't try yet but with just one instance and default settings except for having changed the LAN address and enabled MiM, I can't trigger this either. I updated a VM in Libvirt on KVM to 25.03, when when it booted back up, installed pfBlockerNG-devel 3.2.1_20. I couldn't get it to show any errors or crashes after install, rebooting, uninstalling, configuring, disabling/re-enabling MiM, factory reset and then reinstall pfBlocker-devl, or otherwise poking at it.

This was on:
25.03-DEVELOPMENT (amd64)
built on Fri Jan 3 16:24:00 UTC 2025
FreeBSD 15.0-CURRENT

However I also didn't do this on a completely new installation of 24.11, which it looks like you also saw the error on. Was that new installation part of an HA cluster as well?

Actions #8

Updated by Marcos M about 1 month ago

  • Status changed from New to Closed
  • Release Notes changed from Default to Force Exclusion
  • Affected Plus Version set to 25.03

This is a symptom of a build version issue in recent snapshots which has been resolved.

Actions

Also available in: Atom PDF