Guest User!

You are not Sophos Staff.

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

Endpoint Protection: Timeout was reached ?

Hi

apparently i cant get EP get to work - any ideas ? 
[:S]

TY

2014:06:15-08:11:20 mail-2 epsecd[8406]: W main::_log:432() => severity="warn" sys="System" sub="eplog" name="Listing [d3ceb6c1-2964-36a3-90ef-d6598cadecf0-wdx-2964.broker.sophos.com/.../] failed with return code 28: Timeout was reached SSL connection timeout
2014:06:15-08:14:17 mail-2 epsecd[1020]: >=========================================================================
2014:06:15-08:14:17 mail-2 epsecd[1020]: E id="4281" severity="crit" sys="System" sub="epsecd" name="Unexpected error: Can't locate object method "close" via package "GLOB" at /Epsec/Logic/Client.pm line 1423." effect="Can't talk to Sophos LiveConnect"
2014:06:15-08:14:17 mail-2 epsecd[1020]:
2014:06:15-08:14:17 mail-2 epsecd[1020]: 1. Epsec::Utils::Logging::_log:59() /Epsec/Utils/Logging.pm
2014:06:15-08:14:17 mail-2 epsecd[1020]: 2. Epsec::Logic::Client:[:$]n_error:1446() /Epsec/Logic/Client.pm
2014:06:15-08:14:17 mail-2 epsecd[1020]: 3. Epsec::Logic::Base::run:60() /Epsec/Logic/Base.pm
2014:06:15-08:14:17 mail-2 epsecd[1020]: 4. main::top-level:63() client.pl
2014:06:15-08:14:17 mail-2 epsecd[1020]:  severity="warn" sys="System" sub="eplog" name="Listing [
d3ceb6c1-2964-36a3-90ef-d6598cadecf0-wdx-2964.broker.sophos.com/.../] failed with return code 28: Timeout was reached SSL connection timeout
2014:06:15-08:14:48 mail-2 epsecd[8406]: "


This thread was automatically locked due to age.
Parents
  • Are you using SSL scanning in Web Protection?  Do you have the Exceptions in place for broker.sophos.com?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • If you have country blocking enabled, see if you see drops in your firewall log around the time you see the failure to connect.  A very common issue; often we find new endpoint setups pointing at a LiveConnect server instance in a country we normally block (for instance, Signapore seems to be popular).  The fix would be to add an exception in country blocking (this only works in 9.2xx in my experience) or turn off blocking for the problem country altogether.

    Could be other things, just have seen this one a LOT.  For some reason Sophos doesn't build in exceptions for their own update and cloud servers.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Reply
  • If you have country blocking enabled, see if you see drops in your firewall log around the time you see the failure to connect.  A very common issue; often we find new endpoint setups pointing at a LiveConnect server instance in a country we normally block (for instance, Signapore seems to be popular).  The fix would be to add an exception in country blocking (this only works in 9.2xx in my experience) or turn off blocking for the problem country altogether.

    Could be other things, just have seen this one a LOT.  For some reason Sophos doesn't build in exceptions for their own update and cloud servers.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Children
No Data