Jump to content

davidenco

Members
  • Posts

    99
  • Joined

About davidenco

  • Rank
    Newbie
    Newbie

Profile Information

  • Gender
    Male
  • Location
    Great Britain

Recent Profile Visitors

1,657 profile views
  1. I cannot access EBA or ECOS as of a few minutes ago. ECOS gives me a HTTP 400 error, whereas EBA logs in but then displays a spinning icon.
  2. Status page now says maintenance window has been extended by another 4 hours.
  3. No, this is after closing browser, clearing cookies, etc. I just spoke to technical support who say they are still seeing all cloud services unavailable and they have not been told why, even after asking head office who don't even know themselves what is going on! This is really concerning. Have you been hacked?
  4. Do you know why it's taking longer than 4 hours and when it will be available? I cannot access our email quarantine and need to do so as a matter of urgency. Never known maintenance to be done during the working day.
  5. Has the maintenance run over? It's 13:06 CEST and I still cannot access any cloud services.
  6. 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.
  7. 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'
  8. 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
  9. 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?
  10. All our servers and clients are failing to update via ESMC. The ESMC logs are displaying a lot of HTTP 401 and HTTP 502 errors, but only since around 13:00 today. Is this a global issue that you're aware of? ESMC has been rebooted and the proxy cache cleared but to no avail. 10.1.1.51 - - [14/Oct/2019:16:00:24 +0100] "HEAD hxxp://update.eset.com/eset_upd/ep7/dll/update.ver.signed HTTP/1.1" 502 - "-" "EEA Update (**SNIP**)" 10.1.1.51 - - [14/Oct/2019:16:00:24 +0100] "HEAD hxxp://um09.eset.com/eset_upd/ep7/dll/update.ver.signed HTTP/1.1" 502 - "-" "EEA Update (**SNIP**)" 10.1.1.51 - - [14/Oct/2019:16:00:24 +0100] "HEAD hxxp://um11.eset.com/eset_upd/ep7/dll/update.ver.signed HTTP/1.1" 502 - "-" "EEA Update (**SNIP**)" 10.1.1.85 - - [14/Oct/2019:16:00:25 +0100] "CONNECT edf.eset.com:443 HTTP/1.1" 200 - "-" "-" 10.1.1.51 - - [14/Oct/2019:16:00:25 +0100] "HEAD hxxp://91.228.166.13/eset_upd/ep7/dll/update.ver.signed HTTP/1.1" 502 - "-" "EEA Update (**SNIP**)" 10.1.1.51 - - [14/Oct/2019:16:00:26 +0100] "HEAD hxxp://um02.eset.com/eset_upd/ep7/dll/update.ver.signed HTTP/1.1" 502 - "-" "EEA Update (**SNIP**)" 10.1.1.51 - - [14/Oct/2019:16:00:27 +0100] "HEAD hxxp://um07.eset.com/eset_upd/ep7/dll/update.ver.signed HTTP/1.1" 401 - "-" "EEA Update (**SNIP**)" 10.1.1.51 - - [14/Oct/2019:16:00:28 +0100] "GET hxxp://um07.eset.com/eset_upd/ep7/dll/update.ver.signed HTTP/1.1" 502 487 "-" "EEA Update (**SNIP**)" 10.1.1.51 - - [14/Oct/2019:16:00:30 +0100] "GET hxxp://um07.eset.com/eset_upd/ep7/dll/update.ver.signed HTTP/1.1" 502 487 "-" "EEA Update (**SNIP**)" 10.1.1.51 - - [14/Oct/2019:16:00:31 +0100] "HEAD hxxp://um05.eset.com/eset_upd/ep7/dll/update.ver.signed HTTP/1.1" 502 - "-" "EEA Update (**SNIP**)" 10.1.1.51 - - [14/Oct/2019:16:00:31 +0100] "HEAD hxxp://38.90.226.39/eset_upd/ep7/dll/update.ver.signed HTTP/1.1" 502 - "-" "EEA Update (**SNIP**)" 10.1.1.51 - - [14/Oct/2019:16:00:33 +0100] "HEAD hxxp://um03.eset.com/eset_upd/ep7/dll/update.ver.signed HTTP/1.1" 502 - "-" "EEA Update (**SNIP**)"
  11. I just noticed these entries in the error_log on the ESMC Virtual Appliance. Could this be the problem? [Thu May 09 10:21:02.646568 2019] [access_compat:error] [pid 4373:tid 139798693996288] [client 10.1.1.76:3148] AH01797: client denied by server configuration: proxy:http:/repository.eset.com/v1/com/eset/apps/business/eea/windows/metadata3 [Thu May 09 10:28:07.070201 2019] [access_compat:error] [pid 4373:tid 139798954215168] [client 10.1.1.17:43234] AH01797: client denied by server configuration: proxy:hxxp:/// [Thu May 09 10:38:17.186629 2019] [access_compat:error] [pid 4588:tid 139798836672256] [client 10.1.1.17:43748] AH01797: client denied by server configuration: proxy:hxxp:/// [Thu May 09 10:48:27.266414 2019] [access_compat:error] [pid 4588:tid 139798777923328] [client 10.1.1.17:44598] AH01797: client denied by server configuration: proxy:hxxp:/// [Thu May 09 10:58:37.538603 2019] [access_compat:error] [pid 4373:tid 139798794708736] [client 10.1.1.17:45206] AH01797: client denied by server configuration: proxy:hxxp:/// [Thu May 09 11:08:47.586300 2019] [access_compat:error] [pid 4372:tid 139798945822464] [client 10.1.1.17:46088] AH01797: client denied by server configuration: proxy:hxxp:/// [Thu May 09 11:18:57.845311 2019] [access_compat:error] [pid 4374:tid 139798962607872] [client 10.1.1.17:46702] AH01797: client denied by server configuration: proxy:hxxp:/// [Thu May 09 11:29:07.926779 2019] [access_compat:error] [pid 4374:tid 139798777923328] [client 10.1.1.17:47540] AH01797: client denied by server configuration: proxy:hxxp:/// [Thu May 09 11:39:08.306905 2019] [access_compat:error] [pid 4374:tid 139798719174400] [client 10.1.1.17:48080] AH01797: client denied by server configuration: proxy:hxxp:/// [Thu May 09 11:49:18.604284 2019] [access_compat:error] [pid 4588:tid 139798929037056] [client 10.1.1.17:48882] AH01797: client denied by server configuration: proxy:hxxp:/// [Thu May 09 11:59:28.867581 2019] [access_compat:error] [pid 4588:tid 139798836672256] [client 10.1.1.17:49616] AH01797: client denied by server configuration: proxy:hxxp:/// [Thu May 09 12:09:29.567019 2019] [access_compat:error] [pid 4588:tid 139798735959808] [client 10.1.1.17:50608] AH01797: client denied by server configuration: proxy:hxxp:/// [Thu May 09 12:19:32.004482 2019] [access_compat:error] [pid 4373:tid 139798761137920] [client 10.1.1.17:51794] AH01797: client denied by server configuration: proxy:hxxp:/// [Thu May 09 12:23:40.539484 2019] [access_compat:error] [pid 4372:tid 139798920644352] [client 10.1.1.2:13054] AH01797: client denied by server configuration: proxy:http:/repository.eset.com/v1/com/eset/apps/business/ems/exchange/metadata3 [Thu May 09 12:29:33.354294 2019] [access_compat:error] [pid 4373:tid 139798937429760] [client 10.1.1.17:52960] AH01797: client denied by server configuration: proxy:hxxp:///
  12. In ESMC v7; clicking OK despite the error works fine though, and reopening the condition to edit it shows the expression with no error, until the box is cleared and the text re-entered. Also, focusing on another field does not update the field's error state.
  13. The message disappears when I check for an update manually (as it has already done), so doing what you've suggested isn't going to work. Any suggestions?
  14. Did you read the entire post or just the reference I made to EDTD? This is nothing to do with EDTD, I don't even see it in the UI!
×
×
  • Create New...