Unable to check for updates (SOLVED)

bingo600

@bob-dig said in Unable to check for updates:

@bingo600 said in Unable to check for updates:

@bob-dig
How did you do that "image backup" ?

I use a vm for pfSense.

Ahh

Innz

Awesome! Worked on my 6100 without any issues

KB8DOA

This is creepy - I am getting this but never initiated any sort of update.
I only noticed as I about weekly go and peek at "Package Manager"
to see if I need to do any Package Updates (or install something new).

On this pfSense+ on an SG-5100
v22.01
I was holding off on upgrades, as I wanted to be sure that my OpenVPNs were not going to be "broken" because of changes recently done on recent releases.

I am willing to accept that this final resolution might actually upgrade me to v22.05

I need advice on whether I should try to fix it using the advice already previously mentioned here on this Forum Topic

which might be meant for those that have intentionally upgraded to v22.05 ?

bingo600

@kb8doa
This way of fixing it, came from our resident Netgate guru.
https://forum.netgate.com/post/1062058

/Bingo

KB8DOA

@bingo600

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?

bingo600

@kb8doa

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/1062052

But you could try a reboot first

KB8DOA

@bingo600

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?

bingo600

@kb8doa

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?