Unable to get available and installed packages through web UI (pfSense+ 22.05 AMD64)

sniff122

Just noticed on my dashboard that i'm getting an unable to check for updates message and when going to the package manager page, it states that there are no packages installed and available packages is unable to retrieve package info. Trying to do a pkg update over SSH results in the following message:

pkg: invalid url: /pfSense_plus-v22_05_amd64-core
pkg: Cannot parse configuration file!

I've had a look in /usr/local/etc/pkg/repos/pfSense.conf and this is what is in the file:

FreeBSD: { enabled: no }

pfSense-core: {
  url: "/pfSense_plus-v22_05_amd64-core",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

pfSense: {
  url: "/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

I haven't touched this the configuration for a while and this is just something that has just happened out of nowhere, if someone knows what the package config file is supposed to be for pfSense+ 22.05 (amd64), if they could provide it that would be amazing, really not sure what has caused this to happen though

bmeeks

There was a hiccup maybe three weeks or so back where the repo URL got corrupted. Your box may have pulled in that corrupted one when checking in the past.

This usually fixes the problem:

Go to SYTEM > UPDATE and then click the Update Settings tab.
Change the Branch drop-down to an alternate value, save it, then swap it back to 22.05 and save it again.

The steps above should result in your box pulling down a corrected copy of the repo file.

Details can be found in this post from a long September thread about this issue: https://forum.netgate.com/topic/174768/unable-to-check-for-updates-solved/33.

sniff122

@bmeeks thanks for the info! it doesnt look like that resolved the issue, tried going to the devel branch, which worked but switching back to current release and even previous release has this issue

sniff122

and then its just suddenly worked, typical technology. Thanks for the info!