Ucho1211 0 Posted January 8, 2019 Posted January 8, 2019 We start to use ESMC as virual appliance I set proxy for ESMC too , i add some pc to ESMC console . Problems ESMC (7.0) got error for update : Update modules/Update/Could not connect to server./Failed/System user/system/yes I set proxy in esmc setting . Client Endpoint SEC (7.0.2) have problem with liveGrid after proxy is set to ESMC ( befor we use Endpoint with proxy too but for our standard http proxy and livegrid work) Standart client update work. Did I miss something, ESMCLiveGridLog.zip
ESET Staff MichalJ 434 Posted January 8, 2019 ESET Staff Posted January 8, 2019 (edited) I would recommend that you contact ESET Technical Support in Slovakia which might be able to help you. But maybe @Marcos will have an idea directly Edited January 8, 2019 by MichalJ
Administrators Marcos 5,446 Posted January 8, 2019 Administrators Posted January 8, 2019 If you already have a proxy in your network, you can use the existing one. It is not mandatory to install and use ESET HTTP Proxy. If ESET HTTP Proxy connects through an existing proxy, it will work only if the superior proxy doesn't require authentication. Please check the HTTP Proxy logs for possible errors.
Ucho1211 0 Posted January 8, 2019 Author Posted January 8, 2019 If you already have a proxy in your network, you can use the existing one. Och OK i just change proxy to corporation default and its ok for end point client ESMC still error on update "Update modules/Update/Could not connect to server./Failed/System user/system/yes" Proxy is set correctly in ADVANCED SETTINGS
Administrators Marcos 5,446 Posted January 8, 2019 Administrators Posted January 8, 2019 I assume that you have the proxy server set up correctly here since no issue is reported with connectivity to the repository. Try restarting the ESMC service (on Windows) or the whole VA to enforce a module update.
Ucho1211 0 Posted January 8, 2019 Author Posted January 8, 2019 HTTP proxy is set "Use direct connection if HTTP proxy is not available" is OFF After restart OK any idea why Default proxy client policy do not work ? I try preconfigured "HTTP Proxy Usage" in "ESET Endpoint for Windows"
Recommended Posts