OK I think I've resolved the issue by forcing a reinstall of all the pfsense packages. While ssh'd in to the box and in a shell, I ran pkg info | less to look at the names of all installed packages. I ran pkg clean -ay to clean the archives. I ran the following to force a reinstall of all. pkg install -fy pfSense-2.4.2 pfSense-Status_Monitoring-1.7.5 pfSense-base-2.4.2 pfSense-default-config-2.4.2 pfSense-kernel-pfSense-2.4.2 pfSense-rc-2.4.2 pfSense-repo-2.4.2_1 pfSense-upgrade-0.40 And now the web UI reports 2.4.2-RELEASE (amd64) built on Mon Nov 20 08:12:56 CST 2017 FreeBSD 11.1-RELEASE-p4

@blueadept: I have the vpn issue also. I found that after I restart the firewall, I have to log back in and restart the openvpn. That seems to fix the issue for me. Everything seems to be working and it shows the vpn up. The vpn users can connect but cant go anywhere. After I restart the service, it seems to work. Restarted firewall few times and also tried to disconnect and connect the VPNs. But still having the same issue. It shows that its connected just cant connect to them. Thanks for that, I was really hoping it would just be that simple to fix. But unfortunately that did not help.

@jimp: 2.3.5 is listed in the GUI for updates if you have the correct update branch selected, but 2.3.6 isn't that different from 2.3.5 at the moment (or 2.3.5-p1 when that happens). You may as well just stay there for the time being. Hmm, it wasn't appearing, it was showing 2.3.4 as the latest version until I switched to the dev branch. I'll keep an eye out, and will try on IE instead of Chrome when the next release comes around. Thanks for the help.

@Grimson: you got a valid point! I reinstalled my pfsense and now my OpenVPN Tunnel is working again :)

@mais_um: Hi Have you wait to package be reinstalled? Manually reinstall packages? I tried the Reinstall alternative from the GUI but that did not work (yes it finished successfully). However i just tried to first remove the package completely and than re-installing it and that worked! It even kept my settings for AutoConfigBackup. This topic can be locked, thanks!

Up ? :)

Connect to the console or ssh and run option 13, or go to a shell prompt (console or ssh option 8) and run this: pfSense-upgrade -d If that produces any errors, post them here.

Yes, those packages are fine. Keep a backup, as always, just to be safe.

Reporting in… My standalone SG2440 upgrade failed, too. The GUI said upgrade failed and the box became unresponsive. After digging up a console cable and driver, I bounced it to see a bunch of PHP library errors. I was up and running in a little less than an hour, after burning a stick with the latest release. I've got a bunch of other boxen to upgrade. How do I tell what broke? I've got the uprade_log.txt, but nothing's obvious so far.

Console access is nice to have for an initial setup. Did that last decade. A minimal 640 x 400 will do just fine for that purpose. Now i use the SSH access, and a tool like Putty. Their is no limit for a "screen size" - and very easy to 'setup'  :)

Solution: disable 'Monitor M-Wait' in bios Could be under Features tab > CPU Configuration

@rod1011: What happen after update does it reboot the system? Of course.

If your secondary system doesn't have that syntax then your secondary is broken in some way. The configuration did not upgrade properly.

@jimp: Try this: pkg clean -ya pkg install -fy pear-Net_IPv6 Didn't help, a user on another forum had me try this. However, what did work was SSHing in and selecting the upgrade option from the PfSense menu in the command line. It showed that 1 package needed reinstalling, and it upgraded, and was good to go after.

My bad - I had the ADI memstick inserted instead of the uFW recovery. Recovery seems to be functioning

@luke1018: Hi may I know how can we do testing (Implementing rules, new codes or configurations) on our local machine and once its ready, how can I duplicate it on the live machine? Is there a way we can do backup and restore to the live system? or to patch it? Strange. The very basic concept of pfSense is that it stores all settings in one file - witch can be backup and restored, even on another machine (if identical network interface names, otherwise you have to setup your NIC's again). Patching ? What do you mean ? You are aware of the fact that pfSense lives on github, which means sources are available ?

Look in Services -> Snort -> Alerts. I've found its better to run snort on the internal interface as if you use it on the WAN it logs the WAN address not the client that is natted.

[2.4.2-RELEASE][root@ FQDN]/root: sysctl kern.geom.debugflags=0x10 kern.geom.debugflags: 0 -> 16 [2.4.2-RELEASE][root@FQDN]/root: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 gpart: /dev/ada0p1: Operation not permitted Then I went rogue and tried my own: [2.4.2-RELEASE][root@FQDN]/root: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0p1 gpart: No such geom: ada0p1. As you may see, I have no clue how disk geometry works. I'm very happy I didn't for more than a few minutes offline though, now I have time to schedule a reinstall. Whoever came up with backup & restores on pfSense is a f*cking genius! They way packages reinstall themselves and everything is back as before it just amazing. Thanks for your help!

There are a few different possible issues that could lead to your situation, but without more information it's impossible to say what is happening with any certainty. First, go to the console or connect via ssh and run option 13 and see if it finds the upgrade that way. If not, capture the output and post it here so we can see what it says.