This issue is resolved. I opened a support ticket, and they had me reimage the device with the 21.02_1 image (they linked me the correct image to use). There was an option to recover an existing config before install, and using that I was able to recover my old config. System is back up now and working ok, original config intact, so it was an easy recovery. I have also learned about the free online config backup service PFsence provides. I will be using that from now on, incase this happens again. Thank you.

@n8lbv Don't shoot the messenger? Yes, 6 patches, bugs do happen, to err is human. You may not like it, but Patches are an easy solution, better than waiting for a next release, and faster than doing a fresh install IMHO. (don't need to drive onsite + you get to keep the updated BSD. How's that for a win-win )

@webdawg said in 2.4.5_1 to 21.02_1 Not Working - SG-2440: And then still have a problem. You won't need it with the new stuff.... Cross your fingers and hope for the best You hope,.... you can implement your entire configuration from config -......... anything.xml

@fireodo said in pfSense-upgrade 0.94 -> 0.95: It is fixed since this morning 0.95 -> 0.96 Solved. Thanks!!

@perphide No idea if there is any (known) password during setup

I'd go exactly as you described. Crate a new VM and install 2.5.0 Take a pfSense Backup from the existing 2.4.4 VM Shut down 2.4.4 and restore the config into 2.5.0 If anything goes wrong you can just power on the 2.4.4 VM again. -Rico

@gertjan what did you expect?

@gertjan In the afternoon update started from GUI was ok!

@jpgpi250 Some patience then.

@gertjan It was indeed a DNS issue but it was caused by something else. Time was not in sync and therefore DNS was not working. NTP was configured with DNS names only. So a what came first situation was established? The chicken or the egg? :) I configured an additional time source by IP. Had the time updated, restarted DNS and everything was fine. I do experience some issues with the DNS resolver sometimes. It's a different issue so I should open a new topic for that. It does not always resolve my Active Directory zones defined in the DNS resolver. Restarting the DNS resolver service solves this issue and I find that very strange...

@teamits Agree.

@dominikhoffmann Virtual NICs under VMware Fusion. [image: 1615629358834-screenshot-2021-03-13-at-09.55.07.png] You could even have another virtual Mac sat the other side of a virtual pfSense install.

@mtsgsd said in Am I missing something here? Shuttle XPC no graphics, no serial port: only two pcie slots in this I5 shuttle So which Shuttle XPC computer do you actually have. My brief look suggested most have lots of connectivity options. http://global.shuttle.com/products/productsList?categoryId=105

@discarn8 Hey men, I had the same problem, exactly the same problem, my solution was reinstall pfsense usb via front. This allowed everything to work perfectly.

@bainsley said in new user and not sure about these log entries?: What is the firewall syncing with? the kernel? BSD? Which filter? The rules? The kernel includes capabilities what I would call a "IP stack". And it can act as a firewall. Both are needed so the FreeeBSD kernel can do it's firewall thing, and that's what pfSense is all about. Firewall rules are dynamically reloaded after many possible sirconstances, like processses restarting, alaiase changed, or some user GUI intercation. many others exist. So you will see this : @bainsley said in new user and not sure about these log entries?: check_reload_status 400 Reloading filter check_reload_status 400 Syncing firewall a lot. If you are not using IPSEC, this : @bainsley said in new user and not sure about these log entries?: php 414 rc.bootup The command '/usr/local/sbin/strongswanrc stop' returned exit code '1', the output was strongswan not running? (check /var/run/daemon-charon.pid) is just a message that pfSense stopped IPSEC - and it was already stopped. @bainsley said in new user and not sure about these log entries?: php 414 rc.bootup. Creating rrd update script This happens when pfSense finds a 'new' interface or object to make graphs for. The graph data is stored in a so called rrd file. A scripts that runs every xx seconds, populates the rrd file with data . So you can have, after a while : [image: 1615535267192-9cc0b9bc-bbd5-43ca-a771-a05bffd2cf8f-image.png]