@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.

@quale I was doing it and I would do it even again .

/* XXX: FIX ME! IPV6 */ somebody missed that one ...would have been easier to type the "i" ;)

@Dobby_ all is fine here too. Just the displeasure of having to go through all this instead of a smooth upgrade.

Yeap same issue here. Too scared to try again. Don't want to brick it.

@Dobby_ Ok. I was able to install it on the network. Breath of fresh air. Yet do I have to set it up from scratch or I can restore from a backup? Even if it’s completely different machine with different interfaces etc?

Believe the Hyper- V boot issue was fixed in 23.05. Problem is we can't get from 2.6 to 23.05 direct yet. https://redmine.pfsense.org/issues/13895

@nedyah700 I'm SO glad I didn't fubar my install. I'm far from an expert and it would have probably taken my tiny company offline for a day.