It always helps to read the release notes. But, release notes are for things that the software cannot handle or very specific unavoidable situations. In this case, running under VMWARE is extremely common and instead of assuming the user will catch the issue, why not simply make the installer add the needed change to the boot loader?? The fact that a patch to correct this, was made, says that it should have been caught in the previous release… It is still great work and it is appreciated, but like I said before, if it is meant to be Enterprise, Production ready, these 'silly' things will drive customers away as well as: "I have never, ever had any upgrade issues with Untangle". @Grimson: https://doc.pfsense.org/index.php/2.4_New_Features_and_Changes#Known_Issues reading helps.

Thanks. The reinstall did the trick.

Yep. I did a backup first. If you have done this right, and you are upgrading to the version 2.4.1 and gets out problems and issues too, I would suggest to do a fresh and full install once more again and also play back the backup file once more again! Just needed a pointer in the right direction which I got on fb from a kind soul. Please ensure that you are using the ADI-AMD-64Bit-Serial version of pfSense! All recovered now, thanks. Keep thre eMMC storage up to date and install a small mSATA that fits your needs and you get a fast backup system! Sometimes time will be not even there, and so you might be able to get a working platform fast back.

pfSense archive (all versions)

@Gertjan: @gklimeck: …... I made Rules in my firewall to match my LAN rules but it can't get out to WAN from a wireless device. What am I missing? Dono. Didn't saw your firewall rules. What about a "pass-all" rule to test? Afterward, you make more specific rules- and test after each new rule - and step back when things won't work anymore. Not a bad idea and I'll get better at this. Thanks, G

Thanks - I downloaded all of the 2.3.4…  in case the links disappear later. I know I should run out and buy 5 new boxes to get rid of the old hardware...  Let me check my pockets...  Lent!

At least that is the way with standard FreeBSD I can fairly report that it is working for me in pfSense version 2.3.x and 2.4.x too!

Awesome, thanks! Wasn't sure if there might be any incompatibilities or caveats importing a config from an older version of the nano distro into the current/full distro.

I cannot thank you enough Renato. I've been tearing my hair out for a few months with this issue before stumbling upon your suggestion here. Sure enough, /usr/local/share/pfSense/keys/pkg/revoked/.empty was there - and the moment it was removed, presto! All I wanted to do was install man :'(. This will be pinned prominently in my notebook! (Though all other systems I manage have been upgraded past 2.3.3!) Cheers, Sam. @Renato: It's exactly what I suspected. There is a bug in pkg that causes this crash. You can see details here: https://github.com/freebsd/pkg/pull/1586 We already fixed it in pfSense before submit the patch to upstream, and based on truss output we can see: The presence of the empty file /usr/local/share/pfSense/keys/pkg/revoked/.empty is the cause. I suspect there is a /usr/local/share/pfSense/keys/pkg/trusted/.empty file too. Just remove them and it will work as expected. As soon as you update pkg to latest version bug will be fixed.

@chudak: I have Sonic 1gb fiber.  @opalmer  it sounds it will/may affect me as well? Thx Answering my own query - I see no speed slowness on Sonic 1gb fiber on 2.4.1 release.

We fixed it.

I have 1 with a 32 bit install and that is exactly how it looks…

Perhaps you don't have interfaces available to add? Configure a vlan, or a openvpn server, and check the page again?

Yeah!  Recovered!    Thank you kindly.  I was banging my head against the wall because dropping into Single User mode mounts read-only, and even trying to run the /etc/rc.remount_rw script was failing.      Didn't realize I could cut out the boot process at any time using Ctrl-C. I'm back in business.

Current snapshots are OK here. Looks like somehow you are missing the pfSense PHP module, or it has failed to load.

Hello to all. I revert to this older post of mine, for an unclosed issue. Today, after a long bike trip in Corsica, I performed the update of my SG-1000 to 2.4.0 It worked. Before and after, I saved the entire configuration (not skipping packages nor RRD data). In System>Advanced>Firewall & NAT, Firewall Optimization Options is still on "Normal". From my earlier update to 2.4.0beta, I had received the following remark: (Filter Reload: There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [19]: table <bogonsv6> persist file "/etc/bogonsv6" @ 2017-10-23 15:49:41) Can I now safely erase that remark and forget about it ? TIA.

try bouncing the LAN interface from the console (ifconfig if down; ifconfig if up) and then restarting php-fpm if you get a 502 error

OK, this issue is solved.  I looked further at the error, and needed to apply further debugging techniques. If disabling sdp would not work, go further back. So I disabled the FireWire driver adding this line to /boot/device.hints hint.fwohci.0.disabled="1" Rebooted and firewall came up fine with 2.4.0 kernel just fine.