pfSense Repository down?
-
Hello, Today both my pfsense virtual machines cannot find any available packages listed in the package manager. It just doesn't load a list. The error in the system logs is:
/pkg_mgr.php: The command '/usr/local/sbin/pfSense-repo-setup' returned exit code '1', the output was 'pfSense-repoc-static: failed to fetch the repo data failed to read the repo data. failed to update the repository settings!!!'
When I ssh into the vm I get the following:
pfSense-repoc-static pfSense-repoc-static: failed to fetch the repo data failed to read the repo data.
And also:
pkg-static -o ABI=FreeBSD:14:amd64 -o IGNORE_OSVERSION=yes update pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended Updating pfSense-core repository catalogue... pkg-static: No SRV record found for the repo 'pfSense-core' pkg-static: An error occured while fetching package pkg-static: packagesite URL error for pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.txz -- pkg+:// implies SRV mirror type repository pfSense-core has no meta file, using default settings pkg-static: packagesite URL error for pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.pkg -- pkg+:// implies SRV mirror type pkg-static: packagesite URL error for pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.txz -- pkg+:// implies SRV mirror type Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: No SRV record found for the repo 'pfSense' pkg-static: An error occured while fetching package pkg-static: packagesite URL error for pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.txz -- pkg+:// implies SRV mirror type repository pfSense has no meta file, using default settings pkg-static: packagesite URL error for pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg -- pkg+:// implies SRV mirror type pkg-static: packagesite URL error for pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.txz -- pkg+:// implies SRV mirror type Unable to update repository pfSense Error updating repositories!
When i manually go to https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.txz in the browser i get an error: DNS_PROBE_FINISHED_NXDOMAIN
Any help? Is the URL down for anyone else?
Thanks for your help!
-
@trsy Experiencing the same issue. The URL is down. Seems like a big blocker for many.
-
The good old "option" 13 doesn't work ? :
IDRAC (opt1) -> igc2 -> v4: 192.168.100.1/24 PORTAL (opt2) -> igc1 -> v4: 192.168.2.1/24 VPNS (opt3) -> ovpns1 -> v4: 192.168.3.1/24 0) Logout (SSH only) 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart GUI 3) Reset admin account and password 12) PHP shell + Netgate pfSense Plus tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Disable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) Shell Enter an option: 13 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
It worked for me.
I'm pretty sure we're all using the same 'update/upgrade' server.
So, it's up, from what I can see.Try also the
pkg-static -d update
or, forcing it to use IPv4 only :
pkg-static -d -4 update
Or, why not, let's be modern :
pkg-static -d -6 update
-
I have two pfSense plus virtual appliances deployed in Azure in HA mode and they both had the same issue described above. I redeployed them both with a clean install and checked if I could update/install packages and it worked just fine.
Its a bit odd that both had the same issue but a clean install fixed the issue on both. Not really a solution to redeploy but it was okay because they are not used in production.
-
@trsy said in pfSense Repository down?:
DNS_PROBE_FINISHED_NXDOMAIN
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#packages-netgate-com-has-no-a-aaaa-record
-
@SteveITS said in pfSense Repository down?:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#packages-netgate-com-has-no-a-aaaa-record
Correct, no A or AAAA record.
This time SRV records ("server records ?") are looked for.This is probably is, I'm just thinking out loud : everything is fine, but DNS isn't. pfSense can't call out for self. Seen that before, and I never understood how people to so. Default 'Netgate' DNS settings work, as I've shown above.