No, that patch doesn't work. I haven't looked into turning that on in recent versions, that patch is super old. A packet capture of the exchange should show you the certificates being sent between client and server.

@wgstarks said in Notification if update is available?: There is also a script you can try- https://forum.netgate.com/topic/137707/auto-update-check-checks-for-updates-to-base-system-packages-and-sends-email-alerts/1 Will send notifications for all pending updates. Not just the OS. great, will have a look at that! thanks :-)

Which is why you really should list any and all packages you have installed in your OP...

@megs said in Consolmessage: Calcru : runtinme went backwards from 692usec to 494 usec for pid 0(kernel): Calcru : runtinme went backwards from .... It's a kernel issue (FreeBSD) : more info here : Calcru : runtime went backwards from kernel. Chech your time settings, NTP, BIOS, VM, etc. Btw : pfSense uses the FreeBSD kernel. This kernel is not developed here, but here.

OK, here's I fixed it. From loader prompt, I used the command(s) set kern.vty=sc boot note, using the set command is a temporary solution, read on... this got me to the pfsense console from there I accessed the shell and used the built in editor, vi, to edit the file located at /boot/loader.conf.local and added the line set kern.vty=sc which ensures this command is executed at each boot saved my changes, rebooted

same to me... wrong version in GUI after update to 2.4.4_2. ssh --> 13 --> now everything is ok (2.4.4-RELEASE-p2)

I can confirm that with 2.4.4._2, it's now showing swap space again for me, whereas it had disappeared prior. I have 32G of ram, and thought that maybe it didn't need it, and/or I was losing my mind as to why it wasn't there. I could of sworn it was there in 2.4.3. :)

@teamits said in Change IP: @pama said in Change IP: The local IT has disconnected pfsense nics from vsphere OK but then the symptom of slow web GUI and inability to access updates is to be expected. The slow GUI happens because DNS isn't working and each try must time out on all DNS servers before the GUI moves on. I was assuming the NICs were being reconnected after the IP change. Not sure where to go from here. The only issue I've had with changing IPs is the rebinding check not allowing the new LAN IP but I think that bug was fixed a while ago. pfsense can query the dns without any problem...

Will install again then, just for sure, thanks!

I don't get it, so what then? Just open the port in the firewall rule and allow any guest to connect to any host if they match the protocol or port?

@smartersolutions said in Garbage console output from new: I was wondering if you could provide step by step how to add this as I am also at this stage and would like to be able to try this for myself. Many thanks. James Be smart and you'll find solutions, RTFM: https://www.netgate.com/docs/pfsense/hardware/boot-troubleshooting.html#disabling-acpi and adapt it to your current needs.

I saw another post almost identical to this recently where the problem ended up being a bug in the terminal software (minicom, perhaps) where it failed to update/scroll when maximized. Restoring it to a smaller window allowed it to work. Maybe it's a client-side issue?

Thanks @viragomann for the answer, When I ran the function it did fix something in the records in the fs but it did not fix the boot issue, after using Dr. Google and some keywords in the search I came across this. TL;DR: Same process as you but they used the following command /sbin/fsck -y / This seemed to have fixed the issue and got all of the machines online. Thanks for your help, It definitely helped me.

it's done ! and it's working :) thanks @jimp your plan worked as expected, upgrade VM "in place" was a good advice. I only have 30 seconds of timeout in my RDP Session when disable / enabling CARP between nodes.

See your logs : @electricshock said in pfSense 2.4.4 (latest) and OpenVPN organisation: certificate verify failed About the video : have a look at the official "Netgate" videos

No errors in system log. No relevant errors in resolver log (only a few failed to resolve host : new_name.internal , due to devices that are already configured on the firewall but not on the dns server. Those entries have no concern with the void tables.) Regards

I apologize for the post earlier and believe I ended up finding the answer. I should have dug a little harder into the forum. The answer looks to be that it won't restore without modification to the XML and applicable interfaces at a minimum. Not sure about the other options in the config backup, but I'll play it safe and manually configure. Thanks!

Sorry for the delay, we have been busy: https://forum.netgate.com/topic/139375/pfsense-2-4-4-release-p2-is-now-available Thanks!

Hi Jimp, there was an ext-20-xdebug.ini there. I moved it out of the way, error seems to be gone. Thank you and kind regards, SnakeZZ