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

MCS 504 issues just started 4/7

I was going to post this in the 'Endpoint' forum, but it looks like it got hijacked by spammers or something as it took me like 3 pages to find the 'real' posts.

Starting yesterday around 2am Pacific our Endpoint clients starting complaining about 504 issues with the Sophos Management Communications System randomly throughout the day (and into today, still occurring).  I know this could possibly be a firewall/network issue (Sophos UTM) but I wanted to check to see if anyone else was having the issue first.  We appear to normally talk to the 'west 2' URL at https://mcs2-cloudstation-us-west-2.prod.hydra.sophos.com:443/sophos/management/ep

I haven't yet been able to confirm if any devices outside of our network perimeter are having the issue, I'm trying to locate one.

Any feedback is appreciated, thanks!



This thread was automatically locked due to age.
Parents
  • This issue appears to be affecting new installs too, as the client will fail with a 504 error while to trying to register itself in Central.    I've found the corresponding entry in our UTM web filter logs and they all show '200' for each event.    I also found some previous posts on here from a few years ago with the same issue, which then just went away after a while and most people suspected that Sophos simply 'fixed' the issue.    It looks like the client only waits for 10 seconds from a response from the other end before giving up, so it seems like maybe the servers are congested right now?

Reply
  • This issue appears to be affecting new installs too, as the client will fail with a 504 error while to trying to register itself in Central.    I've found the corresponding entry in our UTM web filter logs and they all show '200' for each event.    I also found some previous posts on here from a few years ago with the same issue, which then just went away after a while and most people suspected that Sophos simply 'fixed' the issue.    It looks like the client only waits for 10 seconds from a response from the other end before giving up, so it seems like maybe the servers are congested right now?

Children