Jump to content

protect cloud not reachable


gregxn

Recommended Posts

I have problem with 5-10 computers that wont/cant reach eset servers. Nor activation, updates, cloud console.

eset.com opens normally. No firewall rules, DNS working correctly,

tracert reaches end destination on checking, but not opening XML in browser:

repository.eset.com  / hxxp://repository.eset.com/v1/info.meta

repositorynocdn.eset.com / hxxp://repositorynocdn.eset.com/v1/info.meta

edf.eset.com  / https://edf.eset.com/edf

Here is agent trace log.

2022-06-13 06:36:21 Error: CReplicationModule [Thread 1078]: InitializeFailOverScenario: Skipping fail-over scenario (stored replication link is the same as current) [RequestId: 10760fe7-a36a-44f4-8fec-8b7446637543]
2022-06-13 06:36:21 Error: CReplicationModule [Thread 1078]: CAgentReplicationManager: Replication finished unsuccessfully with message: InitializeConnection: Initiating replication connection to 'host: "xxxxxxxxxxxx.a.ecaserver.eset.com" port: 443' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "xxxxxxxxxxxxxx.a.ecaserver.eset.com" port: 443 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 14, error message:  Connect Failed, and error details: . Request Id: 10760fe7-a36a-44f4-8fec-8b7446637543 Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: xxxxxxxxxxxxxx.a.ecaserver.eset.com:443, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: ae125732-1e81-40fd-b7e6-9c077d82a667, Sent logs: 0, Cached static objects: 69, Cached static object groups: 10, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0]

i see here some proxy, But agents and endpoints were explicitly set not to use any proxy.

The local network is behind NAT.

 

offline licenses is not an option.

Link to comment
Share on other sites

  • Administrators
47 minutes ago, Michael Heumann said:

Any news on this issue...we have the same problem starting today.

URL reachable, but Repository is empty

This is a problem on the server. Are you really using ESET Protect cloud and not ESET PROTECT on-premise ?

Link to comment
Share on other sites

just wanted to add, no trsafic inspection device, Firewall allows outbound, incoming trafic is behind NAT. 

If i enable VPN to our main office, where all the traffic on computer will go into tunnel replication works, and links in first post are accessible. 

dns resolution works with and without vpn (again links from first post, as well eset cloud address). 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...