gpg: keyserver receive failed: Server indicated a failureHard drive partition and updating troubleDebian jessie GPG error Clearsigned file isn't validHow to install latest version of Tiled Editor on Linux Mint?How to import keys from a keyserver using gpg in debian?Repo APT secure - apt-get update GPG signature were invalidHow to set up keyserver and port permanentlyGPG keyserver that can directly import-export keys using hkpgpg: keyserver receive failed: No dirmngrGPG - “pacman-key --refresh-keys” fails with “gpg: keyserver refresh failed: Permission denied”Why does gpg --recv-keys work as root but not as a normal user?
How do I create uniquely male characters?
How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?
"You are your self first supporter", a more proper way to say it
Why Is Death Allowed In the Matrix?
TGV timetables / schedules?
Example of a continuous function that don't have a continuous extension
Problem of parity - Can we draw a closed path made up of 20 line segments...
Writing rule stating superpower from different root cause is bad writing
In Japanese, what’s the difference between “Tonari ni” (となりに) and “Tsugi” (つぎ)? When would you use one over the other?
What is the word for reserving something for yourself before others do?
Fully-Firstable Anagram Sets
"to be prejudice towards/against someone" vs "to be prejudiced against/towards someone"
What does CI-V stand for?
How old can references or sources in a thesis be?
Can a Warlock become Neutral Good?
Why doesn't H₄O²⁺ exist?
How to find program name(s) of an installed package?
What are these boxed doors outside store fronts in New York?
What do the dots in this tr command do: tr .............A-Z A-ZA-Z <<< "JVPQBOV" (with 13 dots)
How to write a macro that is braces sensitive?
Do VLANs within a subnet need to have their own subnet for router on a stick?
Is this a crack on the carbon frame?
What do you call a Matrix-like slowdown and camera movement effect?
How is it possible to have an ability score that is less than 3?
gpg: keyserver receive failed: Server indicated a failure
Hard drive partition and updating troubleDebian jessie GPG error Clearsigned file isn't validHow to install latest version of Tiled Editor on Linux Mint?How to import keys from a keyserver using gpg in debian?Repo APT secure - apt-get update GPG signature were invalidHow to set up keyserver and port permanentlyGPG keyserver that can directly import-export keys using hkpgpg: keyserver receive failed: No dirmngrGPG - “pacman-key --refresh-keys” fails with “gpg: keyserver refresh failed: Permission denied”Why does gpg --recv-keys work as root but not as a normal user?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
This error has arise when I add gns repository and try to use this command:
#sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys F88F6D313016330404F710FC9A2FD067A2E3EF7B
the error is:
gpg: keyserver receive failed: Server indicated a failure
debian apt gpg
edited Jan 6 at 21:33
Rui F Ribeiro
41.9k1483142
asked Oct 19 '17 at 2:37
Govinda ChaulagainGovinda Chaulagain
66116
add a comment |
This error has arise when I add gns repository and try to use this command:
#sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys F88F6D313016330404F710FC9A2FD067A2E3EF7B
the error is:
gpg: keyserver receive failed: Server indicated a failure
debian apt gpg
edited Jan 6 at 21:33
Rui F Ribeiro
41.9k1483142
asked Oct 19 '17 at 2:37
Govinda ChaulagainGovinda Chaulagain
66116
as I've explained in my answer and comment to the downvotes, it's related to DNS and the way that dirmngr in version 2.1.6 did reverse DNS that have been removed in version 2.1.8 I recall, but 2.2.x I've installed from Debian testing/unstable (Debian 9 current as at writing this) also fixed this issue.
– Hvisage
Feb 4 '18 at 15:52
add a comment |
This error has arise when I add gns repository and try to use this command:
#sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys F88F6D313016330404F710FC9A2FD067A2E3EF7B
the error is:
gpg: keyserver receive failed: Server indicated a failure
debian apt gpg
edited Jan 6 at 21:33
Rui F Ribeiro
41.9k1483142
asked Oct 19 '17 at 2:37
Govinda ChaulagainGovinda Chaulagain
66116
This error has arise when I add gns repository and try to use this command:
#sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys F88F6D313016330404F710FC9A2FD067A2E3EF7B
the error is:
gpg: keyserver receive failed: Server indicated a failure
debian apt gpg
debian apt gpg
edited Jan 6 at 21:33
Rui F Ribeiro
41.9k1483142
asked Oct 19 '17 at 2:37
Govinda ChaulagainGovinda Chaulagain
66116
edited Jan 6 at 21:33
Rui F Ribeiro
41.9k1483142
asked Oct 19 '17 at 2:37
Govinda ChaulagainGovinda Chaulagain
66116
edited Jan 6 at 21:33
Rui F Ribeiro
41.9k1483142
edited Jan 6 at 21:33
Rui F Ribeiro
41.9k1483142
edited Jan 6 at 21:33
Rui F Ribeiro
41.9k1483142
41.9k1483142
asked Oct 19 '17 at 2:37
Govinda ChaulagainGovinda Chaulagain
66116
asked Oct 19 '17 at 2:37
Govinda ChaulagainGovinda Chaulagain
66116
asked Oct 19 '17 at 2:37
Govinda ChaulagainGovinda Chaulagain
66116
66116
as I've explained in my answer and comment to the downvotes, it's related to DNS and the way that dirmngr in version 2.1.6 did reverse DNS that have been removed in version 2.1.8 I recall, but 2.2.x I've installed from Debian testing/unstable (Debian 9 current as at writing this) also fixed this issue.
– Hvisage
Feb 4 '18 at 15:52
add a comment |
as I've explained in my answer and comment to the downvotes, it's related to DNS and the way that dirmngr in version 2.1.6 did reverse DNS that have been removed in version 2.1.8 I recall, but 2.2.x I've installed from Debian testing/unstable (Debian 9 current as at writing this) also fixed this issue.
– Hvisage
Feb 4 '18 at 15:52
as I've explained in my answer and comment to the downvotes, it's related to DNS and the way that dirmngr in version 2.1.6 did reverse DNS that have been removed in version 2.1.8 I recall, but 2.2.x I've installed from Debian testing/unstable (Debian 9 current as at writing this) also fixed this issue.
– Hvisage
Feb 4 '18 at 15:52
as I've explained in my answer and comment to the downvotes, it's related to DNS and the way that dirmngr in version 2.1.6 did reverse DNS that have been removed in version 2.1.8 I recall, but 2.2.x I've installed from Debian testing/unstable (Debian 9 current as at writing this) also fixed this issue.
– Hvisage
Feb 4 '18 at 15:52
add a comment |
5 Answers
5
active
oldest
votes
Behind a firewall you should use the port 80 instead of the default port 11371 :
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 9A2FD067A2E3EF7B
Sample output:
Executing: /tmp/apt-key-gpghome.mTGQWBR2AG/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv 9A2FD067A2E3EF7B
gpg: key 9A2FD067A2E3EF7B: "Launchpad PPA for GNS3" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
answered Oct 19 '17 at 10:33
GAD3RGAD3R
28k1958114
Not port 11371 or 80 related behind firewall. seems to be rather related to DNS resolution when you start to google the net... ``` Executing: /tmp/apt-key-gpghome.imkAGGXMO8/gpg.1.sh --receive-keys --debug-all -vvv --keyserver hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 -> KEYSERVER --clear hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 <- OK gpg: DBG: chan_3 -> KS_GET -- 0x9C1384B1168FD423 gpg: DBG: chan_3 <- ERR 167772379 Server indicated a failure <Dirmngr>```
– Hvisage
Feb 1 '18 at 15:40
3
I get the same error using dirmngr 2.2.5, and addinghkp://and:80resolved the issue
– d3vid
Apr 11 '18 at 15:25
add a comment |
It has to do with DNS and what your DNS server does or does return for dirmngr ;(
It got introduce since 2.1.16 with dirmngr, and I've been looking for solution myself on 2.1.6 with Debian's default packages. ;(
The correct answer, is: Upgrade to version 2.2.x or later that fixed this problem first time.
answered Feb 1 '18 at 15:42
HvisageHvisage
30319
@StephenKitt it wasn't a different answer, I gave the reason why it broke, as the other answer was a totally inadequate answer with all the wrong reasons why it was failing after I've investigated the 2.1.6 versions on Debian. There wasn't any real other fix than to get the latest version from a testing/unstable branch to get passed this problem, which was not HTTP/firewall related, but the DNS issue
– Hvisage
Feb 4 '18 at 15:50
Sorry, the comment above is a canned comment which wasn’t quite appropriate. Your edited answer does indeed answer the question, thanks.
– Stephen Kitt
Feb 4 '18 at 16:02
add a comment |
Encountered the same issue on ubuntu 18.04, running dirmngr 2.2.4. I went with the option of checking my dns settings and added my local dns server 'nameserver 1.1.1.1' and google's 'nameserver 8.8.8.8'. Then it worked.
answered Nov 9 '18 at 10:19
user320161user320161
211
Specifying explicit DNS servers in my network config solved it for me. Gentoo, using NetworkManager.
– Pistos
Dec 28 '18 at 22:55
Also remember Quad9 (9.9.9.9) for helping to filter out malware/etc. in a privacy-advocacy manner ;)
– Hvisage
Dec 31 '18 at 10:14
add a comment |
Add 0x before key, so that it turns 0xF88F6D313016330404F710FC9A2FD067A2E3EF7B.
This plus GAD3R's answer solved it for me.
answered Feb 17 at 20:52
skilowattskilowatt
13613
add a comment |
This issue was really though for me, none of the proposed solutions worked for me until I found this post on reddit.
I just went and added this line to /etc/resolv.conf
nameserver 8.8.8.8 # Google dns
you can try any other dns and see which one works for you.
answered 2 days ago
Nafaa BouteferNafaa Boutefer
1213
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399027%2fgpg-keyserver-receive-failed-server-indicated-a-failure%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
Behind a firewall you should use the port 80 instead of the default port 11371 :
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 9A2FD067A2E3EF7B
Sample output:
Executing: /tmp/apt-key-gpghome.mTGQWBR2AG/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv 9A2FD067A2E3EF7B
gpg: key 9A2FD067A2E3EF7B: "Launchpad PPA for GNS3" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
answered Oct 19 '17 at 10:33
GAD3RGAD3R
28k1958114
Not port 11371 or 80 related behind firewall. seems to be rather related to DNS resolution when you start to google the net... ``` Executing: /tmp/apt-key-gpghome.imkAGGXMO8/gpg.1.sh --receive-keys --debug-all -vvv --keyserver hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 -> KEYSERVER --clear hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 <- OK gpg: DBG: chan_3 -> KS_GET -- 0x9C1384B1168FD423 gpg: DBG: chan_3 <- ERR 167772379 Server indicated a failure <Dirmngr>```
– Hvisage
Feb 1 '18 at 15:40
3
I get the same error using dirmngr 2.2.5, and addinghkp://and:80resolved the issue
– d3vid
Apr 11 '18 at 15:25
add a comment |
Behind a firewall you should use the port 80 instead of the default port 11371 :
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 9A2FD067A2E3EF7B
Sample output:
Executing: /tmp/apt-key-gpghome.mTGQWBR2AG/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv 9A2FD067A2E3EF7B
gpg: key 9A2FD067A2E3EF7B: "Launchpad PPA for GNS3" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
answered Oct 19 '17 at 10:33
GAD3RGAD3R
28k1958114
Not port 11371 or 80 related behind firewall. seems to be rather related to DNS resolution when you start to google the net... ``` Executing: /tmp/apt-key-gpghome.imkAGGXMO8/gpg.1.sh --receive-keys --debug-all -vvv --keyserver hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 -> KEYSERVER --clear hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 <- OK gpg: DBG: chan_3 -> KS_GET -- 0x9C1384B1168FD423 gpg: DBG: chan_3 <- ERR 167772379 Server indicated a failure <Dirmngr>```
– Hvisage
Feb 1 '18 at 15:40
3
I get the same error using dirmngr 2.2.5, and addinghkp://and:80resolved the issue
– d3vid
Apr 11 '18 at 15:25
add a comment |
Behind a firewall you should use the port 80 instead of the default port 11371 :
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 9A2FD067A2E3EF7B
Sample output:
Executing: /tmp/apt-key-gpghome.mTGQWBR2AG/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv 9A2FD067A2E3EF7B
gpg: key 9A2FD067A2E3EF7B: "Launchpad PPA for GNS3" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
answered Oct 19 '17 at 10:33
GAD3RGAD3R
28k1958114
Behind a firewall you should use the port 80 instead of the default port 11371 :
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 9A2FD067A2E3EF7B
Sample output:
Executing: /tmp/apt-key-gpghome.mTGQWBR2AG/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv 9A2FD067A2E3EF7B
gpg: key 9A2FD067A2E3EF7B: "Launchpad PPA for GNS3" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
answered Oct 19 '17 at 10:33
GAD3RGAD3R
28k1958114
answered Oct 19 '17 at 10:33
GAD3RGAD3R
28k1958114
answered Oct 19 '17 at 10:33
GAD3RGAD3R
28k1958114
answered Oct 19 '17 at 10:33
GAD3RGAD3R
28k1958114
28k1958114
Not port 11371 or 80 related behind firewall. seems to be rather related to DNS resolution when you start to google the net... ``` Executing: /tmp/apt-key-gpghome.imkAGGXMO8/gpg.1.sh --receive-keys --debug-all -vvv --keyserver hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 -> KEYSERVER --clear hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 <- OK gpg: DBG: chan_3 -> KS_GET -- 0x9C1384B1168FD423 gpg: DBG: chan_3 <- ERR 167772379 Server indicated a failure <Dirmngr>```
– Hvisage
Feb 1 '18 at 15:40
3
I get the same error using dirmngr 2.2.5, and addinghkp://and:80resolved the issue
– d3vid
Apr 11 '18 at 15:25
add a comment |
Not port 11371 or 80 related behind firewall. seems to be rather related to DNS resolution when you start to google the net... ``` Executing: /tmp/apt-key-gpghome.imkAGGXMO8/gpg.1.sh --receive-keys --debug-all -vvv --keyserver hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 -> KEYSERVER --clear hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 <- OK gpg: DBG: chan_3 -> KS_GET -- 0x9C1384B1168FD423 gpg: DBG: chan_3 <- ERR 167772379 Server indicated a failure <Dirmngr>```
– Hvisage
Feb 1 '18 at 15:40
3
I get the same error using dirmngr 2.2.5, and addinghkp://and:80resolved the issue
– d3vid
Apr 11 '18 at 15:25
Not port 11371 or 80 related behind firewall. seems to be rather related to DNS resolution when you start to google the net... ``` Executing: /tmp/apt-key-gpghome.imkAGGXMO8/gpg.1.sh --receive-keys --debug-all -vvv --keyserver hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 -> KEYSERVER --clear hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 <- OK gpg: DBG: chan_3 -> KS_GET -- 0x9C1384B1168FD423 gpg: DBG: chan_3 <- ERR 167772379 Server indicated a failure <Dirmngr>```
– Hvisage
Feb 1 '18 at 15:40
Not port 11371 or 80 related behind firewall. seems to be rather related to DNS resolution when you start to google the net... ``` Executing: /tmp/apt-key-gpghome.imkAGGXMO8/gpg.1.sh --receive-keys --debug-all -vvv --keyserver hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 -> KEYSERVER --clear hkp://sks1.cryptokeys.org.za:80 gpg: DBG: chan_3 <- OK gpg: DBG: chan_3 -> KS_GET -- 0x9C1384B1168FD423 gpg: DBG: chan_3 <- ERR 167772379 Server indicated a failure <Dirmngr>```
– Hvisage
Feb 1 '18 at 15:40
3
3
I get the same error using dirmngr 2.2.5, and adding
hkp:// and :80 resolved the issue– d3vid
Apr 11 '18 at 15:25
I get the same error using dirmngr 2.2.5, and adding
hkp:// and :80 resolved the issue– d3vid
Apr 11 '18 at 15:25
add a comment |
It has to do with DNS and what your DNS server does or does return for dirmngr ;(
It got introduce since 2.1.16 with dirmngr, and I've been looking for solution myself on 2.1.6 with Debian's default packages. ;(
The correct answer, is: Upgrade to version 2.2.x or later that fixed this problem first time.
answered Feb 1 '18 at 15:42
HvisageHvisage
30319
@StephenKitt it wasn't a different answer, I gave the reason why it broke, as the other answer was a totally inadequate answer with all the wrong reasons why it was failing after I've investigated the 2.1.6 versions on Debian. There wasn't any real other fix than to get the latest version from a testing/unstable branch to get passed this problem, which was not HTTP/firewall related, but the DNS issue
– Hvisage
Feb 4 '18 at 15:50
Sorry, the comment above is a canned comment which wasn’t quite appropriate. Your edited answer does indeed answer the question, thanks.
– Stephen Kitt
Feb 4 '18 at 16:02
add a comment |
It has to do with DNS and what your DNS server does or does return for dirmngr ;(
It got introduce since 2.1.16 with dirmngr, and I've been looking for solution myself on 2.1.6 with Debian's default packages. ;(
The correct answer, is: Upgrade to version 2.2.x or later that fixed this problem first time.
answered Feb 1 '18 at 15:42
HvisageHvisage
30319
@StephenKitt it wasn't a different answer, I gave the reason why it broke, as the other answer was a totally inadequate answer with all the wrong reasons why it was failing after I've investigated the 2.1.6 versions on Debian. There wasn't any real other fix than to get the latest version from a testing/unstable branch to get passed this problem, which was not HTTP/firewall related, but the DNS issue
– Hvisage
Feb 4 '18 at 15:50
Sorry, the comment above is a canned comment which wasn’t quite appropriate. Your edited answer does indeed answer the question, thanks.
– Stephen Kitt
Feb 4 '18 at 16:02
add a comment |
It has to do with DNS and what your DNS server does or does return for dirmngr ;(
It got introduce since 2.1.16 with dirmngr, and I've been looking for solution myself on 2.1.6 with Debian's default packages. ;(
The correct answer, is: Upgrade to version 2.2.x or later that fixed this problem first time.
answered Feb 1 '18 at 15:42
HvisageHvisage
30319
It has to do with DNS and what your DNS server does or does return for dirmngr ;(
It got introduce since 2.1.16 with dirmngr, and I've been looking for solution myself on 2.1.6 with Debian's default packages. ;(
The correct answer, is: Upgrade to version 2.2.x or later that fixed this problem first time.
answered Feb 1 '18 at 15:42
HvisageHvisage
30319
edited Feb 4 '18 at 15:47
answered Feb 1 '18 at 15:42
HvisageHvisage
30319
answered Feb 1 '18 at 15:42
HvisageHvisage
30319
answered Feb 1 '18 at 15:42
HvisageHvisage
30319
30319
@StephenKitt it wasn't a different answer, I gave the reason why it broke, as the other answer was a totally inadequate answer with all the wrong reasons why it was failing after I've investigated the 2.1.6 versions on Debian. There wasn't any real other fix than to get the latest version from a testing/unstable branch to get passed this problem, which was not HTTP/firewall related, but the DNS issue
– Hvisage
Feb 4 '18 at 15:50
Sorry, the comment above is a canned comment which wasn’t quite appropriate. Your edited answer does indeed answer the question, thanks.
– Stephen Kitt
Feb 4 '18 at 16:02
add a comment |
@StephenKitt it wasn't a different answer, I gave the reason why it broke, as the other answer was a totally inadequate answer with all the wrong reasons why it was failing after I've investigated the 2.1.6 versions on Debian. There wasn't any real other fix than to get the latest version from a testing/unstable branch to get passed this problem, which was not HTTP/firewall related, but the DNS issue
– Hvisage
Feb 4 '18 at 15:50
Sorry, the comment above is a canned comment which wasn’t quite appropriate. Your edited answer does indeed answer the question, thanks.
– Stephen Kitt
Feb 4 '18 at 16:02
@StephenKitt it wasn't a different answer, I gave the reason why it broke, as the other answer was a totally inadequate answer with all the wrong reasons why it was failing after I've investigated the 2.1.6 versions on Debian. There wasn't any real other fix than to get the latest version from a testing/unstable branch to get passed this problem, which was not HTTP/firewall related, but the DNS issue
– Hvisage
Feb 4 '18 at 15:50
@StephenKitt it wasn't a different answer, I gave the reason why it broke, as the other answer was a totally inadequate answer with all the wrong reasons why it was failing after I've investigated the 2.1.6 versions on Debian. There wasn't any real other fix than to get the latest version from a testing/unstable branch to get passed this problem, which was not HTTP/firewall related, but the DNS issue
– Hvisage
Feb 4 '18 at 15:50
Sorry, the comment above is a canned comment which wasn’t quite appropriate. Your edited answer does indeed answer the question, thanks.
– Stephen Kitt
Feb 4 '18 at 16:02
Sorry, the comment above is a canned comment which wasn’t quite appropriate. Your edited answer does indeed answer the question, thanks.
– Stephen Kitt
Feb 4 '18 at 16:02
add a comment |
Encountered the same issue on ubuntu 18.04, running dirmngr 2.2.4. I went with the option of checking my dns settings and added my local dns server 'nameserver 1.1.1.1' and google's 'nameserver 8.8.8.8'. Then it worked.
answered Nov 9 '18 at 10:19
user320161user320161
211
Specifying explicit DNS servers in my network config solved it for me. Gentoo, using NetworkManager.
– Pistos
Dec 28 '18 at 22:55
Also remember Quad9 (9.9.9.9) for helping to filter out malware/etc. in a privacy-advocacy manner ;)
– Hvisage
Dec 31 '18 at 10:14
add a comment |
Encountered the same issue on ubuntu 18.04, running dirmngr 2.2.4. I went with the option of checking my dns settings and added my local dns server 'nameserver 1.1.1.1' and google's 'nameserver 8.8.8.8'. Then it worked.
answered Nov 9 '18 at 10:19
user320161user320161
211
Specifying explicit DNS servers in my network config solved it for me. Gentoo, using NetworkManager.
– Pistos
Dec 28 '18 at 22:55
Also remember Quad9 (9.9.9.9) for helping to filter out malware/etc. in a privacy-advocacy manner ;)
– Hvisage
Dec 31 '18 at 10:14
add a comment |
Encountered the same issue on ubuntu 18.04, running dirmngr 2.2.4. I went with the option of checking my dns settings and added my local dns server 'nameserver 1.1.1.1' and google's 'nameserver 8.8.8.8'. Then it worked.
answered Nov 9 '18 at 10:19
user320161user320161
211
Encountered the same issue on ubuntu 18.04, running dirmngr 2.2.4. I went with the option of checking my dns settings and added my local dns server 'nameserver 1.1.1.1' and google's 'nameserver 8.8.8.8'. Then it worked.
answered Nov 9 '18 at 10:19
user320161user320161
211
answered Nov 9 '18 at 10:19
user320161user320161
211
answered Nov 9 '18 at 10:19
user320161user320161
211
answered Nov 9 '18 at 10:19
user320161user320161
211
211
Specifying explicit DNS servers in my network config solved it for me. Gentoo, using NetworkManager.
– Pistos
Dec 28 '18 at 22:55
Also remember Quad9 (9.9.9.9) for helping to filter out malware/etc. in a privacy-advocacy manner ;)
– Hvisage
Dec 31 '18 at 10:14
add a comment |
Specifying explicit DNS servers in my network config solved it for me. Gentoo, using NetworkManager.
– Pistos
Dec 28 '18 at 22:55
Also remember Quad9 (9.9.9.9) for helping to filter out malware/etc. in a privacy-advocacy manner ;)
– Hvisage
Dec 31 '18 at 10:14
Specifying explicit DNS servers in my network config solved it for me. Gentoo, using NetworkManager.
– Pistos
Dec 28 '18 at 22:55
Specifying explicit DNS servers in my network config solved it for me. Gentoo, using NetworkManager.
– Pistos
Dec 28 '18 at 22:55
Also remember Quad9 (9.9.9.9) for helping to filter out malware/etc. in a privacy-advocacy manner ;)
– Hvisage
Dec 31 '18 at 10:14
Also remember Quad9 (9.9.9.9) for helping to filter out malware/etc. in a privacy-advocacy manner ;)
– Hvisage
Dec 31 '18 at 10:14
add a comment |
Add 0x before key, so that it turns 0xF88F6D313016330404F710FC9A2FD067A2E3EF7B.
This plus GAD3R's answer solved it for me.
answered Feb 17 at 20:52
skilowattskilowatt
13613
add a comment |
Add 0x before key, so that it turns 0xF88F6D313016330404F710FC9A2FD067A2E3EF7B.
This plus GAD3R's answer solved it for me.
answered Feb 17 at 20:52
skilowattskilowatt
13613
add a comment |
Add 0x before key, so that it turns 0xF88F6D313016330404F710FC9A2FD067A2E3EF7B.
This plus GAD3R's answer solved it for me.
answered Feb 17 at 20:52
skilowattskilowatt
13613
Add 0x before key, so that it turns 0xF88F6D313016330404F710FC9A2FD067A2E3EF7B.
This plus GAD3R's answer solved it for me.
answered Feb 17 at 20:52
skilowattskilowatt
13613
answered Feb 17 at 20:52
skilowattskilowatt
13613
answered Feb 17 at 20:52
skilowattskilowatt
13613
answered Feb 17 at 20:52
skilowattskilowatt
13613
13613
add a comment |
add a comment |
This issue was really though for me, none of the proposed solutions worked for me until I found this post on reddit.
I just went and added this line to /etc/resolv.conf
nameserver 8.8.8.8 # Google dns
you can try any other dns and see which one works for you.
answered 2 days ago
Nafaa BouteferNafaa Boutefer
1213
add a comment |
This issue was really though for me, none of the proposed solutions worked for me until I found this post on reddit.
I just went and added this line to /etc/resolv.conf
nameserver 8.8.8.8 # Google dns
you can try any other dns and see which one works for you.
answered 2 days ago
Nafaa BouteferNafaa Boutefer
1213
add a comment |
This issue was really though for me, none of the proposed solutions worked for me until I found this post on reddit.
I just went and added this line to /etc/resolv.conf
nameserver 8.8.8.8 # Google dns
you can try any other dns and see which one works for you.
answered 2 days ago
Nafaa BouteferNafaa Boutefer
1213
This issue was really though for me, none of the proposed solutions worked for me until I found this post on reddit.
I just went and added this line to /etc/resolv.conf
nameserver 8.8.8.8 # Google dns
you can try any other dns and see which one works for you.
answered 2 days ago
Nafaa BouteferNafaa Boutefer
1213
answered 2 days ago
Nafaa BouteferNafaa Boutefer
1213
answered 2 days ago
Nafaa BouteferNafaa Boutefer
1213
answered 2 days ago
Nafaa BouteferNafaa Boutefer
1213
1213
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399027%2fgpg-keyserver-receive-failed-server-indicated-a-failure%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
as I've explained in my answer and comment to the downvotes, it's related to DNS and the way that dirmngr in version 2.1.6 did reverse DNS that have been removed in version 2.1.8 I recall, but 2.2.x I've installed from Debian testing/unstable (Debian 9 current as at writing this) also fixed this issue.
– Hvisage
Feb 4 '18 at 15:52