# ElasticSearch 2.3 installation with apt fails 404

**URL:** <https://discuss.elastic.co/t/elasticsearch-2-3-installation-with-apt-fails-404/45848>\
**Category:** Elasticsearch\
**Created:** [March 30, 2016, 8:15pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-installation-with-apt-fails-404/45848 "2016-03-30T20:15:57Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![petermeter](https://avatars.discourse-cdn.com/v4/letter/p/59ef9b/32.png) [@petermeter](https://discuss.elastic.co/u/petermeter)\
**Post date:** [March 30, 2016, 8:15pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-installation-with-apt-fails-404/45848/1 "2016-03-30T20:15:57Z")

</div>

Hi there

It seems that the url from ([current reference](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-repositories.html)) for the debian repository is not working.

cat /etc/apt/sources.list.d/elasticsearch-2.3.list  
`deb http://packages.elastic.co/elasticsearch/2.3/debian stable main`

aptitude update says:  
`W: Failed to fetch http://packages.elastic.co/elasticsearch/2.3/debian/dists/stable/main/binary-amd64/Packages: 404 Not Found [IP: 184.72.244.137 80]`

Thanks for any help

Peter

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 30, 2016, 9:40pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-installation-with-apt-fails-404/45848/2 "2016-03-30T21:40:42Z")

</div>

I think there is a typo, it should be;

```auto
echo "deb http://packages.elastic.co/elasticsearch/2.x/debian stable main" | sudo tee -a /etc/apt/sources.list.d/elasticsearch-2.x.list

```

We removed specific repos for minor releases.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 30, 2016, 9:45pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-installation-with-apt-fails-404/45848/3 "2016-03-30T21:45:12Z")

</div>

I've raised this - [https://github.com/elastic/elasticsearch/issues/17423](https://github.com/elastic/elasticsearch/issues/17423)

(I'm travelling at the moment otherwise I would submit a PR!)

---

<div class="post-metadata">

**Author:** ![billmurrin](https://avatars.discourse-cdn.com/v4/letter/b/3ab097/32.png) [@billmurrin](https://discuss.elastic.co/u/billmurrin)\
**Post date:** [March 31, 2016, 2:10am UTC](https://discuss.elastic.co/t/elasticsearch-2-3-installation-with-apt-fails-404/45848/4 "2016-03-31T02:10:31Z")

</div>

Unable to update any of my packages with yum.

When I hardcode 2.3 instead of 2.x inside of my repo file I get the following:

`http://packages.elastic.co/elasticsearch/2.3/centos/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: elasticsearch-2.3. Please verify its path and try again`

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 31, 2016, 2:15am UTC](https://discuss.elastic.co/t/elasticsearch-2-3-installation-with-apt-fails-404/45848/5 "2016-03-31T02:15:49Z")

</div>

The same thing applies.

---

<div class="post-metadata">

**Author:** ![billmurrin](https://avatars.discourse-cdn.com/v4/letter/b/3ab097/32.png) [@billmurrin](https://discuss.elastic.co/u/billmurrin)\
**Post date:** [March 31, 2016, 9:08pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-installation-with-apt-fails-404/45848/6 "2016-03-31T21:08:57Z")

</div>

Think we are also going back and forth on twitter.

What I'm trying to say is that the yum updates for all of my es products are showing no updates.

I have .repo files setup for the .x version of elasticsearch, logstash and kibana. This worked fine for the last release. Not sure what is causing this.

---

<div class="post-metadata">

**Author:** ![Brian\_Klippel](https://avatars.discourse-cdn.com/v4/letter/b/919ad9/32.png) [@Brian\_Klippel](https://discuss.elastic.co/u/Brian_Klippel)\
**Post date:** [April 1, 2016, 1:07pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-installation-with-apt-fails-404/45848/7 "2016-04-01T13:07:09Z")

</div>

I need to upgrade specifically to 2.2.1 because that's the highest version one of my critical plugins currently supports. Does that mean I can no longer use apt-get for my install and update? I'm not a fan of installing by zip, I never trust that configurations will be preserved.

Disregard, it was just explained to me on a related github thread that the minor version can be specified during apt-get install. Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:03pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-installation-with-apt-fails-404/45848/8 "2017-07-05T23:03:15Z")

</div>


