Thank you, guys! sds,

I have changed it to "SMTP-Einstellungen testen". Should be correct in the next pfSense release.

@iso70x: @kevindd992002: @iso70x: I have just had to restore a 2.3.4 config onto a fresh 2.4 system (upgrade to 2.4 via GUI failed, long story, file system got corrupted somehow). Doing a fresh install of 2.4, then restoring the 2.3.4 config backup worked perfectly. All packages were installed automatically and everything seems fine. Entire system back up and running very quickly. Restore was done via gui diagnostics menu after the system was up and running with default config btw. For ref, this was done on a PCEngine APU1D4 via a serial cable. I see. Did you reinstall it in UEFI mode? No, standard bios I’m afraid. The APU uses the open source coreboot firmware which I believe is comparable to legacy bios. I see. So we're not UEFI-compatible, bummer :(

With that formatting, just run the pkg info pfSense-base package. You can get close with the contents of /etc/version and /etc/version.buildtime

In other words: You did something unsupported, and to the surprise of nobody, it broke. Don't do that.

Worked like a charm. Thanks all.

3 cable and 3 different machines (2 Linux and 1 windows). No luck on any of them. If I'm lucky enough to have the device detected as /dev/ttyUSB0 I still cannot connect. I get input/output errors from minicom. Putty and screen just do nothing. I have made sure to  run those as sudo or to do a chmod -R 777 /dev/ttyUSB0. This has worked before as recent as a couple weeks ago. The only change was the attempt at updating.

About the only thing that makes sense based on what you have said is your eMMC is failing. The fastest thing to try is installing an mSATA and trying again.

Long delays on boot are almost always caused by a DNS resolver/forwarder misconfiguration. A lot of the services that are started on boot really need a fully working network connection with working DNS.

To change the filesystem to ZFS which supposedly fixes a problem with pfBlocker dnsblocklist statistics tracking which causes everything related to php to hang, a complete re-installation of pfSense would be required.

Thank you PiBa, that worked. I installed it and rebooted, the error went away. I un-installed it and rebooted and error is still gone. Thank you again

Ok, did the upgrade this time and that took a few minutes, but at least I know everything is up to date. I was a little concerned since I have been doing 2.4.0.RC updates for about a year. All looks good now. Thanks

Thanks, while I did not see which process exhausted the memory, the fix an bz in that post you mention appear pretty specific so its probably safe to assume that was the issue.

Ram disks are always UFS on pfSense/FreeBSD. Technically you could use another filesystem for them but nobody does that because UFS is the standard filesystem of FreeBSD.

@jimp: @Music: yes that works fine i also did that. But i have a few custom files for my DNS resolver. So when reinstall and then do the config i still need to copy certain files to the correct directory otherwise Unbound etc will not start. Then you can utilize the "Backup" package to easily get an archive of those files to restore later. Also if you put use a glob to specify your files in the advanced options of the resolver (e.g. "custom*.conf") then unbound won't fail if it can't find the files. Or you could get even trickier and use the System Patches package to store them in config.xml create them for you, but that's not quite so easy to maintain. ok thank you will look into that

Thanks!

If either one of your WANs is PPP, then default gateway switching can fail in this way. It's a known issue we've tried fixes for over the years but always ended up backing them out because something else failed. You must have a default gateway, however. It's possible that in the past the PPP gateway was becoming default even when it wasn't set to be.

Ooops, I found the problem…. I have used the wrong VM. I had updated my Pfsense to x64, but misnamed the VM... :( Now uing the correct x64 vm and the update worked. Thnx for the tips!