@cmb: That's what happens when you have the wrong URL hard coded under System>Firmware, Updater Settings tab. Now in 2.3 and newer, it's impossible to switch architectures, since it's no longer doing the monolithic updates of old. That explains it. I hadn't noticed that the URL was incorrect. @cmb: Before upgrading any 2.2.x or earlier system, it's a good idea to double check System>Firmware, Updater Settings, and make sure you have "Use an unofficial server for firmware upgrades" unchecked. Then you'll stay with whichever architecture you have installed. With the old style of updates you could (with some caveats) switch back with another upgrade to the other architecture, but that's not possible once you're up to 2.3. Backup your config, reinstall 64 bit, restore. I did notice that the option to manually supply the "firmware" is gone now. I surmised that this had to do with the move to the package methodology. I made a config backup before performing the upgrade, and was able to use that to successfully restore the config and RRD data post reinstall to 64-bit. Thanks for your answer. I appreciate it.

Thank you - and indeed it all worked smoothly - perfection. Thanks again!

Thanks for your help and hard work on 2.3!

@cmb: @chpalmer: I figured it was because I had gitsynced earlier today. Guessing in your case you gitsynced to RELENG_2_3, which is 2.3.1. I did.  :)

Yes, that's no longer big enough (1 GB image has less than 500 MB available for the OS with two slices). https://doc.pfsense.org/index.php?title=2.3_New_Features_and_Changes#Security.2FErrata

I thought I had the same error if I loaded the webpage before the update.  After about 9 minutes the firewall finished the upgrade and rebooted.  No issues yet and working great after the auto reboot happened.

$99/yr https://www.pfsense.org/our-services/gold-membership.html It also includes access to the book, which is another great resource.

Hi johnpoz I will try as soon as possible and report back. Thanks

I ran the upgrade a third time and it took.  Not sure why it failed the first couple times…

Hi! I've already disabled the HT function these days. All is OK, but it is not a solution. Same thing is happening while pfsense v2.3 install. I tested all the newest pfsense releases, none is working with 2 CPU and HT enabled - Installation hangs up ! :S Somehow, 2 CPUs without HT is much better option than 2 threads / 1 core and 1 CPU option supported by the system. Let's wait, maybe some day a fix will come to this issue. regards, Grzegorz Leśkiewicz

can pfsense resolve?  Under diag, try to resolve something - if pfsense can not resolve then anything using pfsense as dns is not going be able to go anywhere..

Thank you so much for the verification!!

My ISP attempted to hide the bridged mode setting using the CSS file for their web interface. ??? Like I said, attempted. ;)

That's great, thanks Jimp. I'll take your advice and install a new 64bit appliance with VMXNET adapters. Much obliged!