24.11 update refuses to get going

beerguzzle

Netgate 1100, 24.03 running currently. I went thru the pre-update prep at per the "Pre Upgrade Tasks" in the documentation, rebooted, etc.
While the pfSense webpage shows that 24.11 is available for upgrade (most of the time), it refuses to get off the ground. If I click the cloud icon, it takes me to the System/Update/System Update page, then 24.03 is up to date. Same deal trying it with option 13 from the CLI options:

Enter an option: 13

Messages:
Your Netgate device has pfSense+ as part of your device purchase.
Updating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries: . done
pfSense-core repository update completed. 5 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: ........ done
Processing entries: .......... done
pfSense repository update completed. 710 packages processed.
All repositories are up to date.
Your packages are up to date
Netgate 1100 Netgate Device ID: 9ce8acc6eec9f5b88a99
Serial: NTG2150001436

I have walked thru the Troubleshooting Updates doc and nothing got it going. Advice please???

stephenw10

Since 23.09 upgrades are opt-in. The dashboard will show you an upgrade is available but when you reach the upgrade screen you need to select the new 24.11 repo branch from the drop down.

This prevents the vast majority of pkg issues we used to see.

Steve

beerguzzle

@stephenw10 Thanks for the clue here. I selected the 24.11 branch in the System Update GUI, and then it complained "Another instance of pfSense-upgrade is running. Please try again in a few moments." Per another posting about this message, I then tried option 13 from the CLI and 24.11 got going. This setup is whacky/buggy, IMHO.

beerguzzle

Yippee, finally at 24.11 on my 1100. Thanks for the tip.

stephenw10

Yes that error could be handled better. The 1100 hits it more than most because of the relatively low powered CPU. If you come from the dashboard to the update page the check may still be running in the background. But just refreshing the page should show it available as you found.