Thread Info
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 45 replies
  • Subscribers 13 subscribers
  • Views 7367 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

bad pattern updates......AGAIN????

PatrickLee

Current pattern updates v208978. Blocking App Store courier.push.apple.com/


sub="http" name="web request blocked" action="block" method="CONNECT" srcip="192.168.50.20" dstip="" user="" group="" ad_domain="" statuscode="502" cached="0" profile="REF_HttProContaInterNetwo3 (Internal filter profile)" filteraction="REF_DefaultHTTPCFFAction (Content filter (Internal Network))" size="0" request="0x8c7e3100" url="">courier.push.apple.com/" referer="" error="Host not found" authtime="0" dnstime="236" aptptime="127" cattime="30401" avscantime="0" fullreqtime="46490" device="0" auth="0" ua="" exceptions="av,sandbox,fileextension" category="105" reputation="trusted" categoryname="Business"

Can anyone confirm we have a bad pattern updates v206808?  Can't connect to App Store blocking url https://courier.push.apple.com

action="block" method="CONNECT" srcip="192.168.50.20" dstip="" user="" group="" ad_domain="" statuscode="502" cached="0" profile="REF_HttProContaInterNetwo3 (Internal filter profile)" filteraction="REF_DefaultHTTPCFFAction (Content filter (Internal Network))" size="0" request="0x9db16e00" url="https://courier.push.apple.com/" referer="" error="Host not found" authtime="0" dnstime="19295" aptptime="125" cattime="156" avscantime="0" fullreqtime="20543" device="0" auth="0" ua="" exceptions="av,sandbox,fileextension" category="105" reputation="trusted" categoryname="Business"
2022:02:26-18:52:38 httpproxy[14863]: id="0002" severity="info" sys="SecureWeb" sub="http" name="web request blocked"

Thanks



This thread was automatically locked due to age.

Top Replies

  • in reply to Amodin +3 verified

    The problem with the pattern number incrementing has been identified and is being resolved.

    This issue is completely cosmetic and has not had any impact on the continued download and updating of the various pattern sets.

    The pattern number displayed on the WebAdmin screen is usually incremented each time we publish an update to any of the individual up2date pattern sets. It's part of the update, but it is only used for display. The version number of each pattern set is used to check whether any actual updates are required.

    We have identified the cause and corrected it. It was related to some recent changes in the hosting infrastructure for our up2date publishing services.

    You should see the pattern number start to increment again later today.

    Jump to answer
Parents Reply
  • 0 in reply to Amodin

    10 of my and clients firewalls are all stuck on pattern 206808 for 20 hours roughly, don't quote me.  I heard Sophos had tech people in Ukraine working and I don't know the status fo them or that situation, we cyber Threat intel people have been all over twitter since this war started, absolutely amazing how the world is coming together especially the cyber people from every level sharing info etc.  Hopefully the thing will get unstuck or someone that is smarter than me will give a way to manually check the pattern updates  do you see the same thing with your units? mine are all on 9.709, i'll check other clients also.  Thank you all.

Children
No Data