Jump to content

Update to 6.2 failing


jthomas
 Share

Recommended Posts

I'm running a client task to update ERA agent to 6.2 and receiving the following error. 

 

2015-09-09 15:28:17 Error: CSystemConnectorModule [Thread 1340]: UpgradeInfrastructure: Task failed: GetFile: Cannot connect to host 'repository.eset.com'

 

Yes we use a proxy. Sometimes antivirus fails to install as well. For our ERA server I had to manually update it yesterday for the same issues. The ERA proxy policy is setup and also pushed to this test unit. 

Edited by jthomas
Link to comment
Share on other sites

  • Administrators

That looks like an issue with the http proxy. Do you use Apache HTTP Proxy that is bundled with ERA all-in-one installer? Does restarting the proxy server process help? If you installed agent using Live installer (EraAgentInstaller.bat), was the proxy server set up properly?

 

 

set server_hostname=
set server_port=
set peer_cert_b64=
set peer_cert_pwd=
set ca_cert_b64=

set http_proxy_hostname=
set http_proxy_port=
set http_proxy_username=
set http_proxy_password=

Link to comment
Share on other sites

If it helps, I've had the same issue today but we don't have any proxy at all. I was able to copy the agent to the remote PC using TeamViewer and install it from there.

 

Normally it works okay.

 

 

 

Jim

Link to comment
Share on other sites

That looks like an issue with the http proxy. Do you use Apache HTTP Proxy that is bundled with ERA all-in-one installer? Does restarting the proxy server process help? If you installed agent using Live installer (EraAgentInstaller.bat), was the proxy server set up properly?

 

 

set server_hostname=

set server_port=

set peer_cert_b64=

set peer_cert_pwd=

set ca_cert_b64=

set http_proxy_hostname=

set http_proxy_port=

set http_proxy_username=

set http_proxy_password=

 

We do not use the bundled Apache proxy. We are using Microsoft TMG 2010 for this location. Viewing the live agent installer it does include the proxy settings in the .bat file. One issue I originally ran into is it seemed the username needed to be "DOMAIN\user" but I am unsure if this is true. I've tried this time around either with or without the domain and it fails the same both ways. 

 

If I take the url for the msi package I am able to download it through a web browser on that machine using the http proxy. 

Link to comment
Share on other sites

If it will help we have the same problem and it seems that old agent did not use proxy setting to download from eset servers.

This is the topic of our problem with more info:

https://forum.eset.com/topic/5899-era-program-component-upgrade-faild-via-apacheproxy/

Link to comment
Share on other sites

We check this problem and we set the direct internet via gateway and then agent upgarade successfully while it is configured to use our apache proxy server.

Try the direct internet while agent is configure to use apache proxy and let us know the result.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

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