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 gpart recover da1 gpart set -a active da1 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.

I found that I can get to the GUI using http://192.168.2.1/system.php. I went right to System/Update to try to fix the update but it reply's with Retrieving      Unable to check for updates

same here. GRE under ipsec. I setup a cronjob every minute correcting the mtu when needed, my tunnels are up now. I'm running 2.4.2.

@MainSail: No known way for me fix this failed upgrade! FreeBSD showing 11.1 but still showing 2.3.4-Release-P1 as the current version/"up-to-date". I later noticed that all F/W logging had stopped so at that point the only solution was to just reinstall. I had 2.4.0 ready to go on a thumb-drive and then upgraded to 2.4.2 through the console and restored my configuration from backup. All looks fine now and happy with what appears to be a noticeably faster VPN. If someone else have this issue, backup your config and try this - https://forum.pfsense.org/index.php?topic=135582.msg742380#msg742380

Yep you're right - that was indeed one of the problems. fetch -v https://www.google.com resolving server address: www.google.com:443 SSL options: 83004bff Peer verification enabled Using CA cert file: /usr/local/etc/ssl/cert.pem No server SSL certificate fetch: https://www.google.com: Authentication error I thought I had fixed it by SCPing over cert.pem from the source tar.gz and updating the symlinks everywhere, but that wasn't working reliably. Two consecutive fetch commands right after one another would have different results, one would connect over TLS successfully and the second would fail. I think I've messed up horribly somewhere when tweaking the box. Finally gave up and restored factory settings, and everything seems to be good again - was also able to upgrade to 2.4.2 without issues. Thanks Gertjan for all your help.