No trusted public keys found
-
@gertjan Indeed: Current date/time
Fri Sep 16 10:36:35 EDT 2022I have tried switching different update branches from the UI, same results.
-
What branch do you have selected?
Looks like you might be trying to hit the dev branch which would be 22.09/22.11 at this point. Make sure you're set to latest stable to see 22.05.
Steve
-
@stephenw10 I get the same results from all branches; here's the output from 2.6.0
pkg-static -d update
DBG(1)[9368]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[9368]> PkgRepo: verifying update for pfSense-core
DBG(1)[9368]> PkgRepo: need forced update of pfSense-core
DBG(1)[9368]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[9368]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_6_0_amd64-core/meta.conf
DBG(1)[9368]> opening libfetch fetcher
DBG(1)[9368]> Fetch > libfetch: connecting
DBG(1)[9368]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-core/meta.conf with opts "i"
DBG(1)[9368]> Fetch: fetcher chosen: https
Fetching meta.conf: 100% 163 B 0.2kB/s 00:01
DBG(1)[9368]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_6_0_amd64-core/packagesite.pkg
DBG(1)[9368]> opening libfetch fetcher
DBG(1)[9368]> Fetch > libfetch: connecting
DBG(1)[9368]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-core/packagesite.pkg with opts "i"
DBG(1)[9368]> Fetch: fetcher chosen: https
Fetching packagesite.pkg: 100% 2 KiB 1.7kB/s 00:01
DBG(1)[9368]> PkgRepo: extracting packagesite.yaml of repo pfSense-core
DBG(1)[9600]> PkgRepo: extracting signature of repo in a sandbox
pkg-static: No trusted public keys found
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
DBG(1)[9368]> PkgRepo: verifying update for pfSense
DBG(1)[9368]> PkgRepo: need forced update of pfSense
DBG(1)[9368]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[9368]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.conf
DBG(1)[9368]> opening libfetch fetcher
DBG(1)[9368]> Fetch > libfetch: connecting
DBG(1)[9368]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.conf with opts "i"
DBG(1)[9368]> Fetch: fetcher chosen: https
Fetching meta.conf: 100% 163 B 0.2kB/s 00:01
DBG(1)[9368]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg
DBG(1)[9368]> opening libfetch fetcher
DBG(1)[9368]> Fetch > libfetch: connecting
DBG(1)[9368]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg with opts "i"
DBG(1)[9368]> Fetch: fetcher chosen: https
Fetching packagesite.pkg: 100% 149 KiB 153.0kB/s 00:01
DBG(1)[9368]> PkgRepo: extracting packagesite.yaml of repo pfSense
DBG(1)[9650]> PkgRepo: extracting signature of repo in a sandbox
pkg-static: No trusted public keys found
Unable to update repository pfSense
Error updating repositories! -
Hmm, you were running 22.01 and trying to upgrade to 22.05 I assume?
You shouldn't be seeing 2.6 as an available branch at all.
What i the history on that install?
-
@stephenw10 I went from the 2.7.0 (last nightly from 8/30 IIRC) to Pfsense+
-
Ah, OK. Yes, that's not (yet) a supported upgrade path. Curently you can only upgrade between 2.6 and 22.01. You can then update to 22.05.
Are you able to re-install clean? That's probably going to be the quickest way back.
Otherwise try running
freebsd-version -kru
anduname -a
to see what you have ended up with. -
@stephenw10 said in No trusted public keys found:
Wipe and reload is going to be a pita, but one that I forced on myself, this sucker is remote.
Here's the output(s):
uname -a
freebsd-version -kru
12.3-STABLE
12.3-STABLE
12.3-STABLEuname -a
FreeBSD a.localdomain 12.3-STABLE FreeBSD 12.3-STABLE plus-RELENG_22_01-n202637-97cc5c23e13 pfSense amd64 -
Ok, the latest stable repo branch is showing 22.01 or 2.6?
It needs to be 22.01. If it is then I would first try this:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors -
@stephenw10 pulling the keys from git looks like it resolved the key issue. I'm somewhere between the CE>+ migration, but at least the FW is running. I'll leave it like this for the time being. Thank you for the assistance.
-
Ah, good call!