@Popolou yes, there was no re-install packages option as no packages installed during new sw installation. Being connected to Internet was also key. I thought packages were installed from install.

Without the logs to check it's almost impossible to say. It's probably been overwritten. I'd guess some pkg uninstall script stopped maybe.

@SteveITS Thanks. I put it down for a bit, and when I went to look just now the option was magically there all by itself, so problem solved!

It should probably be re-assessed. As you say an interactive serial console is available for Azure installs. I have tested upgrading to 23.09.1 in Azure and never saw any issues. Steve

Make sure you have a backup config in case you need to reinstall. But you should be able to run pkg-static upgrade and agree to the offered packages from there to reach the complete 2.7.2 install.

It is. Probably related to the OpenSSL change that impacted pkg in 23.09.

Run pfSense-repoc -D and note the Model value. Don't post that output here as it contains private data. That should be shown as 'Amazon Web Services'. If it shows 'Unknown' open a ticket with us: https://www.netgate.com/tac-support-request Steve

Yes, you don't need a support sub to request an image so it doesn't matter what you select there.

@jimp This is now resolved, an upgrade direct from console did the trick :)

You'll probably need to wipe the start and end of the disk as described here: https://docs.netgate.com/pfsense/en/latest/troubleshooting/multiple-disks.html#clear-the-disk

How exactly did it fail?

@stephenw10 looks like the issue got resolved by itself today Thanks for your help.

@stephenw10 Many thanks, will review further. It’s up for a fairly decent price.

@lohphat I gave up awaiting further suggestions and just reinstalled from USB to 23.09 and re-upgraded.

@pfthbst said in Empty field "Firmware Branch" in <System/Update/Update Settings> after a fresh install v2.7.2: Under dns host override I redirected dns calls to ews.netgate.com to localhost. Ah, yes that would do it! Access to that is required to pull the dynamic repo data in 2.7. Timestamps in tcpdump are actually in epoch time but by default it displays that as UTC. I don't think tcpdump itself can use a local timezone, I could be wrong. If so though that would require some recoding to make the page show it as such. It's not a bug but could be a missing feature. Yes, it should be a new topic to discuss further.

@kiokoman thanks for the tip. Unfortunately fsck did not work. I will open a ticket. Thanks again and Happy New Year!

@noloader said in Where is /conf/upgrade_log.latest.txt located?: /conf/upgrade_log.latest.txt ^ right there you can either a) ssh in or; b) Diagnostics -> Command Prompt -> Download File or; c) Diagnostics -> Edit File Option b is a good option. Will get a copy on your local system, then open it there.

@SteveITS Thank you. I ended up doing this using an image provided to me from Netgate Support

@Stewart @SteveITS This was solved here. Due to changes in pkg, the new version of pkg may not be able to properly locate and use the CA trust store when running on the previous version before upgrading. If the firewall is unable to load packages or check for updates after selecting the CE 2.7.1 upgrade branch, run certctl rehash from the console, a root shell prompt, or via Diagnostics > Command Prompt. This will allow pkg to utilize the system certificates until the next reboot. This is true in 2.7.0 as well. Running the certctl rehash brought it up to be able to upgrade.