@cclcyber I'm having the same issue. Did you ever find an answer?

@havastamas Okay, the server might have been down, thanks.

@jimp Thank you the explanation; much appreciated!

Once 22.05 comes out, I will update to that and then take a backup config once again and then as you mentioned hopefully by 22.09, when I update to that - I will take a new backup and then also would be able to save the installer for my non-Netgate hardware to save some steps for future rebuilds.

One more additional question; Do you foresee Netgate getting rid of CE? Or Netgate start charging for Home/Lab use? I am trying to make the decision if I made the right call to move away from CE to Plus for my Home use router/firewall.

@nasheayahu It's not really designed to upgrade pfSense via USB. You can kind of do it though, for instance, to convert to ZFS.

This process allows pulling the config file during installation:
https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html#recover-config-xml-from-existing-installation

I would definitely make sure you have your own backup though. Always a good idea.

Since you have a 2100 you want the Plus software so you can open a free ticket. CE is the free, AMD64 software.

That kind of segfault in pkg can also happen if you have a package installed that is not present in the current release. The most common one is an older Zabbix version. You should be able to uninstall that package and then upgrade as normal.

@bingo600 GOOD NEWS. Solved it, and it IS due to a bug of RAM disk + ZFS.

See here.

@someone464 I tried the exact same progress as yesterday today, it magically works now, very weird.

@brian-smit To your question about it not being offered:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

@rcoleman-netgate said in Ver 2.3.5:

AMD Geode or other 32-bit only CPU.

My advice would be to get somewhat current hardware then.. 32bit only - that hardware has to be what 10+ years old.. time to move on..

@adelaide_guy Same blocker. Next, opened a support ticket. Appears they need a cert output from in-place upgraded CE system to correct their backend (asked if the system was in-place upgraded CE migrating to Plus or newly downloaded CE v2.6 upgrading to Plus - might be different fix routes). Anyways Netgate support was awesome! Migration from CE to Plus is complete.

Fix: start a new taclite support request.
Result: Chris verified the issue and then resolved it which allowed the system to upgrade from CE to Plus. Amazing customer service Netgate!

@aspiringnetworkadmin I might be misreading that -- it could be the first is the ISO and the second is the USB file.

I had to copy cert files from a running box to the installation with issues and then it worked...

/etc/ssl -rw-r--r-- 1 root wheel 7544 Feb 15 16:54 pfSense-repo-custom.cert -rw------- 1 root wheel 3242 Feb 15 16:54 pfSense-repo-custom.key

@steveits Correct.

Yeah, 2.0.1 is more then 10 y old. So I assume, your hardware is as old as well and could be incompatible with recent pfSense / FreeBSD versions.
If you want to still use it try to get the latest BIOS for it first. Maybe it works with it.

Aside from this any reason for hesitating to upgrade to a recent version?
2.3.5 was the latest version which was available for 32 bit hardware. So I'm wondering if your hardware is still 32 bit.

Hi there,

finally, I was able to update it, it is very strange, it was failing before on one package listed in the logs above, but today it was crashing many times by retrieving the other packages as well, but in the end, was able to get everything and make an update. I lost the system for 10 minutes after a reboot, I thought tomorrow I will have a very "nice" morning in the office with being hit by hundreds of questions about why the network is dead... The system is now alive, but during the boot process in logs I found some logs which do not really looking good, tomorrow will be more clear whether everything works as before :)
BR,

@cityunionmission There have been a few posts in the last week or two about IPv6 having problems with packages, at least. Try checking "Prefer IPv4 over IPv6" on System/Advanced/Networking. That affects only connections from pfSense itself per the docs.

Have you looked through https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html ?