Thanks for the pointer.  While I needed that option set, I also had to enable the checkbox for WebGUI redirect (System–>Advanced). BTW - A huge shout-out to the pfSense technical support team.  After struggling with this for a few hours, I opened a ticket and immediately had a couple of great engineers on the phone (maybe 2min wait at most).  Brandon and Chris helped figure out the problem in short order as well as clear up some questions about CARP, NAT, and NAT Reflection.  Thanks guys!

Well, one of my test systems now shows: Netgate APU Serial: 655dc6... While the APU part is correct, this device has never seen Netgate. Technically correct would be: PC Engines, APU

@securityconscious: Catch my fix here: https://forum.pfsense.org/index.php?topic=119290.0 This worked for me as well.  I had the same problem.

If I go to DIAGNOSTICS / ntopng Settings / Access ntopng, I can accept the certificate and enter ntopng. From DIAGNOSTICS / ntopng, I get a reset. the https: is missing in the DIANGOSTICS / ntopng item link. I am using port 3000.

Perhaps try this related solution which fixes a few things: https://forum.pfsense.org/index.php?topic=119290.0 Let me know if it solves your issue.

Updated 2.3.2 to 2.3.2_1 and got the same error. Solution is the same. But… what is wrong?

Update finished successfully: >>> Setting secondary partition as active... done. Upgrade is complete.  Rebooting in 10 seconds. >>> Locking package pfSense-kernel-pfSense_wrap... done. Success Thanks!

I'd try wiping the secondary and setting it up from scratch. You just have to get the basic settings done and sync it.

Seems like the pfsense package repositories are struggling with the load.  Have you considered putting Cloudflare in front of it?  It could cache all the packages for you and serve them from the global CDN.

This isn't specific to PFSense. I think it is a FreeBSD issue. I had the same problem on a 6005 and DC5850. Ended up using something Intel instead.

Transip runs KVM for it's VPS-es and has pfsense available as an install option. Don't know of any other provider doing this. Maybe some others let you install your own ISO though.

@muhammadanish: Hi I am trying to fresh install on SATA HARDDISK Version: pfSense-CE-2.3.2-RELEASE-2g-i386-nanobsd-vga Please Check/Read:  https://www.pfsense.org/download/  (Pick Your Platform) Pick Your Platform USB Memstick Installer The USB memstick image is meant to be written to disc before use and includes an installer that installs pfSense software to the hard drive on your system. This is the preferred means of running pfSense software. The entire hard drive will be overwritten, dual booting with another OS is not supported. The USB memstick file is named pfSense-memstick-2.3.2-RELEASE-arch.img.gz. where arch is i386 or amd64, depending on the CPU architecture of your system. **Embedded (NanoBSD) The embedded version is meant to be written to disc before use and is specifically tailored for use with any hardware using flash memory (mostly Compact Flash) rather than a hard drive.** Flash memory can only handle a limited number of writes, so the embedded version runs read only from flash, with read/write file systems as RAM disks. The NanoBSD platform has two OS slices and a config slice. One OS slice is used to boot from, the other is used for upgrades, and the config slice is where the configuration resides is held separately. There are two variations of the NanoBSD platform: The default version which uses a serial console, and another that supports using a VGA console. Each of those variations also comes sized for different sizes of storage media. The filename for NanoBSD downloads is laid out as follows: pfSense-2.3.2-RELEASE-size-arch-nanobsd.img.gz. In that filename, size can be one of 1g, 2g, or 4g. The arch, as above is for i386 or amd64. The nanobsd part can is either nanobsd for serial console, or nanobsd_vga for the VGA-enabled version.

Try it. It will work fine. Particularly so if the interface names do not change. Not sure where you read that you cannot load a 2.1.X config onto 2.3.2.

Ok so figured out how to get this done with HAProxy.  I like it.  Thank you.

Same here, using the IPSec widget on the dashboard causes PHP-FPM to die after a random amount of time. Removing it from the dashboard for now…

Tried manually adjusting the xml via the console, but no luck. Adjusted the config via the Web Gui to make the interface hn0. Saved, powered down. Uploaded the new VHD and bingo, all good now. Thanks for the pointer.