Unable to check for updates (SOLVED)
- 
 Yes, that ^. 
- 
 Reboot needed? 
 Because that did not resolve it for me.Still getting "There are no packages currently installed." And if I go to System Update, getting "Unable to check for updates" 
- 
 Check the system log. Do you see the repo package being upgraded and then downgraded again? This could be a completely different problem of course. Try running at the command line: pkg -d update
 See what error it throws.Steve 
- 
 It is now working and is seeing updates and packages correctly for v22.01 Thank you all, for your assistance. 
- 
 G Gertjan referenced this topic on G Gertjan referenced this topic on
- 
 B bmeeks referenced this topic on B bmeeks referenced this topic on
- 
 B bmeeks referenced this topic on B bmeeks referenced this topic on
- 
 B bmeeks referenced this topic on B bmeeks referenced this topic on
- 
 B bmeeks referenced this topic on B bmeeks referenced this topic on
- 
 @matt2 Worked on my Super Micro 1537 one too. Thanks so much! 
- 
S ssppcc referenced this topic on
- 
S ssppcc referenced this topic on
- 
S ssppcc referenced this topic on
- 
S ssppcc referenced this topic on
- 
 @bingo600 said in Unable to check for updates (SOLVED): https://forum.netgate.com/post/1062058 My sincerest apologies to revive a resolved thread. 
 currently experiencing this error.
 switching the upgrade channel to DEVEL and back to upgrade+ did not work for me.command pkg -d update keeps throwing certificate errors. this is a fresh install of pfsense 2.6 
- 
 @gothixkhan 
 The above solution, was due to an update error that Netgate made.
 I doubt they would make the same mistake again.I think there is something else : Than an incomplete update URL, causing your issue. /Bingo 
- 
 Yes, any error you're seeing now is not the same cause. 
 What's the actual error 'pkg -d update' shows?I know there were some backend issues yesterday you could potentially have been hitting. Steve 
- 
 @stephenw10 it alternates between Certificate and authentication issues. it flips on reboot. 
- 
 Can we see the exact error text? 
- 
 @stephenw10 not anymore, apparently. 
 it works now?I'm sorry 
- 
 Cool, good to hear.  
- 
 @stephenw10 just to clarify what I did and why it worked. I had it set to the development branch. 
 I think you guys had a release either yesterday or the day before.
 the updater + upgrade to pf+ only works because it picked up the new release, which is 20221220.1549up until yesterday it was erroring out. 
- 
 I had the same issue and this worked like a charm! 
- 
 @sgc Fixed for me. THankyou! 
- 
 Still having trouble with this. I'm on a 6100 - running 22.01. When running "pkg -d update" I get different errors depending on the selected firmware branch. I get an invalid link error on the release branches and the dev branch gives me much more... few examples below. I can post the entire result if needed. "pkg: Repository pfSense-core has a wrong packagesite, need to re-create database" "DBG(1)[79952]> PkgRepo: need forced update of pfSense-core" "pkg: wrong architecture: FreeBSD:14:amd64 instead of FreeBSD:12:amd64" "pkg: repository pfSense-core contains packages with wrong ABI: FreeBSD:14:amd64" "Processing entries... done" "Unable to update repository pfSense-core" "Error updating repositories!" I've searched around and found some info on forced update of the database but thought I'd check in here first. Thank you. 
- 
 Looks like you may have pulled in a bad pfSense-upgrade at some point. What does pkg info pfSense-upgradeshow?
 You may need to switch the repo back to 22.01 and force reinstall pfSense-upgrade from there.
- 
 pfSense-upgrade-1.0_27 
 Name : pfSense-upgrade
 Version : 1.0_27
 Installed on : Fri Sep 16 19:48:18 2022 EDT
 Origin : sysutils/pfSense-upgrade
 Architecture : FreeBSD:12:amd64
 Prefix : /usr/local
 Categories : sysutils
 Licenses : APACHE20
 Maintainer : coreteam@pfsense.org
 WWW : https://www.pfsense.org/
 Comment : pfSense upgrade script
 Annotations :
 FreeBSD_version: 1203506
 build_timestamp: 2022-09-08T00:05:44+0000
 built_by : poudriere-git-3.3.99.20220831
 port_checkout_unclean: no
 port_git_hash : 83c4d6dbf695
 ports_top_checkout_unclean: yes
 ports_top_git_hash: 8065fbca4d5a
 repo_type : binary
 repository : pfSense
 Flat size : 63.7KiB
 Description :
 pfSense upgrade scriptWWW: https://www.pfsense.org/ 
- 
 Yeah, that's a much later version. Make sure the update branch is set to 22.01 then run: 
 pkg upgrade -f pfSense-upgradeThat should bring you back to the correct pkg for 22.01 and that should then allow you to upgrade to either 22.05 or 23.01b. 
- 
 Just gave that a shot and received the following; pkg: invalid url: /pfSense_plus-v22_01_amd64-core 
 pkg: Cannot parse configuration file!I would obviously like a quick fix to this, but would doing a clean install of 22.05 and uploading my 22.01 config file clear up this issue? I've been toying with the idea of changing to ZFS anyway. I appreciate your time - thank you. 

