Jump to content

Remote Agent Unable to Connect to ERA


Recommended Posts

I'm trying to install the remote agent onto an AWS instance and am getting the following error:

Quote

It is not possible to connect to the ESET Security Management Center Server.

I have opened the firewall ports for TCP 2222 and 2223, and tested them using telnet as listed in a previous post (https://forum.eset.com/topic/15968-it-is-not-possible-to-connect-to-the-eset-remote-administrator-server/).

Any help or advice is welcome and appreciated.

Link to post
Share on other sites
  • Most Valued Members

Hi,

Where is this being shown in?  The agent installation log or somewhere else?  What operating system does this AWS instance run on?

:ewong

 

Link to post
Share on other sites

The agent it installed on Centos 7.7 and is version 7.1.503.0.  It was installed from the RPM presented on the ESET downloads page.

The error occurs during configuration, when running the agent-linux-x68_64.sh command.

$sudo bash agent-linux-x86_64.sh --hostname=redacted.domain.com --port=2222 --webconsole-port=2223 --webconsole-user=redactedUsername --webconsole-password=redactedPassword

Do you accept the license? [y/N]:
y

Product improvement program
Participating in product improvement program includes sending crash reports and anonymous telemetry data such as OS version and type, ESET product version and other product-specific information to ESET when enabled.

Do you want to participate in the Product improvement program? [Y/n]:
n
Creating directories...
Creating 'install' directory path: /opt/eset/RemoteAdministrator/Agent
Creating 'config' directory path: /etc/opt/eset/RemoteAdministrator/Agent
Creating 'data' directory path: /var/opt/eset/RemoteAdministrator/Agent
Creating 'Pki Cache' directory path: /var/opt/eset/RemoteAdministrator/Agent/pki.eset.com/
Creating 'logs' directory path: /var/log/eset/RemoteAdministrator/Agent
Creating 'libs' directory path: /opt/eset/RemoteAdministrator/Agent
Directories created
The archive will be extracted to: /opt/eset/RemoteAdministrator/Agent
Extracting, please wait...
Checking OpenSSL ... done [OpenSSL 1.0.2k-fips 26 Jan 2017]
Checking installed version ...
Status of current installation is: NEW
New connection settings are 'hostname': 'redacted.domain.com', 'port': 2222
Getting certificate from server...
It is not possible to connect to the ESET Security Management Center Server.
Cleaning up setup directories

 

Link to post
Share on other sites
  • ESET Staff

Could you please check also more detailed log file:

/var/log/eset/RemoteAdministrator/EraAgentInstaller.log

for possible clues? You are performing so called server-assisted installation which requires active connection to ESMC. It might happen due to multiple reasons, mostly network or SSL/TLS related.

Link to post
Share on other sites
  • Most Valued Members

Well, I feel a bit dense, even with the information provided. 

It's my understanding that the command you ran was on the AWS instance and not your workstation (or whereever you access this AWS instance).    Is the ESMC server behind a firewall?  If so, do you happen to have the correct port-forwarding rules?  If it's a system directly connected to the Internet requiring no firewall, then check the ESMC system's firewall.  If it's a windows system, check the incoming port allowances.  If it's a linux ESMC system, check for selinux and iptables rules.

 

Edmund

Link to post
Share on other sites

I was able to get the agent to install by forwarding all ports to it, but would like to know which ports need to be forwarded.  Before I was forwarding 2222-2223 TCP and UDP, but apparently that's not enough.

Link to post
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...