Unable to check for updates (SOLVED)

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

[Jare 0]

@stephenw10

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 script

WWW: https://www.pfsense.org/

[stephenw10]

Yeah, that's a much later version.

Make sure the update branch is set to 22.01 then run:
pkg upgrade -f pfSense-upgrade

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

[Jare 0]

@stephenw10

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.

[stephenw10]

@jare-0 said in Unable to check for updates (SOLVED):

would doing a clean install of 22.05 and uploading my 22.01 config file clear up this issue?

Yes. An that's also probably quickest if you have local access to the firewall.

[thwong]

@techpro2004 thanks for your fix.
I was running stable 22.05.14 and since then I couldn't update to any version.

With your fix, I can update mine to development version without any issues.

[dedskwirl]

@stephenw10
I'm having a similar issue. Running pkg info pfSense-upgrade gives me the following:

pfSense-upgrade-1.0_27
Name           : pfSense-upgrade
Version        : 1.0_27
Installed on   : Fri Sep 16 19:30:36 2022 EDT
Origin         : sysutils/pfSense-upgrade
Architecture   : FreeBSD:12:armv7
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:04:38+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 script

And running pkg-static update -f gives me the following output:

Updating pfSense-core repository catalogue...
pkg-static: Repository pfSense-core has a wrong packagesite, need to re-create database
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries:
pkg-static: wrong architecture: FreeBSD:12:amd64 instead of FreeBSD:12:armv7
pkg-static: repository pfSense-core contains packages with wrong ABI: FreeBSD:12:amd64
Processing entries... done
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: Repository pfSense has a wrong packagesite, need to re-create database
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries:
pkg-static: wrong architecture: FreeBSD:12:amd64 instead of FreeBSD:12:armv7
pkg-static: repository pfSense contains packages with wrong ABI: FreeBSD:12:amd64
Processing entries... done
Unable to update repository pfSense
Error updating repositories!

I have also tried the fix pinned at the top of this page. I do not have local access to the system. Running an SG-3100.

[stephenw10]

Ah, OK. That manual fix should not be required for any users any longer but also it would never have applied to the 3100 because it's an armv7 device not amd64. Hence the errors you see there. You need to revert that change did you keep a copy of the original file?

It should be:

FreeBSD: { enabled: no }

pfSense-core: {
  url: "pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_armv7-core",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

pfSense: {
  url: "pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_armv7-pfSense_plus_v22_05",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

What error are you seeing trying to update with that file in place?

[dedskwirl]

@stephenw10
That seems to have worked. Thanks!

[SHoover80]

Is it too much to ask for, to just release the installer for the latest version of pfsense plus. Here I am trying to resolve an issue with PFSense Plus 22.5 resulting in me having to do a fresh install. As other recovery methods aren't working, And in normal circumstances with my situation, The easiest method would be to just do a fresh install, and use my backup config to recover and go on with my day. But I cant simply install PFSense Plus, restore my backup. and get back to where I was and what I was working on. Instead I have to install an out outdated version of CE, upgrade that, Then upgrade that to PFSense Plus, 22.1 Then upgrade that again to 22.5. But for whatever reason, CE is having issues unable to check for updates. So, 5 fresh installs failed attempts later, multiple issues during one required update process or the next. An hour+ of my time wasted dealing with update issues trying to get an outdated version of CE to update Just so I can get to the point where I get PFSense Plus to install, so I can update that and Finally get to the current Non BETA version.