23.05 branch is now available for CE. I was able to directly upgrade today from 2.6.0 > 23.05 on server 2022 hyper v. No issues.

@jimp Just tried it - took a backup of my config using the GUI, created a VHDX of 20 MB. Init as MBR. Created one partition. Formatted it as FAT (20 MB is too small for FAT32). Created a folder "config" and put the backed up configuration file into it and renamed it "config.xml". I copied my regular VM definitions, just changed the name. So it uses the same virtual HDD as the 1st VM. Only difference is that I add the above VHDX file as a 2nd HDD in its definition. If I really screw things up, I shutdown VM1, boot VM2 - this restores the config w/o having to set up LAN etc. Shut VM2 down once it is up and boot VM1. So confirmed (and a big thanks) - any attached disk which is partitioned and has a partition formatted FAT/FAT32 with a folder "config" in it with a file "config.xml" will be used during all boot if present and copied, replacing your config file. After booting, it must be removed otherwise on each boot, the config.xml file on it will replace your updated.

@jimp thanks. This was indeed the issue. Switched to prefer IPv4 and everything is now working; updates and upgrades take seconds not minutes, and the GUI now displays updated status too.

Just a quick update on this. I finally sent those PCs back and ordered slightly different ones where the vendor claimed they would come with TPM module (however, they didn't ) But the issue doesn't turn up, not with the original BIOS and not with the most recent one. So it might have had a different reason we'll probably never find out. Whatever. Happy it's working now!

@aholmes5 I did that with other versions save your auto backup config serial it changes each reload

@tknospdr FWIW I checked ebay and found Promise SANLink2 E2002t adapters that do Thunderbolt 2 and have two SFP ports for a not so bad price. Might be worth looking at. As far as Apple stuff goes, I first used one in 1982. An Apple ][ plus with 48k of memory and a single floppy drive. My that was primitive.

@SteveITS Thanks Steve! That did the trick!

@Klaus2314 said in (SOLVED) No upgrade for SG-1100?: @bmeeks I've re-installed and restored my config and everything seems to be back to normal with 23.05 running. Thank you again! Glad you got everything up and going on 23.05

@crgbt That thread helped me fix it. Thanks everyone.

@sgw This is the exact thing I'm seeing. Something isn't right with pfSense-upgrade 1.0.66. As soon as I roll back to 1.0.61, everything works right again with package management.

I too have that issue, so I managed to rollback to 2.6.0 as it was a VM via a snapshot. I am now, unable to update any packages, see any packages, checking for 2.6.0 updates says I am on the latest version. When I got to register for pfsense Plus again, it say is already registered, but now when I select the pfSense Plus upgrade option, I get an error: Retrieving: Unable to check for updates: SSH says: /root: pfSense-upgrade -d -c >>> Updating repositories metadata... pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended Updating pfSense-core repository catalogue... Could not load client certificate /etc/ssl/pfSense-repo-custom.cert Could not load client certificate /etc/ssl/pfSense-repo-custom.cert Could not load client certificate /etc/ssl/pfSense-repo-custom.cert Could not load client certificate /etc/ssl/pfSense-repo-custom.cert pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Authentication error repository pfSense-core has no meta file, using default settings Could not load client certificate /etc/ssl/pfSense-repo-custom.cert Could not load client certificate /etc/ssl/pfSense-repo-custom.cert pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: Authentication error Could not load client certificate /etc/ssl/pfSense-repo-custom.cert Could not load client certificate /etc/ssl/pfSense-repo-custom.cert pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.txz: Authentication error Unable to update repository pfSense-core Updating pfSense repository catalogue... Could not load client certificate /etc/ssl/pfSense-repo-custom.cert Could not load client certificate /etc/ssl/pfSense-repo-custom.cert Could not load client certificate /etc/ssl/pfSense-repo-custom.cert Could not load client certificate /etc/ssl/pfSense-repo-custom.cert pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01//meta.txz: Authentication error repository pfSense has no meta file, using default settings Could not load client certificate /etc/ssl/pfSense-repo-custom.cert Could not load client certificate /etc/ssl/pfSense-repo-custom.cert pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01//packagesite.pkg: Authentication error Could not load client certificate /etc/ssl/pfSense-repo-custom.cert Could not load client certificate /etc/ssl/pfSense-repo-custom.cert pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01//packagesite.txz: Authentication error Unable to update repository pfSense Error updating repositories! ERROR: Unable to compare version of pfSense-repo

@jdeloach said in Updates to 2.7.0 CE ??? (Solved): .....or should hold off till I upgrade to 2.7.0 CE I would do so in any case! It makes no sense to install packages for 2.7 on 2.6 because the PHP code was on change and "something" as I would be imagine about or from. I’ve seen that posted before. Is your update branch set to 2.7? I think this will be the problem here.

@Cabledude PHP errors are more or less expected when changing PHP versions during an upgrade. If it’s working with no errors after, I would not worry about it.

@Ignat No, I"m running VMXNET3 and have no problems. The reason mine failed was because of the squid package. I have to not only remove the package, but delete the cache folder manually. Once the folder was removed, upgrade went through successfully. I don't know why. Also: Make sure you KEEP the VMware plug-in installed when doing the upgrade. It should be the only installed package prior to upgrade.

@wavesound said in 23.01 -> 23.05 upgrade = bunch of PHP errors: As a fellow SG-3100 owner I'm convinced that the SG-3100 with ARM doesn't get the same love and attention as its x86 cousins. I am pretty sure that they will do all for their own hardware because it is also their "figurehead". I always see something like this whenever I go to check the forums before upgrading. Would be the best as I see it, I was installing three (3x) times, pfSense 2.6 > 23.01 > 23.05 pfSense 2.7 Devel But now all is running fine and well for me. And if I read (like you) the forum before upgrading I see even again and again that many owners of the Netgate SG hardware will be mostly installing, upgrading and be happy by using a real 23.01 or 23.05 image! That is the other site of the medal, you see only your case and not the other once!

@bcdouglas - what did you mean by "cert refresh"? Is this equivalent of receiving a new activation token for pfSense Plus, or does it refer to something else? Thanks in advance.

@jimp That appears to have worked -- even though it too forever to reboot and come back. Thank You! [image: 1685196788157-535b7622-5093-4c3e-b3ac-7151cfba2482-image.png]

@nightreap3r Cert issues are starting to look like a common theme. I have faced one since trying any build related to 23.05 RC onward.