Many PHP errors after config backup restore

Grimson

https://redmine.pfsense.org/issues/8938

Don't be dumb and try to use outdated and unsupported pfSense versions.

Rico

Download and install the latest 2.4.4-p1 release, update to 2.4.4-p2, restore your backup and everything will be fine.

-Rico

demux

@grimson I was not aware that I need to update before restoring the configuration. I was not aware that it reinstalls the packages. I was not aware that this could result in an unusable system.
Life long learning...

demux

Thank you very much. I will do a complete reinstall with the latest version and will then restore my config backup.

Grimson

@demux said in Many PHP errors after config backup restore:

Life long learning...

Your first lesson is to RTFM and follow the forums, then you would have been aware of all this.

Also keep up to date with your security software, and yes this includes pfSense. pfSense 2.4 was released on October 12, 2017 and there have been multiple security issues fixed since then. Running such an old version is simply moronic.

Rico

FreeBSD 11.1-RELEASE-p10 is pfSense 2.4.3-p1 released 2018-05-14

-Rico

Grimson

@rico said in Many PHP errors after config backup restore:

FreeBSD 11.1-RELEASE-p10 is pfSense 2.4.3-p1 released 2018-05-14

-Rico

Still heavily outdated and doesn't change the result.

renat_kaa

I also got such issue (a lot of php warnings) with latest 2.4.4-p2.
https://docs.netgate.com/pfsense/en/latest/packages/fixing-a-broken-pkg-database.html
That's worked for me)

JeGr

@Renat said in Many PHP errors after config backup restore:

I also got such issue (a lot of php warnings) with latest 2.4.4-p2.

You normally don't "get" these errors out of the blue sky. Especially not the PHP ones that clearly indicate that someone installed packages from/for a newer version of pfSense to an old base system, the got force-updated only partially to some new packages throwing the system in a fit.

Also changelogs and update notes/warnings clearly state those "problems".

renat_kaa

@JeGr thanks for your reply. In fact there was unexpected issue. No updates, no upgrades.