<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: opaque: Failed to check WildFire content upgrade info due to generic communication error in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33372#M24453</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Few related discussion on the forum, might help you. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/message/29090"&gt;:&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/message/33643"&gt;generic communication error&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/message/22288"&gt;Re: updates.paloaltonetworks.com connectivity&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 May 2014 19:18:30 GMT</pubDate>
    <dc:creator>HULK</dc:creator>
    <dc:date>2014-05-13T19:18:30Z</dc:date>
    <item>
      <title>opaque: Failed to check WildFire content upgrade info due to generic communication error</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33371#M24452</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any suggestions please?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have it set to update every 15 minutes at an odd number of minutes to hopefully avoid "Let's all download at 00:00".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Doesn't happen all the time but it does happen more than I'd expect given we have a solid/stable leased line connection.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 May 2014 18:28:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33371#M24452</guid>
      <dc:creator>networkadmin</dc:creator>
      <dc:date>2014-05-13T18:28:25Z</dc:date>
    </item>
    <item>
      <title>Re: opaque: Failed to check WildFire content upgrade info due to generic communication error</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33372#M24453</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Few related discussion on the forum, might help you. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/message/29090"&gt;:&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/message/33643"&gt;generic communication error&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/message/22288"&gt;Re: updates.paloaltonetworks.com connectivity&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 May 2014 19:18:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33372#M24453</guid>
      <dc:creator>HULK</dc:creator>
      <dc:date>2014-05-13T19:18:30Z</dc:date>
    </item>
    <item>
      <title>Re: opaque: Failed to check WildFire content upgrade info due to generic communication error</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33373#M24454</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have had same issue for wildfire as well as content update check. We used to get bunch of emails on daily basis. I had a case open with support but dont think any resolution was provided. The alerts stopped for last few months however started again since week. Not sure if there is anything changed Palo Alto side.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 May 2014 05:04:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33373#M24454</guid>
      <dc:creator>Sly_Cooper</dc:creator>
      <dc:date>2014-05-14T05:04:20Z</dc:date>
    </item>
    <item>
      <title>Re: opaque: Failed to check WildFire content upgrade info due to generic communication error</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33374#M24455</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We had a reply from support saying Palo Alto "upgraded" their WildFire servers last week and since then some other people have apparently logged similar issues so they suspect it's something at Palo Alto's end - they are going to check with Palo Alto.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 May 2014 17:15:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33374#M24455</guid>
      <dc:creator>networkadmin</dc:creator>
      <dc:date>2014-05-15T17:15:03Z</dc:date>
    </item>
    <item>
      <title>Re: opaque: Failed to check WildFire content upgrade info due to generic communication error</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33375#M24456</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So support are suggesting change the update server from &lt;STRONG style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3b3b3b;"&gt;updates.paloaltonetworks.com&lt;/STRONG&gt; to &lt;STRONG style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3b3b3b;"&gt;staticupdates.paloaltonetworks.com&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Both point to exactly the same data center though, same route.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2014 19:31:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33375#M24456</guid>
      <dc:creator>networkadmin</dc:creator>
      <dc:date>2014-05-16T19:31:04Z</dc:date>
    </item>
    <item>
      <title>Re: opaque: Failed to check WildFire content upgrade info due to generic communication error</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33376#M24457</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Still&lt;/STRONG&gt;&lt;/EM&gt; seeing this - any ideas at all?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2014 15:57:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33376#M24457</guid>
      <dc:creator>networkadmin</dc:creator>
      <dc:date>2014-06-19T15:57:30Z</dc:date>
    </item>
    <item>
      <title>Re: opaque: Failed to check WildFire content upgrade info due to generic communication error</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33377#M24458</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Talking to myself I guess :smileylaugh:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Support have had a tech support bundle, I don't think they'll find anything as a Palo Alto SE has said that use of WildFire has increased massively and he's heard anecdotes about the back-end needing to be upgraded etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It would be nice if there is an issue if Palo Alto simply acknowledged it as it would save wasting Exclusive's time on something that can't be fixed by anything they or I do.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jun 2014 15:44:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33377#M24458</guid>
      <dc:creator>networkadmin</dc:creator>
      <dc:date>2014-06-20T15:44:54Z</dc:date>
    </item>
    <item>
      <title>Re: opaque: Failed to check WildFire content upgrade info due to generic communication error</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33378#M24459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I suspect that at least part of this is that wildfire does the every 15 minute update on the hour exact for all users and cannot be configured.&amp;nbsp; I had run into issues juggling the various update times on the devices to prevent conflicts.&amp;nbsp; I can only imagine what the traffic looks like on the hub side.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are of course right, that PA just needs to acknowledge some kind of DC issue on their side so we don't crawl the configs and waste time trying to fix what we have no control over.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Jun 2014 12:04:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/opaque-failed-to-check-wildfire-content-upgrade-info-due-to/m-p/33378#M24459</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2014-06-21T12:04:40Z</dc:date>
    </item>
  </channel>
</rss>

