Elastic Agents Update Issue Behind Proxy

Elastic Stack Elastic Agent
1

Hello,

I'm having an issue where my Elastic Agents are unable to update. The following error occurs:

[elastic_agent][warn] unable to download package: 2 errors occurred:
	* package '/opt/Elastic/Agent/data/elastic-agent-cdc5ba/downloads/elastic-agent-8.14.1-linux-x86_64.tar.gz' not found: open /opt/Elastic/Agent/data/elastic-agent-cdc5ba/downloads/elastic-agent-8.14.1-linux-x86_64.tar.gz: no such file or directory
	* fetching package failed: Get "https://artifacts.elastic.co/downloads/beats/elastic-agent/elastic-agent-8.14.1-linux-x86_64.tar.gz": dial tcp 34.120.127.130:443: connect: network is unreachable

Our servers are behind a zScaler proxy. I can manually download and update via Curl from https://artifacts.elastic.co without any problems. The Elastic Agents also connect to the Fleet Server successfully. Our cluster is self-hosted and runs on Ubuntu.

We've already configured the proxy in the Agent Binary Download Settings (Beta setting) but the error message persists.

Are there any additional settings where we can specify the proxy URL for the Elastic Agents to use for downloads? The environment variables HTTP_PROXY and HTTPS_PROXY are set in the Linux environment settings.

Is there a way to enable a verbose mode to determine if the proxy is being used and if the issue lies elsewhere? Similar to using curl -v, which we can execute from one of the agent hosts against https://artifacts.elastic.co to confirm that the zScaler proxy is correctly utilized from the environment variables.

Thank you!

2 Likes
2

Hello Werheids,

I too facing the same issue. Do you get any solution on this. Thanks in advance.

3

Unfortunately, we haven't found any solutions. We've migrated most of the agents and the fleet server to Windows Server, which allowed us to work around the issue. For the few Linux servers, we have shell scripts that manually remove and reinstall the agent.