Trying to upgrade to CE 2.7.2 from CE 2.7.1 -- No Joy

Wylbur

I am trying to upgrade a new machine from CE 2.7.1 to 2.7.2. I have my primary system running 2.7.2 and it is working fine. But the new machine has no option to allow me to upgrade. Having done this on the other machine, I know it is supposed to exist.

I have also looked for a 2.7.2 ISO to download. I'm willing to just blow away what I have on the new machine.... But I can't find where the download for this is.

Any hints about how to get this done?

SteveITS

@Wylbur see
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

And re: install:
https://docs.netgate.com/pfsense/en/latest/install/netinstaller.html

stephenw10

Legacy install images can be found here: https://atxfiles.netgate.com/mirror/downloads/

But, as you said, you should be able to upgrade.

Wylbur

This is interesting. Now I am showing that I am at 2.7.0 (deprecated version). And when I attempt to update using the terminal (not gui) via "13" it says:

Error updating repositories!
ERROR: It was not possible to determine pfSense-upgrade remote version
ERROR: It was not possible to determine pfSense-upgrade remote version

Upgrading pfSense-upgrade... failed

This system has sometthing over 3GB RAM, 2 SSDs, with over 300GB each. And a 6 core AMD cpu (something less than 3GHz clock) - smallest custom machine that our local Micro Center could build.

So, I decided do a re-install 2.7.0 from scratch just to see if it could be done and then immediately attempt the upgrade. So installed completed and I took option 13 and It immediately took the system to 2.7.2!!

I don't know why it wouldn't let me do that via the GUI since I had uninstalled any packages.

But it is up, responsive and accepting config options and the like, so far. It won't take me long to get it configured as the current system is, so this one can replace it, and the old system become the backup.

Wylbur

One other thing. This system ("hardware") will not use my Intel ethernet adapters. Even though it saw them during install, etc., I can see them for "auto" config (using "a", etc.), but then it will not work on the LAN side (can't ping the firewall/gateway system 192.168.1.1) sigh. So I pulled the Intel adapters and went with the RTL based ethernet adapter(s). BTW -- This is what started the problems, trying to get away from RTL. But it seems with watchdog, the problem I have with IP address change by ISP is handled. sigh.

stephenw10

For reference when coming from 2.7.0 you almost always need to run certctl rehash in order to see the update. That's fixed in 2.7.1 but it appears you may not actually have been on that.