Updates.pfsense.org is unreachable

[jsimon1231]

Running new install of pfSense 2.0.1.  "System: Firmware: Auto Update" shows the following:
–-------------------------------------------------------------------------------------------------------
Downloading new version information...done
Unable to check for updates.
Could not contact pfSense update server http://updates.pfsense.org/FreeBSD_RELENG_8_1/amd64/pfSense_RELENG_2_0/.updaters/

When I ping updates.pfsense.org from the console, I receive the following:

PING updates.pfsense.org (91.227.27.66): 56 data bytes
36 bytes from 91.227.27.61: Destination Host Unreachable
Vr HL TOS  Len    ID Flg    off TTL  Pro  cks          Src          Dst
4  5  00 5400 25da  0 0000  34  01 2796 192.168.1.108  91.227.27.66

So I AM getting name resolution.  Just for fun, I tried a trace route from a Win7 computer connected to the LAN interface, and received the following:

C:\Users\John>tracert 91.227.27.66

Tracing route to updates.pfsense.org [91.227.27.66]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms  pfSense.localdomain [192.168.10.1]
  2    <1 ms    <1 ms    <1 ms  my.router [192.168.1.1]
  3    *        *        *    Request timed out.
  4    7 ms    7 ms    7 ms  acr02sghlga-tge-7-1.sghl.ga.charter.com [96.34.72.8]
  5    7 ms    7 ms    7 ms  crr02sghlga-tge-0-4-0-0.sghl.ga.charter.com [96.34.78.16]
  6    11 ms    11 ms    12 ms  bbr02atlnga-bue-3.atln.ga.charter.com [96.34.2.72]
  7    10 ms    16 ms    10 ms  66.216.1.177
  8    30 ms    29 ms    29 ms  ash-ten3-1-atl-ten3-1.bboi.net [66.216.1.158]
  9    29 ms    30 ms    28 ms  ny111-te2-2-chi-te3-3.bbo.net [66.216.1.49]
10  114 ms  130 ms  112 ms  ams-vl2-ny60-vl2.bboi.net [66.216.48.218]
11  130 ms  131 ms  119 ms  nl-rt-dc2-ice-ir01.kpn.net [195.69.144.89]
12    *        *        *    Request timed out.
13    *        *        *    Request timed out.
14  117 ms  117 ms  117 ms  91.227.27.61
15  91.227.27.61  reports: Destination host unreachable.

Trace complete.

–---------------------------------
Any help would be appreciated!

[nexusN]

System –> Firmware -->Updater Setting,
Set Default Auto Update URLs to pfsense [Your-Arch] stable updates,
save and check if it's fixed. ;)

[Pennyless]

I may be wrong, but if my memory serves me right….
when 2.0 RC changed to 2.0 Release the updaters didn't disappear.
And when 2.0.1 RC changed to 2.0.1 Release the updaters didn't disappear.
But when 2.0.2 RC change to 2.0.2 Release the updaters vanished without any indication.
Based on the detail of Jsimon1231's question, I'm guessing he knew how to fix his problem.

Literally for years we were told to stay updated using the updater.
The often proffered solution to a bug was to "update".
The first question asked when a problem occurred was "what version" or "have you updated".
All of the PFSense group are real savvy guys.
I'm sure you understand why people are scratching their heads.

When longstanding procedures or policies change, wouldn't a "heads up" in a sticky be helpful?

[podilarius]

Pennyless, they didn't disappear. I can check updates even on my 2.0.2 install. He has a fundamental problem.

Version 2.0.2-RELEASE (i386)
built on Mon Aug 20 06:05:56 EDT 2012
FreeBSD 8.1-RELEASE-p6

You are on the latest version.

*** DISCLAMER ***
I built my own and 2.0.2 is not yet released. I am only posting this to prove that it still works.
*** DISCLAMER ***

Sometimes if you upgrade, the setting remains the same and you only need to change and re-save it to have it working. In this case, it should be http://updates.pfsense.org/_updaters/amd64 and not the URL that was posted. If you switch it and re-save it, it should work at least for those who don't have connection problems. Also, these servers are behind firewalls that do not allow ping or traceroute. Best thing to use is a port scanner to see if port 80 is open.

Far as I can tell no procedure has changed. Especially since 2.0.2 has not even dropped. How can something disappear that was never there? I am not talking snapshots, this is in reference to release versions only, since that is what we are dealing with here. Snapshots are on a different URL and usually once releases are done, the snapshots for the version released are no longer available. This has always happens to the best of my recollection. Course, my memory is not what it used to be.

[jsimon1231]

podilarius, you hit the nail on the head.

I when to "Updater Settings" and set "Default Auto Update URLs" to "pfsense amd64 stable updates", clicked the "Save" button (which set the "Base URL" to "http://updates.pfsense.org/_updaters/amd64"), and everything is GOLDEN!

Thanks again!