@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.

@techn01ddr01d hi there I was able to fix this by following the instructions Tubal listed on this reddit thread: https://www.reddit.com/r/PFSENSE/comments/9il2u0/pfblockerng_install_broke_my_installation/ To fix this I: Updated /usr/local/etc/pkg/repos/pfSense.conf to point the repos back to 2.4.3 Run pkg update Removed php72 ('pkg delete php72') Reinstall missing packages ('pkg check -d') Then I was good to go. In my case I was pointing to 2.4.2 but the same will apply for you but use 2.4.3 Fixed all my issues :) Let us know how you go. Cheers PDANZ

Cool. Thanks for following up. Steve

M4 large. I determined that everytime I tried to hard set the IP address I wanted on the AWS subnet it would fail. After installing and then terminating it several times, I could relaunch a new instance with an automatically generated IP address with no problems.

Thanks a million Jim! boot -s did the trick!

You're welcome to try the 2.4.5 snapshots which will likely become 2.4.4p1. There's no point releasing p1 before whatever errors are in 2.4.4 are found and fixed though. Steve

What type of interfaces were they? em? igb? Something else? Are they working after a reinstall?

@rgc Thanks, that did do the trick.

@chudak said in DNS Forwarder broken in 2.4.4: any clues how to fix it ? Add the two patches that you found here :https://redmine.pfsense.org/issues/8967 ;)

Seems to be working fine now. Not sure why a disconnected WAN interface would prevent me from accessing the webgui but in any event everything seems to be working just fine now. This week I'll upgrade the other end of my VPN and turn on Asynchronous Cryptography. Roveer

I've been using PFSense for 4 years now; this is the first major upgrade where I've had to remove packages. I'm overall very happy with the product, just want to help improve others' upgrade experience.

That card should be supported to some extent by the iwm(4) driver. But it won't work in AC mode and it won't work in hostap mode so you cannot use it as an access point. Steve

After some poking around, going back to boot partition ada0s2a, rebooting, problem is the same. I had made a copy of / on some spare space on the SSD. I changed /usr/local/share/pfSense/pkg/repo/pfSense-repo.conf to point to url: "pkg+https://pkg.pfsense.org/pfSense_v2_3_5_xxx and I did a pkg-static bootstrap -f and it seems the problems are solved: pkg is working nginx is starting at boot time How can I make sure nothing else is messed up in my installation? Thanks in advance, Olivier

@stephenw10 Many thanks for the answer.

Seems like "sudo pkg update -f" fixed the problem

Looks like there were some disabled gateways that I am guessing were being applied. I deleted them and the internet came back. Probably similar to this issue: https://forum.netgate.com/topic/135903/2-4-4-gateway-issue

Re-installing to 2.4.4 clean is quick and you can just import the config from 2.4.5, the config version has not been incremented. You can even do it during the install: https://www.netgate.com/docs/pfsense/backup/automatically-restore-during-install.html Steve

Just to close the loop here - following @jimp's instructions, I was able to install with Recover Config as advised. However, if I had it to do over again, I would have tried to install with 2.4.3_1 w/Recover and then upgrade vs. 2.4.4 w/Recover because the resulting install was very slow and became non-responsive whenever it brought up the WAN interface and while the install removed some packages, there were vestiges of the old settings in places like the Services menu and on the Service Status widget on the dashboard. Unfortunately, it doesn't appear that the 2.4.3_1 disk images are available anywhere. To resolve the slow WAN issue, I inspected the config diffs that the install/upgrade recorded and notice "an unknown interface change" - it turned out that advanced DHCP settings were enabled for the WAN interface with none entered so I disabled it and that seemed to solve the WAN access and performance issue. To eliminate the package vestiges, I installed the various packages and then removed them to purge them fully. I probably could have downloaded the config and removed any semblance of the packages instead but wanted to rely on more supported methods. The system seems to be working properly now and I really appreciate @jimp's prompt insight, help and guidance. Rock on! Cheers Lanner FW-7525A Intel(R) Atom(TM) CPU C2358 @ 1.74GHz 2 CPUs: 1 package(s) x 2 core(s) AES-NI CPU Crypto: Yes (active) Hardware crypto AES-CBC,AES-XTS,AES-GCM,AES-ICM

Thank you I have followed these instructions and ultimately upgraded the system from console and rebooted. It now appears to show the correct version [image: 1538209351479-2.4.4.png]

I'm an idiot Decided to add parameters (i915kms_load="YES", ...) to /boot/loader.conf.local in advance, instead of checking the functionality without them. After deleting /boot/loader.conf.local, everything was OK. Excuse for troubling.