PfSense unable to check for updates?

dataking

Hi all.

First post! lol

I am a newcomer to pfSense, but I like what I'm seeing so far.

On the dashboard, my pfSense says (in the version block) that it is "Unable to check for updates". Is this normal? Why wouldn't it be able to check for updates?

Metu69salemi

two reasons:
1. you have no internet access yet
2. pfsense can't use dns servers you applied to it

A Former User

i have the same issue

Downloading new version information…done
Unable to check for updates.
Could not contact pfSense update server http://updates.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_RELENG_2_0/.updaters/

i was using the openDNS servers but i switch the first one to google and i still see the above message.

dataking

@Metu69salemi:

two reasons:
1. you have no internet access yet
2. pfsense can't use dns servers you applied to it

I definitely have internet access.

Ping from my pfSense can resolve www.google.com, but updates.pfsense.org or forums.pfsense.org doesn't respond. The names DO resolve to IPs however, so DNS is working.

A Former User

i also have internet access, the network i am on now sits behind a pfsense box.

ptt

Do you have set properly the "Update URL" at "System:Firmware:Settings" ?

Autoupdate_URL.PNG_thumb

A Former User

@ptt:

Do you have set properly the "Update URL" at "System:Firmware:Settings" ?

i dont, because it says other than pfsense.org, isnt that where the update should be coming from?

EDIT- i didnt see the drop down option…checking that now.

EDIT2- ok, i selected the correct drop down option, which checks the box and auto populates the url field...i saved and went to the 'auto update' tab...

Downloading new version information…done
Obtaining current version information...done

You are on the latest version.

thanks.

hopefully the OP has the same issue as i did.

A Former User

@Metu69salemi:

two reasons:
1. you have no internet access yet
2. pfsense can't use dns servers you applied to it

or

3. you dont have it setup properly. :)

Metu69salemi

@tomdlgns:

3. you dont have it setup properly. :)

That might also be the case, but that's rare isn't it ???

dataking

@tomdlgns:

hopefully the OP has the same issue as i did.

I did. Thanks.