Nothing that significant changed in the package from 2.2.x to 2.4 that would cause problems as you describe. Maybe you have a browser cache issue or script blocker that is interfering.

I have just attached the amount of the errors. I get them for any config saving. This worries me a lot.


@jimp:

_[…]_The recover option will (very briefly) print a message of success or failure, it's easier to see with a serial console but it's there on VGA if you can catch it, it just doesn't pause after.

Priceless feature!
Though over KVM I bit the nails during install as I did not see this notification [yes or no], everything went flawless, from 2.3.4 > 2.4.2

The certs can be found as <cert>…</cert> pairs in the config.
But, be careful, al these <caref>... <caref>inside them are used on other places (where the certs are used) should also be included, if not => bad things will happen. It's this aspect that makes certs difficult to import or export separately.</caref></caref>

Thanks for setting me straight!!!

Roveer

I had the same problem, and the thread linked above seems to be about some other issue entirely.

All I needed to do was reboot the device (SG-2440).  Afterwards, the branch change page was nice and snappy.

Was browsing thru redmine just now and noticed #7307.  So it seems this is offically a bug. Not a huge deal, but just wanted to link here in case anyone else stumbles onto it.

Played around with it and eventually got it to boot from memstick, but after intsall it hung at the  Consoles: EFI console.

I found a post on the FreeBSD forum which is exactly my problem on the very same hardware.  No answers or workarounds (other than ugly manual process).

https://forums.freebsd.org/threads/61243/ and the bug report he posted here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219957

So to save myself headache's once this is running I'm going to stick with Legacy boot and the fuzzy console.

Unless…

Someone can help me with the linux commands to set the console to something better.

Roveer

Fixed it! Made the following modification:

https://doc.pfsense.org/index.php/Boot_Troubleshooting

Then changed the boot drive in the bios.

502 bad gateway issue has a separate topic. It appears to be related to something triggering the issue with pfBlocker's DNSBL. To be clear, the issue is still under investigation and I am not pointing fingers at pfBlockerNG. For now, disable DNSBL. Lastly, pfBlockerNG is not installed by default with pfSense as its a community developed package. We love and fully support pfBlockerNG development however it's not maintained by pfSense team.

https://forum.pfsense.org/index.php?topic=137103.255

@Modesty:

I have exacly same issue. Tried a lot but still no internet. Are there any solution for this?

You probably want to start a new thread with a complete description of the problem you are experiencing. This thread referred to a (long resolved) issue with migrating monitoring parameters from apinger to dpinger which affected monitoring only.