Upgrade / repo issue
-
Trying to upgrade and the GUI is showing"
"pfSense-repoc: failed to fetch the repo data"
If I try via the CLI, any pfSense-upgrade or pfSense-repoc command results in the same error:
pfSense-repoc: failed to fetch the repo data
failed to read the repo data.pfSense-repoc-static: failed to fetch the repo data
failed to read the repo data.
failed to update the repository settings!!!
failed to update the repository settings!!!Is there something globally broken? There does not appear to be any real debugging available for these commands. "-d" does not seem to do anything.
-
I was able to revert back to 23.09.1 and the in the update GUI, Messages says "Your Netgate device has pfSense+ as part of your device purchase." now.
However, Retrieving says "Unable to check for updates"
Does anyone have any ideas?
-
What were you running before you reverted? What were you trying to upgrade from?
What hardware is that?
-
-
Hmm, well that should always have access. Not some backend issue there. More likely a connectivity issue.
You can run:
pfSense-repoc -NDto see more from 25.11. -
@stephenw10 said in Upgrade / repo issue:
pfSense-repoc -ND
I have the same issue with version 25.07.1
OS: FreeBSD
OS Version: 15.0-CURRENT
Platform: amd64
Product: Netgate pfSense Plus
Version: 25.07.1-RELEASE
FS type: zfs
Language: en_US
Model: Super Micro 1537
NDI: f3cc9916802085fa2af9
Package prefix: pfSense-pkg-
Serial: VM185S028733
Repo path: /usr/local/etc/pfSense
Request query: {"platform":"Super Micro 1537","os":"FreeBSD","osver":"15.0-CURRENT","prod":"Netgate pfSense Plus","ver":"25.07.1-RELEASE","ed":"Plus","fstype":"zfs","pkgs":"[{"name":"Nexus","ver":"25.07.1_1"},{"name":"suricata","ver":"7.0.8_2"},{"name":"WireGuard","ver":"0.2.9_5"},{"name":"aws-wizard","ver":"0.12"},{"name":"pfBlockerNG","ver":"3.2.7"},{"name":"zabbix-agent7","ver":"1.0.9_1"},{"name":"zabbix-proxy7","ver":"1.0.9_1"},{"name":"ipsec-profile-wizard","ver":"1.2.4"},{"name":"Netgate_Firmware_Upgrade","ver":"23.05.01"}]"}
POST data: uid=f3cc9916802085fa2af9&language=en_US&serial=VM185S028733&version=%7B%22platform%22%3A%22Super+Micro+1537%22%2C%22os%22%3A%22FreeBSD%22%2C%22osver%22%3A%2215.0-CURRENT%22%2C%22prod%22%3A%22Netgate+pfSense+Plus%22%2C%22ver%22%3A%2225.07.1-RELEASE%22%2C%22ed%22%3A%22Plus%22%2C%22fstype%22%3A%22zfs%22%2C%22pkgs%22%3A%22%5B%7B%5C%22name%5C%22%3A%5C%22Nexus%5C%22%2C%5C%22ver%5C%22%3A%5C%2225.07.1_1%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22suricata%5C%22%2C%5C%22ver%5C%22%3A%5C%227.0.8_2%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22WireGuard%5C%22%2C%5C%22ver%5C%22%3A%5C%220.2.9_5%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22aws-wizard%5C%22%2C%5C%22ver%5C%22%3A%5C%220.12%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22pfBlockerNG%5C%22%2C%5C%22ver%5C%22%3A%5C%223.2.7%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22zabbix-agent7%5C%22%2C%5C%22ver%5C%22%3A%5C%221.0.9_1%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22zabbix-proxy7%5C%22%2C%5C%22ver%5C%22%3A%5C%221.0.9_1%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22ipsec-profile-wizard%5C%22%2C%5C%22ver%5C%22%3A%5C%221.2.4%5C%22%7D%2C%7B%5C%22name%5C%22%3A%5C%22Netgate_Firmware_Upgrade%5C%22%2C%5C%22ver%5C%22%3A%5C%2223.05.01%5C%22%7D%5D%22%7D&arch=amd64
pfSense-repoc: failed to fetch the repo data
failed to read the repo data. -
Same problem here now.
Yesterday i updated several Devices from 25.11.1 to 26.03.1, with Patches from System Patches 2.3.4, without any Problems.Today i have additional Devices to Upgrade/Update - now got this messages:
-On Devices with 25.11.1:
pfSense-repoc: failed to fetch the repo data
-On Devices with 26.03.1:
pfSense-repoc: failed to fetch the repo data pfSense-repoc: failed to read the repo data.EDIT:
The issues were resolved about an hour ago, and I was able to successfully update the affected devices. -
Yup there appears to have been a backend issue overnight that is now resolved.
@tma84 Are you still seeing the error?
-
I can't upgrade to 25.11 from 23.09 as it is saying:
"Unable to check for updates"
"pfSense-repoc -ND" is not a valid command on 23.09 apparently:
: pfSense-repoc -ND
pfSense-repoc: illegal option -- N
pfSense-repoc: dynamic repositories client -
Yes -N is more recent than that. Try just
pfSense-repoc -D -
@stephenw10 said in Upgrade / repo issue:
pfSense-repoc -D
: pfSense-repoc -D
OS: FreeBSD
OS Version: 14.0-CURRENT
Platform: amd64
Product: Netgate pfSense Plus
Version: 23.09.1-RELEASE
FS type: zfs
Language: en_US
Model: Netgate 6100
NDI: 42012414eb43c8fd43e1
Package prefix: pfSense-pkg-
Serial: 2033220393
Repo path: /usr/local/etc/pfSense
Request query: {"platform":"Netgate 6100","os":"FreeBSD","osver":"14.0-CURRENT","prod":"Netgate pfSense Plus","ver":"23.09.1-RELEASE","ed":"Plus","fstype":"zfs","pkgs":"[]"}
POST data: uid=42012414eb43c8fd43e1&language=en_US&serial=2033220393&version=%7B%22platform%22%3A%22Netgate+6100%22%2C%22os%22%3A%22FreeBSD%22%2C%22osver%22%3A%2214.0-CURRENT%22%2C%22prod%22%3A%22Netgate+pfSense+Plus%22%2C%22ver%22%3A%2223.09.1-RELEASE%22%2C%22ed%22%3A%22Plus%22%2C%22fstype%22%3A%22zfs%22%2C%22pkgs%22%3A%22%5B%5D%22%7D&arch=amd64
Messages:
Your Netgate device has pfSense+ as part of your device purchase. -
Looks good. Does it not show an upgrade available.
-
-
I would post the output of "pfSense-upgrade" but the system keeps saying that my post content is spam.
-
@zesta said in Upgrade / repo issue:
but the system keeps saying that my post content is spam.
Time for plan B : post the content here https://pastebin.com/ and post in the forum a link to your post @https://pastebin.com/
The free version will even delete your uploaded stuff so it doesn't linger around forever on the Internet. -
It was apparently the arrows in the output that were messing it up...
: pfSense-upgrade -n
Messages:
Your Netgate device has pfSense+ as part of your device purchase.
Updating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries: . done
pfSense-core repository update completed. 5 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
pfSense repository update completed. 739 packages processed.
All repositories are up to date.
ERROR: It was not possible to identify which pfSense meta package is installed
Your packages are up to date -
Try
pkg-static -d updateandpfSense-upgrade -dfor more debug output. -
@stephenw10 said in Upgrade / repo issue:
"pkg-static -d update" appears to complete properly (output is very long)
"pfSense-upgrade -d" gives this:
Messages:
Your Netgate device has pfSense+ as part of your device purchase.
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries: . done
pfSense-core repository update completed. 5 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: ........ done
Processing entries: .......... done
pfSense repository update completed. 739 packages processed.
All repositories are up to date.
ERROR: It was not possible to identify which pfSense meta package is installed
Your packages are up to date -
Weirdly enough...
I was able to revert to a 25.07 boot environment after several attempts. It let me upgrade from there to 26.03.1 but did not detect 26.07 as available.
I am now seeing the upgrade to 26.07 as available from 26.03.1.
I am assuming some of the issues were due to repo backend issues that others reported, but I still don't understand some of the errors I was seeing. Is it possible for an improperly responding repo to permanently brick an install?
-
@zesta said in Upgrade / repo issue:
Is it possible for an improperly responding repo to permanently brick an install?
No. I mean I could imagine some scenario that might do it but it would requite more than just not responding. And a client can always be recovered.
Privacy Policy · Cookie Policy