Jump to content

Urgent Problem with Agent 9.1.1295.0


Go to solution Solved by Peter Randziak,

Recommended Posts

Hello

I started to upgrade Eset Management Agent 9.0.1141.0 to 9.1.1295.0. I got an issue... For now, I upgraded only 2 clients, and with only these 2 clients I cannot connect anymore to Eset Protect Cloud.... the last syncoinization date is exactly some minutes before the upgrade.

I investigated analyzing our firewall logs and I found this:

- Management Agent 9.0.1141.0 establishes connection to an hostname, ie: https://xxxxxxxxxxxxx.a.ecaserver.eset.com  

- Management Agent 9.1.1295.0 establishes connection to the ip address of previously indicated hostname, ie: https://xxx.yyy.www.zzz

Of course, my firewall is set to bypass https inspection scan for all urls that contains eset.com, eset.systems, eset.eu hostnames. When i added another exception for https://xxx.yyy.www.zzz url, also the clients with 9.1.1295.0 could connect to Protect Cloud.

Of course, this is a temporary workaround, the ip address associated to the hostname may change... so, I suppose that you should consider to fix this issue.

 

Thanks

Fabio

Link to comment
Share on other sites

  • ESET Moderators

Hello @eclipse79,

I'm checking it with the dev team.

Can you please provide us with the status.log and trace.log logs?

If you can capture the connection attempt with a Wireshark, it might help too.

You can send them to me via a private message. 

Peter

Link to comment
Share on other sites

1 hour ago, Peter Randziak said:

Hello @eclipse79,

I'm checking it with the dev team.

Can you please provide us with the status.log and trace.log logs?

If you can capture the connection attempt with a Wireshark, it might help too.

You can send them to me via a private message. 

Peter

Thanks you, I will send you the files

Link to comment
Share on other sites

  • ESET Moderators

Hello @eclipse79,

The SNI was not sent by the agent, which caused the behavior you reported.

We already have a fix for it, new agent version will be probably released to address it.

Peter 

(P_EP-26930)

Link to comment
Share on other sites

11 minutes ago, Peter Randziak said:

Hello @eclipse79,

The SNI was not sent by the agent, which caused the behavior you reported.

We already have a fix for it, new agent version will be probably released to address it.

Peter 

(P_EP-26930)

Thank you Peter,

is this issue also present on new MacOS agent release?

Link to comment
Share on other sites

  • ESET Moderators
59 minutes ago, eclipse79 said:

Thank you Peter,

is this issue also present on new MacOS agent release?

You are welcome, pleasure is on our side.

It seems that the management agent for macOS is affected too.

Peter

Link to comment
Share on other sites

4 minutes ago, Peter Randziak said:

You are welcome, pleasure is on our side.

It seems that the management agent for macOS is affected too.

Peter

Thank you,

last question: is there any way to install previous agent version 9.0.1141.0? Or do you suggest to wait until next release? All my clients have 9.1.2051.0 Enpoint realease with 9.0.1141.0 agent, except for 3 clients with 9.1.1295.0 agent.

Thanks

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

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