# Elasticsearch Installation: gpg: no valid OpenPGP

**URL:** <https://discuss.elastic.co/t/elasticsearch-installation-gpg-no-valid-openpgp/133223>\
**Category:** Elasticsearch\
**Created:** [May 24, 2018, 8:44pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-gpg-no-valid-openpgp/133223 "2018-05-24T20:44:49Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![am159](https://avatars.discourse-cdn.com/v4/letter/a/90db22/32.png) [@am159](https://discuss.elastic.co/u/am159)\
**Post date:** [May 24, 2018, 8:44pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-gpg-no-valid-openpgp/133223/1 "2018-05-24T20:44:49Z")

</div>

Hello All,  
When trying to install new instance of elasticsearch, I keep getting the below error message.

$ wget -qO - [https://artifacts.elastic.co/GPG-KEY-elasticsearch](https://artifacts.elastic.co/GPG-KEY-elasticsearch) | sudo apt-key add -  
gpg: no valid OpenPGP data found.

I've also tried on a new VM with no luck.  
OS: Ubuntu Server 16.04

Thank you,  
Alex

---

<div class="post-metadata">

**Author:** ![JKhondhu](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@JKhondhu](https://discuss.elastic.co/u/JKhondhu)\
**Post date:** [May 24, 2018, 8:54pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-gpg-no-valid-openpgp/133223/2 "2018-05-24T20:54:34Z")

</div>

In [this thread](https://discuss.elastic.co/t/pgp-keys-fails-to-install-no-valid-openpgp-data-found/32710), a user solved the problem by running the command separately. Perhaps try that?

---

<div class="post-metadata">

**Author:** ![am159](https://avatars.discourse-cdn.com/v4/letter/a/90db22/32.png) [@am159](https://discuss.elastic.co/u/am159)\
**Post date:** [May 24, 2018, 9:12pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-gpg-no-valid-openpgp/133223/3 "2018-05-24T21:12:23Z")

</div>

I just tried and it appears the first command goes through but the second gets stuck at a blank line. Am I supposed to just enter "sudo apt-key add -" on a new line?

---

<div class="post-metadata">

**Author:** ![JKhondhu](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@JKhondhu](https://discuss.elastic.co/u/JKhondhu)\
**Post date:** [May 25, 2018, 10:22am UTC](https://discuss.elastic.co/t/elasticsearch-installation-gpg-no-valid-openpgp/133223/4 "2018-05-25T10:22:32Z")

</div>

sure do try the second portion after the `wget`

---

<div class="post-metadata">

**Author:** ![am159](https://avatars.discourse-cdn.com/v4/letter/a/90db22/32.png) [@am159](https://discuss.elastic.co/u/am159)\
**Post date:** [May 25, 2018, 1:38pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-gpg-no-valid-openpgp/133223/5 "2018-05-25T13:38:07Z")

</div>

Yeah that's what I tried, the second portion just adds a new blank line on the command line and stays there until I ctrl+c

---

<div class="post-metadata">

**Author:** ![am159](https://avatars.discourse-cdn.com/v4/letter/a/90db22/32.png) [@am159](https://discuss.elastic.co/u/am159)\
**Post date:** [May 29, 2018, 3:25pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-gpg-no-valid-openpgp/133223/6 "2018-05-29T15:25:05Z")

</div>

This can be closed. Still wasn't able to get it working so I did a manual install of .deb package with --no-check-certificate and did the hash check

Thank you.

---

<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:** [June 26, 2018, 3:25pm UTC](https://discuss.elastic.co/t/elasticsearch-installation-gpg-no-valid-openpgp/133223/7 "2018-06-26T15:25:06Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.