pfSense CE 2.8.0 - PHP Error
-
Upgraded from 2.7.2 to 2.8.0, rebooted again after the install failed to see if the issue was a one off, but that did not resolve the issue. Also read the Troubleshooting Upgrades section, and didn't see anything that appeared to apply in this situation. Log below:
Crash report begins. Anonymous machine information:
amd64
15.0-CURRENT
FreeBSD 15.0-CURRENT #1 RELENG_2_8_0-n256081-401ec5f685b9: Wed May 21 23:53:51 UTC 2025 root@freebsd:/var/jenkins/workspace/pfSense-CE-snapshots-2_8_0-main/obj/amd64/0q9vjGjc/var/jenkins/workspace/pfSense-CE-snapshots-2_8_0-main/sources/FreeBSD-src-RECrash report details:
PHP Errors:
[01-Jun-2025 20:37:00 US/Pacific] PHP Fatal error: Uncaught TypeError: Nette\Utils\Html::insert(): Argument #2 ($child) must be of type Nette\HtmlStringable|string, null given, called in /usr/local/pfSense/include/vendor/nette/utils/src/Utils/Html.php on line 580 and defined in /usr/local/pfSense/include/vendor/nette/utils/src/Utils/Html.php:610
Stack trace:
#0 /usr/local/pfSense/include/vendor/nette/utils/src/Utils/Html.php(580): Nette\Utils\Html->insert(NULL, NULL)
#1 /usr/local/www/widgets/include/disks.inc(100): Nette\Utils\Html->addHtml(NULL)
#2 /usr/local/www/widgets/widgets/disks.widget.php(65): disks_compose_widget_table(Array)
#3 /usr/local/www/index.php(428): include('/usr/local/www/...')
#4 {main}
thrown in /usr/local/pfSense/include/vendor/nette/utils/src/Utils/Html.php on line 610No FreeBSD crash data found.
-
So the upgrade failed?
Or it shows this error after logging into the gui after upgrading?
-
@stephenw10 yes, the update failed, and it reverted to 2.7.2, with some loss of functionality. It also turns out that the original 2.7.2 install media was still mounted in the hypervisor, and only 1Gb of RAM had been allocated, so either issue may have been the root cause.
Is there a reinstall/repair best practices guide for this situation? Thanks
-
@Tablet3381 If it were me, restore last config I'm comfortable with (up to and including troubleshooting of lost functionality after failed upgrade), and simply perform upgrade again with two potential root causes you identified now remediated.
Whether or not you roll back to a config backup from before the first update attempt—or just try the upgrade all over again, with your most recent config changes included, is a fair best practices question. Reasonable minds could differ. Six of one, half-dozen of another if the second attempt goes smooth.
-
Hmm, that error is probably just a symptom of the upgrade not completing then.
If it's a VM I would just roll-back to the last good snap and try again.
-
@stephenw10 that seems like a good guess at this point, reinstall and restore to prior config worked, CE 2.8 is running fine. Thanks everyone!
