Unable to check for updates (SOLVED)
-
It is not working for me.
I am running v22.01 on a SG-5100
Should I really have "pfSense_plus-v22_05_amd64-core" in that file?Perhaps a reboot has to happen, to make this effective?
-
That sounds right you have an Intel CPU
Does your file look like this ?
Else there was a guide how to Edit the file manually here.
https://forum.netgate.com/post/1062052But you could try a reboot first
-
Can you clarify:
I am running v22.01
Should the pfSense.conf file have pfSense_plus-v22_05_amd-core ?And do I need to reboot after fixing this?
-
OOpzz - I missed that you are running 22.01 , thought you were on 22.05
According to Netgate , if you have switched to the Development "train" , and then back to "normal" , your file should contain the correct lines.
@stephenw10
Any wise words here ? -
Yeah, switch to dev(22.11) and then back to prev(22.01). The should restore the correct repos pkg.
You shouldn't need to edit anything manually. But if you do then, yes, it should be 22_01 since that's what you're running.
Steve
-
Did you mean switch the Firmware Branch to "Latest development snapshots (Experimental 22.09 DEVEL)" then Save
Then
switch the Firmware Branch to "Previous stable version (22.01)" then Save
? -
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.
-
-
-
-
-
-
@matt2 Worked on my Super Micro 1537 one too. Thanks so much!
-
-
-
-
-
@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!