MichaelWest

Hi @marcos. I've been working with Alex in business support who could possibly provide more information. There is a certificate negotiation problem as far as I can tell. Alex said that auth is supported for caching functions but not replication. Your documentation online says that a proxy must not require authentication. https://help.eset.com/protect_install/91/en-US/arch_proxy.html At our company we're being migrated to all outbound traffic going through squid proxy requiring auth. They're moving away from direct internet access via firewall rules. We've had in place an on-prem ESET Protect Server with firewall opened to ESET cloud services, and your apache proxy on the eset server. We're trying to migrate to ESET Protect Cloud using our proxy with auth, and I've been unable to get this working with your support team. I'd appreciate any help you can give trying to figure this out. Our deployment methodology btw is to install agent_x64.msi alongside the install_config.ini file provided via the Installers page in our cloud management console.

Description Add support for proxy authentication for agent connections. Detail Our company is moving to requiring a authenticated proxy connection for all traffic to external services. They are not going to allow unauthenticated connections and no firewall rules for direct-network access. I worked with ESET support and it looks like authenticated proxy isn't supported for the replication fxnality ESET using a proxy. I'm not sure I'll be able to get an exception to this company-wide security rule, so this may require us to move off ESET as our AV solution.