<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[PfSense 2.1 amd64 UNABLE TO CHECK FOR UPDATES]]></title><description><![CDATA[<p dir="auto">Hi Everyone,</p>
<p dir="auto">I searched for awhile and couldn't really find any useful information so I decided to make a new post.</p>
<p dir="auto">The issue I'm having is with a pfSense box we're working on implementing at a Library. We have VLANs set up in an Active Directory environment.</p>
<p dir="auto">I just wanted to get internet access to it so I could install packages and halfway configure it, so I gave the WAN interface a 192.168.x.x/24 IP and UNblocked "private addresses"….I am able to ping the Gateway...ping Google DNS...NSLookup several sites (yahoo.com, google.com, etc).</p>
<p dir="auto">BUT it is unable to check for updates?...</p>
<p dir="auto">Any Ideas on this, I've seen some other posts with update issues but none seem to have answers...</p>
<p dir="auto">Thanks</p>
]]></description><link>https://forum.netgate.com/topic/63165/pfsense-2-1-amd64-unable-to-check-for-updates</link><generator>RSS for Node</generator><lastBuildDate>Tue, 17 Mar 2026 15:51:52 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/63165.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 25 Nov 2013 18:23:16 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to PfSense 2.1 amd64 UNABLE TO CHECK FOR UPDATES on Sun, 16 Nov 2014 15:38:45 GMT]]></title><description><![CDATA[<p dir="auto">YES!!</p>
<p dir="auto">This has been bothering me for months! This fixes it.</p>
<p dir="auto">Thank you.</p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/eduardr">@<bdi>eduardr</bdi></a>:</p>
<blockquote>
<p dir="auto">My particular problem was I had set the DNS forwarder service to bind only to the LAN IP's, and it turns out Localhost needs to be added to the list to bind to as well - otherwise the firewall itself cannot resolve the dns name for the update server.</p>
<p dir="auto">This post had the info that clued me in -<br />
https://forum.pfsense.org/index.php?topic=68164.15</p>
</blockquote>
]]></description><link>https://forum.netgate.com/post/495898</link><guid isPermaLink="true">https://forum.netgate.com/post/495898</guid><dc:creator><![CDATA[wawawawa]]></dc:creator><pubDate>Sun, 16 Nov 2014 15:38:45 GMT</pubDate></item><item><title><![CDATA[Reply to PfSense 2.1 amd64 UNABLE TO CHECK FOR UPDATES on Thu, 28 Aug 2014 22:22:26 GMT]]></title><description><![CDATA[<p dir="auto">My particular problem was I had set the DNS forwarder service to bind only to the LAN IP's, and it turns out Localhost needs to be added to the list to bind to as well - otherwise the firewall itself cannot resolve the dns name for the update server.</p>
<p dir="auto">This post had the info that clued me in -<br />
https://forum.pfsense.org/index.php?topic=68164.15</p>
]]></description><link>https://forum.netgate.com/post/480176</link><guid isPermaLink="true">https://forum.netgate.com/post/480176</guid><dc:creator><![CDATA[eduardr]]></dc:creator><pubDate>Thu, 28 Aug 2014 22:22:26 GMT</pubDate></item><item><title><![CDATA[Reply to PfSense 2.1 amd64 UNABLE TO CHECK FOR UPDATES on Fri, 11 Apr 2014 04:49:56 GMT]]></title><description><![CDATA[<p dir="auto">If others get this, check your default gateway.  I have all my LAN traffic going out through a gateway group, and the default gateway has been offline for six months but the other one is up, so everything has been working, but update checks were failing.</p>
<p dir="auto">Thanks to stephenw10's test, a "no route to host" got me clued in on what to check.</p>
]]></description><link>https://forum.netgate.com/post/454483</link><guid isPermaLink="true">https://forum.netgate.com/post/454483</guid><dc:creator><![CDATA[bill_mcgonigle]]></dc:creator><pubDate>Fri, 11 Apr 2014 04:49:56 GMT</pubDate></item><item><title><![CDATA[Reply to PfSense 2.1 amd64 UNABLE TO CHECK FOR UPDATES on Tue, 26 Nov 2013 17:44:18 GMT]]></title><description><![CDATA[<p dir="auto">Hi Stephenw10,</p>
<p dir="auto">Thank you for the reply.</p>
<p dir="auto">Well…I shutdown the pfSense box yesterday afternoon, without making any further changes. I just turned it back on and it booted up and WAN interface is working properly now.</p>
<p dir="auto">Sorry for the troubles, I have just never had any problems before with interfaces not refreshing properly while turned on, so I didn't even think to reboot...</p>
<p dir="auto">However, I did go ahead check the version file anyway...</p>
<pre><code>$ fetch -o /dev/null http://updates.pfsense.org/_updaters/version
/dev/null                                               12  B  146 kBps
</code></pre>
<p dir="auto">Thanks again for the reply and information</p>
]]></description><link>https://forum.netgate.com/post/431573</link><guid isPermaLink="true">https://forum.netgate.com/post/431573</guid><dc:creator><![CDATA[MasterfulMethods]]></dc:creator><pubDate>Tue, 26 Nov 2013 17:44:18 GMT</pubDate></item><item><title><![CDATA[Reply to PfSense 2.1 amd64 UNABLE TO CHECK FOR UPDATES on Mon, 25 Nov 2013 20:07:50 GMT]]></title><description><![CDATA[<p dir="auto">Can you fetch the versions file from the command line?</p>
<pre><code>[2.1-RELEASE][root@pfsense.localdomain]/root(2): fetch -o /dev/null http://updates.pfsense.org/_updaters/version
version                                       100% of   12  B   71 kBps

</code></pre>
<p dir="auto">Do you have the update URL set correctly? Go to System: Firmware: Updater Settings: and select the appropriate url from the drop down.</p>
<p dir="auto">You might also try this:<br />
https://doc.pfsense.org/index.php/Controlling_IPv6_or_IPv4_Preference</p>
<p dir="auto">Steve</p>
]]></description><link>https://forum.netgate.com/post/431446</link><guid isPermaLink="true">https://forum.netgate.com/post/431446</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Mon, 25 Nov 2013 20:07:50 GMT</pubDate></item></channel></rss>