Jump to content

Endpoint update failed on apache http proxy


Recommended Posts

ESMC was installed one mth ago without apache http proxy. Today, I installed apache http proxy use ESMC AIO installer, edited httpd.conf file and created polices for Agent and Endpoint to update using it (Refer to https://support.eset.com/en/kb6750-install-apache-http-proxy-esmc-7x). But endpoint update failed with error "Module update failed, Unauthorized access". I didn't configure username and password.

 

 

 

Edited by jinlei801011
Link to post
Share on other sites
  • ESET Staff

Could you please double check that HTTP proxy was not installed with enabled mandatory authorization? Asking because referenced tutorial mentions this optional step in section 8 If you want to configure a username and password as last step of manual installation. If so, HTTP proxy requires authentication and thus providing credentials to endpoint is required - or authentication can be disabled by removing specific proxy configuration part.

Link to post
Share on other sites
18 hours ago, MartinK said:

Could you please double check that HTTP proxy was not installed with enabled mandatory authorization? Asking because referenced tutorial mentions this optional step in section 8 If you want to configure a username and password as last step of manual installation. If so, HTTP proxy requires authentication and thus providing credentials to endpoint is required - or authentication can be disabled by removing specific proxy configuration part.

Hi MartinK,

I didn't go to the section 8 to configure a username and password. I installed it using ESMC AIO installer. Added below ProxyMatch to httpd.conf file, and then configured policies for Agent and Endpoint.

<ProxyMatch (?i)^(172\.17\.253\.189(:[0-9]+)?(\/.*)?)$>
Allow from all
</ProxyMatch>

Link to post
Share on other sites
  • ESET Staff

One you mentioned ProxyMatch I realized that also this might be an issue, as it is not clearly communicated in referenced article.

Could you also check, that your httpd.conf contains lots of other ProxyMatch directives, enabling clients to access ESET servers? If not, I would recommend to check httpd.conf which is part of proxy package for windows. In case directives are matching, clients won't be able to access resources on ESET servers, including updates. Configuration file from windows version contains directives enabling communication with all ESET services that could be possibly accessed by ESET products via HTTP proxy + it just has to be extended with your internal hostnames or addresses in case proxy is to be used for accessing also other resources - this applies especially in proxy is expected to route also AGENT-to-ESMC communication.

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...