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

The following is from AN OLD POST SO IGNORE the errors.....

>>> Modules::Audld::LocalRestriction::_seek_own_country::130()
Could not connect to Server us1.utmu2d.sophos.com (status=500 Can't connect to us1.utmu2d.sophos.com:443 (timeout)).

>>> Modules::Audld::LocalRestriction::_seek_own_country::130()
Could not connect to Server us2.utmu2d.sophos.com (status=500 Can't connect to us2.utmu2d.sophos.com:443 (timeout)).

>>> Modules::Audld::LocalRestriction::_seek_own_country::130()
Could not connect to Server sg1.utmu2d.sophos.com (status=500 Can't connect to sg1.utmu2d.sophos.com:443 (timeout)).

>>> Modules::Audld::LocalRestriction::_seek_own_country::130()
Could not connect to Server eu1.utmu2d.sophos.com (status=500 Can't connect to eu1.utmu2d.sophos.com:443 (timeout)).

>>> Modules::Audld::LocalRestriction::_seek_own_country::130()
Could not connect to Server eu2.utmu2d.sophos.com (status=500 Can't connect to eu2.utmu2d.sophos.com:443 (timeout)).

but at least it gives what may still be the upmu2d nslookup names.  appears they're all on amazon aws which is never ever good, single point of failure.  I hope someone from sophos logs into here and reads this and looks into it,  many of us don't have time to call sophos tech support and wait on hold for hours and still not get resolution.  Is some employee from sophos reading this???

I was wondering restoring to 9.708-6 would also restore previous pattern updates?

cool

it is up, it was on 206.675, and the newest update it sees is206808..... dangit..

that snapshot was from jan 27 2022

can you change to manual in the configuration tab, so it doesn't auto update.

yes, did that, on manual. sees 206808

it was on a sum to update also, now direct, it sees the same 206808...... so I guess if you're having other issues and you restore to 9.708 iso and that datafile backup then turn off autoupdate you'd be back in business. just don't update the pattern, 

i just got a spam email in through it, i have it as a 60 on my mx record so not much goes through it except spam.

guess just have to wait for Sophos.  Hope someone from Sophos see this thread.  I'm just seeing random issue.

what features aren't working?  sometimes, or actually if something is fried, i'd restore the iso, update it to 708, load the708 newest backup and be happy for a bit.

I've had stupid things happening in the past before, on many different brands of FW, just re-ISO it, restore backup from last night and all the weird crap goes away.  If I could find a forcepoint brain/reseller, i'd do that as a test, they're total overkill but looks like overkill would be normal these days. haha

I've had stupid things happening in the past before, on many different brands of FW, just re-ISO it, restore backup from last night and all the weird crap goes away.  If I could find a forcepoint brain/reseller, i'd do that as a test, they're total overkill but looks like overkill would be normal these days. haha