Well dadgum! Got it working. I did 2 things: 1. Switched the WAN to 1gb1 from igb0. 2. Found that a Cat6A cable was being used from the modem to the router so I switched it to Cat5e. One of those two worked, I'm guessing the Cat5e cable. I'll switch the interface back to igb0 at another date… Thanks for your time and help coxhaus and cmb, I know you are busy right now :)

@macboy6: cmb, did the CE memstick image also require an update?  I need it for another system and downloaded at release, but have not installed yet. No.

Looks like there's an issue in the config upgrade code with changing the parent interface in an edge case there. I'm looking into the root cause, but just editing the IP alias virtual IPs with CARP parents, picking the CARP IP, save and apply changes will fix in the mean time.

It's a bug - see https://github.com/pfsense/pfsense/pull/2867 and Redmine issue https://redmine.pfsense.org/issues/6144 Try the very simple and confirm that it will work OK restoring an area that currently does not exist.

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

That solved it - thanks!

I have the same underlying issue. This problem also affects the use of the /status_carp.php page. I have +100k states and using a CARP HA fw pair and get this error when using the CARP status page. As I needed the function to activate / deactivate CARP on this page I patched the file  /usr/local/www/status_carp.php and replaced $states = pfSense_get_pf_states(); with $states = 0; so the page loads but displays no states because of my workaround. René

I might have worked out the issue.  I had snort on the machine and I saw other people are having problem with that package.  What I did was delete the snort package and based on my users they say it is back to normal. Not sure if this helps anyone and I will still run some test to see but looks like the removal of snort might have fixed it Paul

OK, this has been partly solved - the ACB failure was down to a subscription issue which has now been sorted. However, I still think there is a bug with the ACB module, in that if the ACB registration fails, it messes up the GUI in a major way until you reboot. Cheers, Keith

Good to know it wasn't a problem – if it was, it would have been quite unusual given it appeared to be working correctly in every way. :-)

Don't do that. Replacing entire files is a bad idea, and this is one example why. If that was a more critical system file, your config would have rendered any system it was restored on inoperable. Using a patch is much better way to accomplish that task, and if things change too much, the patch won't apply, but the system will still be operational.

@phil.davis: I did mine by editing the config: Diag->Backup/Restore - download the config. Edit the config, look for the package name (e.g. I did tftp yesterday on a box) and delete the sections related to it - probably a menu entry, services entry, and a package settings section. Restore the config. (System will reboot) Thanks ill try this.

@robi: Nut package does not exist on 2.3. Yet….  :)

Hello! Thanks - switching to always R/W helped a lot  :)

The "Live CD" it mentions is an older platform that was removed. It literally ran the entire time from CD. If you installed to a disk in the firewall, it's not a Live CD after it's been installed, it's a Full Install.