Jump to content

AdWiMa

Members
 View Profile  See their activity

  • Posts

    5

  • Joined

  • Last visited

Kudos

2 Trainee Reputation badge

See kudos

About AdWiMa

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Germany
  1. AdWiMa
    We already have a ticket open for this and wait for an answer (Cyprotect).
  2. AdWiMa
    ESET Bridge is installed on the ESET PROTECT Server. After a reboot or restart of the service, the updates no longer work. In the error.log file of Nginx we find a lot of errors of the following kind. 2023/12/27 10:05:43 [notice] 7764#3740: signal process started 2023/12/27 10:05:43 [error] 5636#5392: *133054 connect() failed (10060: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat) while connecting to upstream, client: 127.0.0.1, server: , request: "HEAD /eset_upd/server7/dll/update.ver.signed HTTP/1.1", upstream: "hxxp://91.228.167.21:80/eset_upd/server7/dll/update.ver.signed", host: "91.228.167.21" ... 2023/12/27 10:05:46 [error] 5636#5392: *132016 connect() failed (10060: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /v1/auth/A0CCC998C81F3D96CAA1/updlist/0/eid/11269961/lid/11270122 HTTP/1.1", upstream: "hxxp://91.228.165.40:80/v1/auth/A0CCC998C81F3D96CAA1/updlist/0/eid/11269961/lid/11270122", host: "i5.c.eset.com:80" 2023/12/27 10:05:46 [warn] 5636#5392: *132016 upstream server temporarily disabled while connecting to upstream, client: 127.0.0.1, server: , request: "GET /v1/auth/A0CCC998C81F3D96CAA1/updlist/0/eid/11269961/lid/11270122 HTTP/1.1", upstream: "hxxp://91.228.165.40:80/v1/auth/A0CCC998C81F3D96CAA1/updlist/0/eid/11269961/lid/11270122", host: "i5.c.eset.com:80" Does anyone know these errors and has a solution?
  3.    Arko reacted to a post in a topic: Failed to update the agent through Eset Protect Cloud
  4. AdWiMa
    we have redirected the cache folder to another drive via the bridge policy
  5.    ma77y88 reacted to a post in a topic: Failed to update the agent through Eset Protect Cloud
  6. AdWiMa
    We stopped the ESET Bridge services and then deleted the contents of the cache folder.
  7. AdWiMa
    After we cleared the cache of the bridge it now works for us (on-prem).
×
×
  • Create New...