Dashboard crash report (x50)

cjbujold

When starting the pfSense plus, I get a crash report. I am able to go to other menu options but cannot get to the dashboard. How do I fix. Thanks

When I try to clear the crash report I get a X50 error.

Crash report begins. Anonymous machine information:

amd64
16.0-CURRENT
FreeBSD 16.0-CURRENT #41 plus-RELENG_25_11-n256500-a43915e7ef55: Mon Dec 1 19:02:15 UTC 2025 root@pfsense-build-release-amd64-1.eng.atx.netgate.com:/var/jenkins/workspace/pfSense-Plus-snapshots-25_11-main/obj/amd64/mjYGPXLl/var/jenkins/workspace/pfSe

Crash report details:

No PHP errors found.

No FreeBSD crash data found.

stephenw10

Check the System-General and GUI Service logs for errors at that time.

cjbujold

Hope this helps: My PC Nic is a 2.5 GB and the pfSense Nic is a 10GB connected to a 10GB switch. Tested the speed to the Internet to see if it was some sort of communication issue, and I get a steady 2.5GB throughput with no packet lost and a 0.02 ms average delay.

Here are the messages from the System-General log.

Jan 2 07:24:12 kernel arp: 192.168.76.8 moved from 00:11:32:47:f3:29 to 00:11:32:47:f3:2a on ix1
Jan 2 07:24:10 kernel arp: 192.168.76.8 moved from 00:11:32:47:f3:2a to 00:11:32:47:f3:29 on ix1
Jan 2 07:23:49 nginx 2026/01/02 07:23:49 [error] 18314#100611: *738 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 192.168.76.50, server: , request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "192.168.76.1:5000", referrer: "https://192.168.76.1:5000/"
Jan 2 07:23:48 kernel arp: 192.168.76.8 moved from 00:11:32:47:f3:29 to 00:11:32:47:f3:2a on ix1
Jan 2 07:23:46 kernel sonewconn: pcb 0xfffff8034c4f5a80 (192.168.2.20:443 (proto 6)): Listen queue overflow: 193 already in queue awaiting acceptance (28 occurrences), euid 0, rgid 0, jail 0
Jan 2 07:23:44 kernel arp: 192.168.76.8 moved from 00:11:32:47:f3:2a to 00:11:32:47:f3:29 on ix1
Jan 2 07:23:41 kernel arp: 192.168.76.8 moved from 00:11:32:47:f3:29 to 00:11:32:47:f3:2a on ix1

The GUI service log show for that time period :

Jan 1 16:31:30 nginx 192.168.76.50 - - [01/Jan/2026:16:31:30 -0400] "GET /index.php HTTP/2.0" 200 4756 "https://192.168.76.1:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:146.0) Gecko/20100101 Firefox/146.0"
Jan 2 07:23:56 nginx 192.168.76.50 - - [02/Jan/2026:07:23:56 -0400] "GET /crash_reporter.php HTTP/2.0" 200 8026 "https://192.168.76.1:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:146.0) Gecko/20100101 Firefox/146.0"
Jan 2 07:23:56 nginx 192.168.76.50 - - [02/Jan/2026:07:23:56 -0400] "GET /css/pfSense.css?v=1764611878 HTTP/2.0" 200 7054 "https://192.168.76.1:5000/crash_reporter.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:146.0) Gecko/20100101 Firefox/146.0"
Jan 2 07:23:56 nginx 192.168.76.50 - - [02/Jan/2026:07:23:56 -0400] "GET /vendor/jquery-ui/jquery-ui-1.13.2.min.js?v=1764611878 HTTP/2.0" 200 255084 "https://192.168.76.1:5000/crash_reporter.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:146.0) Gecko/20100101 Firefox/146.0"
Jan 2 07:24:35 nginx 192.168.76.50 - - [02/Jan/2026:07:24:35 -0400] "GET /status_logs.php HTTP/2.0" 200 16516 "https://192.168.76.1:5000/crash_reporter.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:146.0) Gecko/20100101 Firefox/146.0"

stephenw10

OK so you are trying to access the gui at 192.168.76.1 on port 5000?

What is at 192.168.2.20? Something it hitting pfSense at that address and it's not servicing the requests.

cjbujold

The 192.168.2.20 is our ISP provided address from their router. They provide a 4 ports router and 192.168.2.20 is the PFsense port. The other 3 ports have nothing connected.

The various ports (80, 443, etc..) required by us are forwarded from the ISP router to PFSense. All our PC's/servers are behind the 192.168.76.1 PFsense box.

tinfoilmatt

@cjbujold Change the gateway "Monitor IP" to something other than the ISP's 'gateway' IP address.

stephenw10

Ok so you're forwarding incoming traffic on the WAN on port 443. Using HAProxy?

And, to confirm, you're running the webgui on port 5000?

cjbujold

Yes on Both. (forwarding and HAProxy) and pfSense on port 5000.

stephenw10

Hmm well it looks like something was exhausted in the input queue to HAProxy and that prevented nginx servicing the webgui request.

Was there a backend issue in HAProxy? Anything logged there?

cjbujold

The problem seems to have gone away. We did a fix for a WireGuard issue that seem to have also fixed this issue (problem was causing a large amount of packet fragmentation).

Will continue to monitor, but only seeing from time to time the same handshake error in the HAProxy log (about every 5-10 minutes). Do not know if my issue is related to this error or if I should be concerned with this error.

Jan 3 10:26:29 protector haproxy[41211]: 127.0.0.1:20880 [03/Jan/2026:10:26:29.589] HTTPS-OffLoading3-Accra/127.0.0.1:1443: SSL handshake failure

stephenw10

You'd probably have to turn up the logging to know more there. But if it's not actually causing connectivity issues it's probably just something timing out when it's loaded.