Unable to download any packages
-
Which version of pfSense are you running?
-
2.15-RELEASE, last updated in August.
-
I forgot to ask if you're running a nano version on hardware or the standard version on a PC or virtual machine.
-
Standard in a VM, ESXi 5.10.
-
The curl error may apply since curl transfers data. If pfSense uses curl to download updates and it's barfing, that would explain your lack of updates. A quick search shows someone else had this same problem without solution, unfortunately.
-
If it was a curl error shouldn't I get system log messages?
-
Well, you would think so. Ever since FreeBSD deprecated the 8.3 stuff and moved it to a different FTP server, it caused problems for some packages. 2.2 will be out soon. Perhaps an upgrade may fix your issue.
-
Re-upgrading to 2.1.5 should fix, you most likely were using pkg_add to install something that overwrote and broke php-curl.
@KOM:
Ever since FreeBSD deprecated the 8.3 stuff and moved it to a different FTP server, it caused problems for some packages.
All the stock built-in packages are pulled only from us and have no such issues. If you're getting in and mucking with pkg_add, yes that's the case.
-
Still have this issue; any suggestions that would be less of a PITA than a complete reinstall?
-
You don't need to reinstall, just re-apply the update file for the same version you're already on and it'll fix.
-
That sounds good, would you mind pointing me to the instructions on how to do that please?
-
Ok, I just tried that. It didn't work. What's next?
-
Ok, I just tried that. It didn't work. What's next?
Is this happening for all packages? or just one in particular?
-
All packages; also note the error message I mentioned that appears on the dashboard where pfsense's update status would normally be.
-
Can you ping packages.pfsense.org ? Is IPv6 disabled?
-
Yes, and no. Although when I tried disabling it, there was no change.
-
[bump] last call for help before I just nuke and pave.
Update 28/02 for anyone who encounters a similar problem:
Backed up configuration, nuked, paved, restored config. Issue was resolved. My guess is that an update failed in the middle of writing files or something similar and borked some download functions.
