It's this: https://docs.netgate.com/pfsense/en/latest/releases/2-8-0.html#legacy-serial-console It should still boot fully you just don't see it at the console. But you can fix it by adding the loader value as show here. You can also set that one time at the loader prompt to get past it like: OK set hint.uart.0.at="isa" Then edit the /boot/loader.cobf.local file once you're connected again.

PS: I have been delayed from checking in via ScreenConnect due to unrelated issues. Will do so tomorrow AM.

@tmacalp said in Unable to install pfSense Plus 24.03: 18GB worth of config history Yeah that's a sneaky one. I have it in our upgrade notes (coming from an older version, now) to check the config history page until it doesn't time out, before upgrading, but it's been long enough it's not top of mind anymore.

Although I won't be able to provide much/any logs or so, I just want to report that yesterday I had another super slow upgrade. SG1100, from release 23.09.1 to 26.03.1 .. the downloads took over 1hr and 15 minutes. This is a 300 MBit/s line, I had factory reset the appliance and plugged it into LAN via DHCP. The provider is located in Austria: AS # 49163, if that is of any interest. The active upstream gateway also was a pfSense, just mentioning (two appliances in that network, cold standby ...). Internet worked fine on other devices at that time. A reinstallation with the installer would have been an option, but would also result in downloads, so I had decided to just wait for it to keep the overall time as short as possible.

Ok currently you cannot set a custom partition layout in the Net Installer. I'll raise this internally and see what we can do for 1.3.

@stephenw10 I checked the packages (web UI) and could update one of the packages without problem. But the error log was populated again after each reboot. Then I did an upgrade to 25.11.1 and got a different error log: Crash report begins. Anonymous machine information: arm 16.0-CURRENT FreeBSD 16.0-CURRENT #7 plus-RELENG_25_11_1-n256519-3d5e07ee0abe: Mon Jan 19 17:41:32 UTC 2026 root@pfsense-build-release-aarch64-1.eng.atx.netgate.com:/var/jenkins/workspace/pfSense-Plus-snapshots-25_11_1-main/obj/armv7/na6g1KNN/var/jenkins/workspace Crash report details: PHP Errors: [12-Jun-2026 10:25:35 Europe/Amsterdam] PHP Fatal error: Uncaught Error: Call to undefined function parse_config() in /usr/local/pkg/wireguard/includes/wg_globals.inc:228 Stack trace: #0 /usr/local/pkg/wireguard/includes/wg_globals.inc(244): wg_globals() #1 /usr/local/pkg/wireguard/includes/wg_api.inc(34): require_once('/usr/local/pkg/...') #2 /usr/local/pkg/wireguard/includes/wg.inc(30): require_once('/usr/local/pkg/...') #3 /etc/inc/pkg-utils.inc(1083): require_once('/usr/local/pkg/...') #4 /etc/rc.packages(80): delete_package_xml() #5 {main} thrown in /usr/local/pkg/wireguard/includes/wg_globals.inc on line 228 No FreeBSD crash data found. After deleting this log and rebooting I get no new errors so I assume all is good now, Thanks for your suggestions!

@jimp Worked fine for me too, thank you very much. Claudio.

Yup

That behaviour hasn't actually changed in 26.03.1, pkg always failed at the CLI if the client cert has expired. Either load the GUI or run pfSense-repoc -N at the CLI to pull a new cert.

@Gertjan No, it doesn't break DNS if only LAN is connected. Actually, unbound doesn't really care which interface you use. And the configuration page allows to select the interfaces to use and the default is "All", so the DNS Resolver would have still worked, if the DNS traffic would not have been blocked when not going to the LAN-DNS. The only strange thing is that having the local DNS resolver non-working also blocks the entire DNS lookup and the normal DNS lookup will only be done after the resolver has failed. I would have expected that the regular DNS is being used and the resolver only if the local one doesn't have data, but I'm not a DNS expert.

@stephenw10 thanks I'll give that one a try. No, I haven't used pfsense on it before; I was running Ubuntu.

FYI the 2nd upgrade attempt to 26.03.1 was successful.

I tested with Firefox and Chromium in Linux Mint with various window sizes. It just drew the table as expected in each case.

Hello @stephenw10, How do you install Tor on pfSense 2.8.1?

I got the update to install! In order to do it, I had to stop all services, except for sshd and syslogd. Then I logged out of the web page and closed the browser. I used option 13 from the console and it completed this time. I was guessing that stopping all those services would free up some RAM.

You could manually update the config file and reboot like: - <pkg_repo_conf_path>26_03</pkg_repo_conf_path> + <pkg_repo_conf_path>26_03_1</pkg_repo_conf_path>