Unable to check for updates (SOLVED)

bingo600

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 ?

stephenw10

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

KB8DOA

@bingo600

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
?

stephenw10

Yes, that ^.

KB8DOA

@stephenw10

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"

stephenw10

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

KB8DOA

@stephenw10 @bingo600

It is now working and is seeing updates and packages correctly for v22.01

Thank you all, for your assistance.

TheQuank

@matt2 Worked on my Super Micro 1537 one too. Thanks so much!

gothixkhan

@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

bingo600

@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

stephenw10

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

gothixkhan

@stephenw10 it alternates between Certificate and authentication issues.

it flips on reboot.

stephenw10

Can we see the exact error text?

gothixkhan

@stephenw10 not anymore, apparently.
it works now?

I'm sorry

stephenw10

Cool, good to hear.

gothixkhan

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

up until yesterday it was erroring out.

briddle

@matt2

I had the same issue and this worked like a charm!

wifi-will

@sgc Fixed for me. THankyou!

Jare 0

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.

stephenw10

Looks like you may have pulled in a bad pfSense-upgrade at some point. What does pkg info pfSense-upgrade show?
You may need to switch the repo back to 22.01 and force reinstall pfSense-upgrade from there.