upload_config() should be found in /usr/local/pkg/autoconfigbackup.inc It could just be an issue while the system was booting and reinstalling all packages, including AutoConfigBackup. or maybe something went wrong with the package reinstall part way through installing AutoConfigBackup. You could reinstall AutoConfigBackup and then use it to do a manual backup, make some config change and check that it has done the backup and that no errors are logged.

7 different sites updated no issues!  :)

Hi, It's now OK. I have manualy install the amd64 upgrade. This is due a backup done on a i386 system… Thanx. Cyril

@luma: Hi there, I remotely upgrade through webgui a APU amd64 2.2.4 pfSense full install. All seemed to went fine until I discoved FreeBSD system packages installed myself not working anymore… What a suprise, the system switch to i386 ! Any idea of what happened ? How can I remotely revert to AMD64 ? Thanks and regards Same problem as you. To try to correct I have downloaded the Full Update 2.2.5 for amd64 tar ball. I have run the manually update with the tgz file. It's still in progress. I'll keep in touch. Cyril

@NOYB: You might try a process like this to put the system into a KISS state before applying the upgrade. I've yet to see a situation where that was necessary. Way too much effort. If your packages fail to reinstall, just clear the lock and hit reinstall packages after it's booted back up.

You were right ! I did some cleaning in /tmp and after a reboot everything is working fine.

Connect to the serial console. https://doc.pfsense.org/index.php/Locked_out_of_the_WebGUI

What's the exact message you're getting?

thinking I will take you up on that…Will try moving my wifi to its own separate lan this weekend. thanks..didnt think of that one

It is not incompatible with the motherboard as I have run Windows 7, Windows 8.1, Windows 10, Ubuntu, and Linux Mint with the same set up without an issue.  My question is simple, does pfsense support installations on m.2 PCIe-based SSDs?

and how many interfaces does this computer have? You want to do this physical or with vlans?  Do you have switch that supports vlans?

What you did should have worked.  Edit the config.xml and change the interfaces to the new interface names (igp0/igb1?) Beware search and replace or you'll probably whack some crypto blobs. Be sure every replacement is actually an interface name. Should only take a couple minutes.  Then it should restore without the interface reassignment phase. Not that that's what blew up. It should have worked.

im looking to get a hang of the fundamentals. Then configure your network in a fundamentally-sound way.  Not one that requires hairpinning traffic in and out of 192.168.1.1 to get from 192.168.1.26 to 192.168.100.3. You also have to disable NAT in pfSense. or you won't be able to directly address 192.168.100.0/24 at all.

I installed the openvpn export package and all is working fine now.

MEDIUM ERROR Smells like a wonky disk. pfsense 2.2.4 32bit i386 builds are being phased out.  Why not install the x64 build?  The hardware is certainly 64-bit.

sir no luck…

Hi again :) Thanks for the quick response. Unticking the forwarding mode actually seems to have fixed it. Not sure where I picked up that I had to tick this setting, but it seems to do the trick. Many thanks for that!!!! While we're at it, would you know if I should tick the "Block Private Network" box in "Interfaces: WAN"? My understanding from the contextual help is that because I'm behind another router that I need to un-tick this? Is that corrector should I leave it ticked? Many thanks again for your help!

As the others have already said, this is dead simple if you know what you're doing.  Hopefully you did NOT specify a gateway for your LAN NIC. Post screens of Interfaces - LAN, and Firewall - Rules - LAN.

there is a HUGE freaking difference between 7 years and 12 years in computer tech… Freaking HUGE!!!