@grimson Actually I couldn't ssh or WebGui connect because I couldn't know it booted. I just saw it suck in booting. So you can call me dumb but I would like to know what would you do when finding a problem totally new to you. I tried what ever I could think for hours before coming to the forum but that wasn't something I could think because I don't have the experience. The link you sent I had already seen but it didn't help because it was VAGUE and for that reason unhelpful.Now, as for the marketed product names I am sorry if I can't read between the lines IN THE OFFICIAL PRODUCT PAGE and find that my intel called Celeron processor isn't a Celeron but an ATOM. So again call me dumb or an idiot and proceed.

Yup, it is/was: https://redmine.pfsense.org/issues/8910 Plus there are some other tickets covering related things. It is fixed now and will be in 2.4.4p1 or is in current 2.4.5 snapshots if you're able to test. Steve

It seems like the subnet between your ISP router and IPCop is 10.0.0.0/24. If you put the pfSense WAN into that subnet it's gateway must be ISP routers internal IP address. So I would expect to see the pfSense WAN set to something like 10.0.0.100/24 with a gateway of 10.0.0.1. Steve

The only thing not backed up there would be packages pulled in directly from FreeBSD by specifying a different repo. Those are not directly supported though What did you actually have installed from FreeBSD? Steve

Is it something that re-appears if you delete it? If not it's likely an artifact from the php change during the upgrade. Steve

@anh I am on Amd platform. Not sure if this help or not

A few more hours in, and the WAN is holding up, thankfully.

I'll probably release this feature in a snapshot in the next few days. The official -p1 release is harder to pin down since we never know what is going to turn up in testing - Likely weeks rather than months though.

@piba Good to know. That was my only concern.

Swapping in a straight up DSL modem resolved this issue. Looks like the draytek router was to blame, perhaps a power outage reset it into an unusable state etc.

@msf2000 said in Where to Find Packages for 2.4.3_1?: Where can I download previous release of packages? You can't. You could checkout the sources for the packages on a commit before the switch to PHP 7.2 and then build them yourself and install them manually, if you know how to do it.

Solution! Diagnostics / File Edit Edit /boot/loader.conf.local Insert the lines below: i915kms_load = "YES" drm.i915.enable_unsupported = 1 Save and restart!

i will let it continue to run and see if it was just a blip or something. Thanks for having a look..

The -p1 images are only for Netgate hardware, not installations using the community edition. There were no -p1 installers for CE.

If the users were not in the config before the upgrade, nothing in the upgrade could have done that. I don't see any sign of local users other than admin, or signs of RADIUS or LDAP being used. Something or someone else must have removed the users from that configuration before. There haven't ever been any bugs that I can recall that would remove all users except admin. I'd look for an older backup, see if they are in there.

@jimp said in V2.4.4 - The firewall has enountered an error: pfSense-upgrade -d Removed pfBlockerNG, rebooted, ran pfSense-upgrade -d with no errors. And no dashboard errors. Re-installed pfBlockerNg and everything seems to be working now, Thanks.

Something must be failing at boot time for that to happen. Can you monitor the firewall console while it boots to see if there are any errors?

@peterfranca said in Version 2.4.4 completely broken on my server. Could someone share the version 2.4.3?: After I had upgraded my pfsense from version 2.4.3 to 2.4.4 I am having weird errors and the server sometimes reboot without a single warning. What are the "weird errors"? What didn't work? We need exact error messages and more specific information. If you do not provide the details of the problem, it can't be fixed. If you just say "It's broken" and try to roll back, future updates will likely still be a problem for you.