I have a post over in upgrading/troubleshooting. This is cool pretty excited about the release. I have a number of system running 2.7dev. But am unable to upgrade them. Update page just shows "Unable to check for updates" It's been 18 days since release and I'm surprised not to see any chatter about this. I am not finding any official stuff on if this upgrade path is supported or not supported but I sure would like to be able to do this. Verus a clean install and restore from backup. But I am not finding where this is or is not the only way to get this upgrade done.

@fireodo Yep, we're aware and we're paying attention.

@SteveITS Thank you for your answer

@Stewart said in Upgrade from 2.4.5 to 2.6: @SteveITS So, is it OK to go straight from 2.4.5 to 2.6.0? I went from 2.4.5 to 2.6.0, but I did a clean install of 2.6.0 and restored the 2.4.5 config.xml file and it worked great. I don't know if the direct upgrade process works that smoothly. Ideally you'd test the process on-site and if it fails, be able to to a clean install of 2.6.0 and restore a fresh backup config, and if that works, ideally it'll work at your other sites.

@Rico said in SG-1100 upgrade horror, now brick: No valid device tree blob found! WARNING! Trying to fire up the kernel, but no device tree blob found! That error implies it has failed to load the dtb file at boot. That means the file it tried to load wasn't present. So either it failed to access the file because it couldn't see the media or the file wasn't on the media. Or that the file it was trying to load was incorrect. The latter was the case here, the uboot env that contains the file name was wrong. Steve

@rcoleman-netgate said in Minor display bug: When did you download this installer file? Ryan: You sent me the link to the file on 03July at 1250 PDT. And it worked very well, thank you.

Probably since you used sdb1 and not sdb. That is a full disk image so must be written to the disk directly.

@xgiovio Sure but as I noted we will move Professional and Enterprise subscriptions one time during the subscription period. But the terms on those subscriptions do dictate no transfers. If you are not a TAC Professional or TAC Enterprise subscriber... the TAC Lite license is still free (at the time of commenting) so there's no reason to get a new one. It's the least painful path.

@lrqnet I thought this looked familiar. Thanks for the followup!

Putting this out there in case it helps others. I kept dorking at this, tried again when 23.05.1 came out, but still couldn't get the upgrade to work. I opened a support case online, truthfully not expecting a lot of help (I have the free home-lab style license, no support). Netgate TAC responded very quickly to the ticket (maybe 15 minutes), reviewed my notes, and requested remote access if I was ok with that. I didn't have an issue with it, provided them access, and after some digging, they found an issue with how I was loading my Solarflare 10gbe NIC. I found two ways to do this, one using /conf/config.xml with <earlyshellcmd> and the other was in /boot/loader.conf.local. I chose to use config.xml because I used that for something else, it was easy enough. The issue was in how the NDI was being calculated; the 10gbe NICs were not being included in the calculation. TAC stated that the proper way to load the NIC driver was with loader.conf.local. They made that change, I rebooted, and had a new NDI. I already had a reg key I created a month ago because I thought it was a license key issue. I stuck that on, and upgrade was good to go. This was my first exposure to Netgate TAC, and I was really impressed. They were very quick to respond, even though it was limited to the ticket (not live/phone/chat, because, I don't have a support contract). Also taking into account, this was my hardware (Dell R210ii), not a Netgate box.

@utendar Also do you have a default route in System/Routing or Ststus/Gateways?

@jimp Ah sorry I missed that thanks!

Your upgrade did not complete successfully. Apparently you still have the older version of the PHP code on your system. The code in the file referenced in your error changed between versions 2.6 and 2.7 of pfSense. So, some of your system got updated, but not everything it would appear because the new g_get() function is not on your system. At this point I would copy off your config.xml (or access your most recent backup if you have one) and reinstall using a downloaded 2.7.0 CE image.

@rcoleman-netgate I will check, but with testing istance of pfsense I have problem with github.io repositories, too. There I also have snort with "over configured" its configuration.

@SteveITS gotcha! Thanks.

@bingo600 I am not seeing the "Devel" branch to upgrade from 2.7 to 2.8 for my VM...even after rebooting twice. [image: 1688156267079-screenshot-2023-06-30-at-2.40.24-pm.png]

@phil214 said in The upgrade process is still broken for 23.05.1: Our confidence in Netgate is decreasing and this is pushing us to look at other solutions for linking our office and cloud infrastructure Be careful. The very same 'ISO' "pfSense 23.01" has been used to init thousands of pfSense installs, and nearly all have left 23.01 to go to 23.05 or even 23.05.1 or whatever intermediate version. So, upgrading from an identical situation, works. And I'm of course very aware that "it doesn't work for all of us" as we all have to choice to set up our own pfSense 'as we want'. For example : the only difference between your system and mine is : the settings. And also : the hardware used - mine is a 4100. The uplink can also be a factor. What I want to say : whatever you change, you could bring the same situation with you. What I advise you to do : do the thing that works. Go TAC Netgate. Ask for a 23.05 or even a 23.05.1 IS. Burn it to a USB drive. Install. DO NOT ( !!!!) import your settings : just make WAN work - that's all !! NO "enter DNS IPs" no NAT or firewall rule stuff. Just a WAN, LAN and you. Now check that it shows upgrades. Do so if needed. Test basic operations. Now, import your"23.01" saved config. Test again. If it is broken again : you know where to find the issue ;) Mark your saved config as 'bad - don't use' And you know how to get rid of it.

@onetwo see if there is an error: https://docs.netgate.com/pfsense/en/latest/troubleshooting/firewall.html#new-rules-are-not-applied