Unable to check for updates
-
Hello,
I'm running Release 2.0, i386 version of PfSense. I have noticed in the last couple days, the system is "unable to check for updates" under version in the web dashboard. The system seems to be working fine. Is this an issue on my end or the PfSense update server?
Thanks
-
I believe your issue is related to one I had yesterday.
http://forum.pfsense.org/index.php/topic,41922.0.htmlIn the end I had to go to System -> Firmware -> Updater Settings
I cleared all the fields -> chose pfSense Stable Release Updates (i386) in the Default Auto Update URLs
and hit Save.I had the same problem you did.
My updater was set to http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_RELENG_2_0/.updaters/The entire snapshots.pfsense.org domain looks to be offline - except for "back soon" page at / .
-
FYI: The latest Updates Base URL is http://updates.pfsense.org/_updaters
-
Hi,
The URL is 'http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/.updaters/', but not responding.
If you go to 'http://snapshots.pfsense.org/' => Snapshots will return soon.
Wait for the end of maintenance
-
So, I assume the best thing to do is wait for thier maintenance to complete, instead of changing my system, YES?
Ok, I changed the updater to the "Release" directory http://updates.pfsense.org/_updaters and this solved the issue. The dashboard now states "You are on the latest version." Thanks for the help!
Regards
Highroller
-
No, you should be looking at the updates.pfsense.org server unless you want to start tracking 2.0.x snapshots when they start back up.
The snapshots server is not an "official" update server, we just put the updates there for convenience since so many people were already pointed there.
-
None of these URLs are working for me right now. http://updates.pfsense.org/_updaters returns a 404. My system can't check for updates.
-
That URL will show 404 in a browser because it has no index.html (or similar) and directory listings are denied. It is not meant to be viewed in a browser, the 404 has nothing to do with whether or not your system can check for updates.
That always boils down to either broken routing/WAN configuration, or broken DNS.
Start a new thread rather than hijacking an old one.
