Thanks for your reply. But it seems the issue was related to BIOS and enabled secure boot ON https://itsfoss.com/no-bootable-device-found-ubuntu/

@Gertjan Thanks. Although I didn't read your reply in time - and upgraded to 2.5.0 : It's my home router/firewall; so I only have a potentially angry wife and some angry kids : Edit (and totally off-topic): I am very pleased to see that my host overrides work again - now I am running 2.5.0 :

Switched back to 2.5.0-DEVELOPMENT version as client DNS issue soon reappeared on 2.4.4_3.

Glad it worked out without too much grief.. Great learning experience for sure! I use to run a proxy in the house back in the day when had 2 teenage boys to filter p0rn from.. But no reason for it any more, and internet is a different place - not like its saving you much bandwidth, etc. And now that on unlimited high speed connections, etc. as well..

Huh? There is not really much difference to the CE. -Rico

@Gertjan dead like this [image: 1558613004673-deadpfsense.png] so only the shell option was working...basically the same issue as the begining

Yes, but you can get detailed information for reinstalling the XG-7100 here: https://docs.netgate.com/pfsense/en/latest/solutions/xg-7100/reinstall-pfsense.html -Rico

@Gertjan Really wish I could, we have some legacy IPMI gear that can only send alerts in the clear to smtp, they support authentication but not SSL or TLS so it limits us configuring them to send directly to our external mail server, we need a service to capture them internally and them securely forward them externally.

I restored a couple more times and the VLANs worked after reassigning the NICs. I don't know what went wrong during the first restores, but it finally works on the last one.

@Rico yes, thank you.

Thanks.

You could download an upgrade image for 2.3 if you can find one, and upgrade to that offline, but that only gets you to 2.3. There isn't a way to live upgrade from 2.3 to 2.4.x offline. Reinstalling would be much faster and easier.

A clean reinstall with 'Recover config.xml' option is probably the fastest way: https://docs.netgate.com/pfsense/en/latest/backup/automatically-restore-during-install.html Before the reinstall take a Backup first just in case... -Rico

Hello, Sorry for this late response as a student and I'm not always at work. Thank you very much for your help because that's exactly what I was looking for.

@rbuckland said in Upgraded from 2.4.3.? to 2.4.4p2 (now p3) sporadic loss of network WAN: add in some extra monitoring somewhere .. That for sure. I'd go and set up a small VM or server/raspi/whatever to not only ping an external source but also add 2-3 other checks as in Ping, DNS, File get / File Put (via sftp for example) Also check if your cable modem has a status site you can call. That's some strange error, that would let out ping and dns but nothing else.

@ady2 said in PHP Startup: Unable to load Dynamic Library. Help please: But this situation when for unknown reason the pfSense stopped working completely, it's a bit worrying me. You just hopped into the thread with "me too" ;) As no one knows what exactly your problem was, one can't read minds what the reason/solution is. The error above is typical for a system that wasn't on at least version 2.4.3 and had trouble with the update. As the OP wrote he had uninstalled squid it's possible that triggered an update (from an older version, 2.4.2 or older perhaps) that had the problem with not locking various packages so they don't accidentally trigger a package update of only few packages instead of a complete update of pfSense base.

@walchst said in Unable to Upgrade 2.4.3-p1 to 2.4.4: Cheers had the same issue using Cloudflare 1.1.1.1. Huh? You want to say that CFs 1.1.1.1 and 1.0.0.1 intercepted your SSL, broke it up and handed you a bad certificate error while contacting the netgate PKG repositories? I can hardly believe that statement as I'm running several production and live setups with CF nameservers as fallback/default for pfSense itself and never ever have I been seeing this. OpenDNS makes sense, as their offer is to filter your DNS with your setup. But CF doesn't filter their public DNS as to my knowledge!

Which will upgrade you to p3 ;)

Hi again. Today, the firewall has decided to crash. After recovering, the IPSEC tunnel has stopped working again, but this time doesn't seem to recover in any way. I've tried to reset de VM but still is unable to connect. I'll try to revert to a snapshot prior of the upgrade.

@rmaeder said in Absolute Worst Experience Trying to Upgrade to 2.4.4_3: but that should have been fixed in 2.4.4_1? Yes, it was, but fix didn't clean your existing config file. Open a console, option 8 and use viconfig Add an empty <donothing> </donothing> And save the config (: wq). From now on, it will be part of your config file, it will last in there. Note that reading in the existing config while booting doesn't break things, but importing does (when a double rrddata exists). Also : https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/diag_backup.php#L204 looks nice, but I guess (again - I'm just thinking out loud here) that a second <rrddata></rrddata> isn't removed. So, in a config backup, selected without rrddata you had always an empty rrddata section, that silently failed when restoring the actually RRD data files on disk when booting pfSense. Actually exporting rrd data : [image: 1558940734211-57f1302b-8da6-490b-b8d5-55cad482b471-image.png] and you wind up having two rrddata section again, and that went wrong.