@stephenw10 Thank you ! And I want to repeat - pfSense is awesome and I’m glad I made several years ago to to switch to it !

Mmm, we'd need to seem more of the boot output I think to know. If you can install and boot 2.4.5 OK but then when you restore your config it fails that seems more like a config issue. Does it fail in exactly the same way when you do that? Steve

Yes you should be able to allow to 'see' the available upgrade using those steps. You might also consider installing 2.4.5 clean and importing you config though. 2.3.4 to 2.4.5 is a big step. Steve

:)

Nothing has changed there in 2.4.5 as far as I know. It's likely just luck it only happened now. Steve

@McDing I guess you learn something new every day. I always changed my config file before uploading it so I never saw this prompt to select new interfaces. Very Cool! Roy...

Correct

@stephenw10 said in PHP Error in pfsense 2.4.5: Oh, it only appeared during the upgrade? I thought you were saying it keeps re-appearing. Then if it doesn't appear again it's unlikely to be a problem. Just watch for futher alerts for a while. Steve Nope, it was a one-time occurrence. So yeah, I guess I can ignore for now. Thanks.

With screenshots: https://forum.netgate.com/topic/140169/update-failed/9 -Rico

@muppet You're right. In my case it seems to be CPU related. The utilization is much higher than before and therefore the individual cores cannot handle the load for the queue they're assigned to.

Sorted out. The issue is not related to the password itself as the error occurs even before the user get a chance to enter his password. The fix is to use either option from -o PreferredAuthentications=password -o PubkeyAuthentication=no or corresponding options in .ssh/config , this will prevent the client from offering the server all the keys it has available. I'm curious while that never happened before, as nothing changed on the user side.

@jimp Thank you very much for the help! problem solved

@jimp said in ERROR "Failed opening required 'Net/IPv6.php' " - HELP: At this point the only sure way to recover from that is to reinstall+restore your config. Use 2.4.5. This is why the upgrade instructions tell you not to upgrade packages before upgrading to a new pfSense version. The packages are only compatible with the latest release. @jimp @Gertjan Can you please see that nothing is missed here ? https://forum.netgate.com/topic/151956/restore-pfsense-setting-during-usb-stick-setup

Yeah that isn't the ADI one, that would be this one. pfSense-netgate-memstick-ADI-2.4.4-RELEASE-p3-amd64.img It will be on my public server in a bit, will PM you link.. Check the hash for yourself please. But promise you I grabbed it direct from pfsense.. it will be the .gz file. Please let me know when you have it, so I can remove it. edit; Ok sent you a link in PM I don't have the p3 version - sorry... Lucky I hadn't gotten around to purging those yet...

See https://forum.netgate.com/topic/151715/crash-reporter or https://forum.netgate.com/topic/151675/2-4-5-update or https://forum.netgate.com/topic/151780/pfblockerng-devel-install-php-startup-errors-failed-to-load-readline-so or https://forum.netgate.com/topic/151780/pfblockerng-devel-install-php-startup-errors-failed-to-load-readline-so or ... etc

Fixed. For posterity.. I edited Config.xml manually and removed the "Deny Config Write" Line. Log out and back in. Fixed.

Update: I got myself out of this one by reverting the config to the stage before I created the group. Thanks Netgate for the backup feature :)

@bobbyp : I advise you to test this : go back to default settings. Then check if you can get to the list of installable packages. Btw : not being able to get a list with possible packages is most often an indication that DNS is not working for pfSense itself.

Hello: @ffuentes, You stated "My squid issue comes from before and I think is a config issue in my case...", a squid config issue or a pfSense config issue? Fist and foremost any kind of config issue would drive me insane! I would hunt it down and fix whatever was wrong. If that meant starting fresh until it worked (correctly) then that's what I would do (and have done in the past). Total PITA, but, I then know I don't have to play that "well maybe because I did/didn't do something and now that might be what's causing this new problem." SO FRUSTRATING!!!! Problem with this approach is obviously time (and money). Either way, you might want to consider fixing the issue so as to avoid a future headache. I'm guessing this unit is a unit in production so fixing may require doing it when the impact is at a minimal. Always hated that, but no greater joy than knowing the config is perfect and possible future headaches will be avoided (well at least that's how I felt). As stated previously, I don't use squid (not that I haven't experimented with it in the past and decided it wasn't necessary for my needs). My setup is very vanilla with a dash of a few VLANs thrown in. My conversion to 2.4.5 was easy peasy! No problems, less than 5 minutes total. But then again, I'm not utilizing pfSense to it's full potential. I just hope whatever issue(s) it is, it's found quickly and COMPLETELY resolves the problem for everyone. Feel so sorry for anyone going through this as pfSense is an awesome product!