Good to read that your issue has been resolved. But, you should have checked well before posting your problem here.

Had to do a USB install using 2.4.4 and it's up (mostly). But the PhP7.2 is still throwing warnings and messages to me from pfBlockerNG.

@gregeeh said in Console fails to boot after 2.4.4 upgrade: Added the following to my /boot/loader.conf.local and the console now boots up correctly. kern.vty=sc Yep, same here.

Run through the suggestions at https://www.netgate.com/docs/pfsense/install/upgrade-troubleshooting.html

It seems everything is up to date. Thanks @jimp

oh, ok ... I see no reaction over some minute and I thought it hangs. I give them more time ... I work on a Hyper-V virtual machine ... speed should be good

It looks like there is a device with an invalid name in that file. I'd check it for anything with unusual characters for example. It may just need to be removed and re-initiallised. Stop the DHCP service whilst you do that if so. Steve

it is a class 10 SDHC, 4GB. The slow speed shouldn't matter in normal operation, I assume. But I'll get something faster occasionally. That 40min without any internet connection was painful. Roman

@jegr Have just experience a similar issue with updating acme package

I ended up doing a fresh install and then upgrade. This time it worked... I didn't try the refresh or incognito...next time. Thank you both for the help...

https://redmine.pfsense.org/issues/8915 That specific case is harmless. We'll have a fix in 2.4.4-p1 for it.

Nevermind. Figured it out. I had IPV6 disabled.... once i renabled it, the update worked.

Hmm, it would normally show it has found the config just after the 'launching external config loader' line. It also gives you an alert on the dashboard but I think only if you restore the config after the initial boot. Steve

@wordo said in CVE-2018-6922 (FreeBSD crash due to TCP fragment reassembly vulnerability): Thanks! But running HAProxy or OpenVPN on 443/TCP for hotspot compatibility would be affected? I also don't see such a high risk, but was wondering what the reason behind not pushing a new kernel to 2.4.3 release. Because the next release is 2.4.4. Users running 2.4.3 should update to that when it is available.

https://forum.netgate.com/topic/135395/where-to-download-old-versions

@stephenw10 thanks a lot, i boot it from another Computer with 2 Network_card, had Access to web_GUI. and changed what you said: - System > Advanced >Serial console enabled, - System > Advanced >Miscellaneous: moved /var and /tmp to RAM and now it works in my Hardware as well.

@stephenw10 I couldn't find the emoticon of Elon Musk holding a spliff.

@derelict Ok, so 2.4.4 definitely got me the driver. Separately, moving from my old to new was a bit clunky. Upgraded my old from 2.4.3 to 2.4.4, backed up config. Uploaded new config to my new box, prompted me to adjust the interfaces then apply. Hit apply, it complains about the browser not supporting cookies. I tried being smart and manually adding "cookie_test" that it was looking for but nothing. I'd enter in the correct credentials, it'd refresh but not redirect. Eventually I think it rebooted, and I couldn't access it. I then determined it applied my config but not the interfaces. I set the interfaces to the correct ones, but still not accessible. When I reset webConfigurator password, then everything kicked in. I think it had something to do with backing up on an HTTPS to an HTTP. My old box was using HTTPS on 4443. Best guess anyway.