# Upgrading Elastic-Agent via Fleet in an Air-gapped environment failing **URL:** \ **Category:** Elastic Observability\ **Tags:** fleet\ **Created:** [February 16, 2022, 8:13pm UTC](https://discuss.elastic.co/t/upgrading-elastic-agent-via-fleet-in-an-air-gapped-environment-failing/297413 "2022-02-16T20:13:26Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![dyltay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dyltay/32/96741_2.png) [@dyltay](https://discuss.elastic.co/u/dyltay)\ **Post date:** [February 16, 2022, 8:13pm UTC](https://discuss.elastic.co/t/upgrading-elastic-agent-via-fleet-in-an-air-gapped-environment-failing/297413/1 "2022-02-16T20:13:26Z")
Hello, We have an air-gapped environment. Recently upgraded to 8.0.0. The Fleet GUI is rightly showing that the elastic-agents (Linux tar.gz installed) have an upgrade is available, but when trying to upgrade we get the following error: ```auto [elastic_agent][error] failed to dispatch actions, error: failed upgrade of agent binary: 2 errors occurred: * package '/opt/Elastic/Agent/data/elastic-agent-93708b/downloads/elastic-agent-8.0.0-linux-x86_64.tar.gz' not found: open /opt/Elastic/Agent/data/elastic-agent-93708b/downloads/elastic-agent-8.0.0-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.0.0-linux-x86_64.tar.gz": context deadline exceeded ``` I tried to put the already downloaded package in the downloads directory in the error, and re-run the upgrade, but the agent appears to have deleted the existing file and tried to download from the internet again. Is there any option to specify a local location for the elastic-agent-8.0.0-linux-x86\_64.tar.gz package, instead of the one found on the internet that the servers do not have access to? ---
**Author:** ![mostlyjason](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mostlyjason/32/60849_2.png) [@mostlyjason](https://discuss.elastic.co/u/mostlyjason)\ **Post date:** [February 17, 2022, 4:12pm UTC](https://discuss.elastic.co/t/upgrading-elastic-agent-via-fleet-in-an-air-gapped-environment-failing/297413/2 "2022-02-17T16:12:39Z")
This capability is not available at the moment, but we have plans to add it in the future [[Fleet] Ability to configure agent.download.sourceURI in Kibana · Issue #100413 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/100413). One workaround is to set up a proxy server. Another is to uninstall the old agent via CLI, then install the new version. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 4, 2022, 8:34am UTC](https://discuss.elastic.co/t/upgrading-elastic-agent-via-fleet-in-an-air-gapped-environment-failing/297413/3 "2022-11-04T08:34:15Z")