davidenco 1 Posted September 12, 2022 Posted September 12, 2022 All our clients last connected to the cloud console nearly an hour ago. The Agent status log says this: Error: Replication connection problem: Stream removed (code: 2) for request Era.Common.Services.Replication.CheckReplicationConsistencyRequest Error: Replication connection problem: Response for request of type DeviceSessionTokenRequest (request id: 99) was not received in time Are you having an outage?
davidenco 1 Posted September 12, 2022 Author Posted September 12, 2022 Now seeing HTTP 504 (Gateway Timeout) messages! Error: Replication connection problem: Received http2 header with status: 504 (code: 1) for request Era.Common.Services.Replication.CheckReplicationConsistencyRequest
Administrators Marcos 5,733 Posted September 12, 2022 Administrators Posted September 12, 2022 All systems are fully operational at the moment: https://status.eset.com/ Please open a support ticket for further troubleshooting of the issue.
davidenco 1 Posted September 12, 2022 Author Posted September 12, 2022 Latest status message states "503" as being the error code that your server is responding with. That's a service unavailable error. Technical support are non the wiser. I'm aware there's an outage tomorrow. Has someone decided to kick things off a full day early and just not admit to it or update the status page? Error: Replication connection problem: Received http2 header with status: 503 (code: 1) for request Era.Common.Services.Replication.CheckReplicationConsistencyRequest (id: 506da417-093f-4bc9-9783-796589e45f4d) on connection to 'host: "%hash%.a.ecaserver.eset.com" port: 443'
davidenco 1 Posted September 12, 2022 Author Posted September 12, 2022 I am now getting an error "Too many requests. Try again later. (Code: 8)"... in TWO separate worldwide locations. One location has the workstations running the Agent and Endpoint Security combined, whereas the other location is a Linux web server that only has the Agent installed. This issue is occurring on two completely separate networks and different geographical locations.
Recommended Posts