Bad pattern updates again???

Hello PatrickLee,

Thank you for contacting to the community, and indeed it is getting blocked, reason=Host not found || even in the logs you shared:  error="Host not found 
And you can also check from the policy test:


You can submit the url request sample > select the product Sophos UTM
https://support.sophos.com/support/s/filesubmission?language=en_US

Hi Vivek,

This is the same issue I had brought up last month and resolved by Sophos staff Rick Baldry.  Please follow the URL above and read the solution.

I'll just go ahead and set this here, so we know what we are starting off with this week, lol.

According to Sophos staff Rick Baldry,

bad pattern updates......AGAIN???? - General Discussion - UTM Firewall - Sophos Community

It was related to some recent changes in the hosting infrastructure for our up2date publishing services.". 

I've noticed the pattern version updating.  I've not experienced though what is shown above yet.

I'm experiencing similar issue to my previous post on my iPhone (email stuck, apple store blocked, apple weather app not updating) and on my Windows laptop (windows updates stuck).  Reply to Vivek (Sophos staff), but it seems nothing else is coming him indicating they are looking at the issue.

Also I noticed that the status code in the log is statuscode="502"
Indicates: Bad Gateway server error response code indicates that the server, while acting as a gateway or proxy, received an invalid response from the upstream server.

Whenever there's a statuscode="5xx" block, first try an Exception for antivirus.  If the problem persists, the only solution is to skip the Proxy.  I've found that many Apple downloads require skipping the Proxy.

Cheers - Bob

My issue causing my iPhone unable to connect to the Apple Store or the weather app got stuck or email not fetching, and Windows update not working was similar to my previous post about bad pattern updates https://community.sophos.com/utm-firewall/f/general-discussion/133028/bad-pattern-updates-again until a Sophos staff Rick Baldry posting indicating the issue was identified and resolved and it was related to "recent changes to the updates hosting infrastructure for our up2date publishing services." My problem is now resolved after rebooting my UTM, so it seems pattern updates is not synchronizing among infrastructure hosting up2date publishing services.