GPG Keychain: unable to access keyserver
As noted above. Text is:
Details:
Search keys failed! (Server indicated a failure)
Code = 219
Error text:
gpg: error searching keyserver: Server indicated a failure
gpg: keyserver search failed: Server indicated a failure
Also, when I go into Settings to select a key server, it tells me all of them are unreachable.
Expected
to be able to connect to the key server!
macOS 10.14.5 18F203
GPG Suite 2018.5 2368 (6f26711)
GPG Mail 3.0.1 1330 (807c323e) 30 trial days remaining
GPG Keychain 1.4.6 1514 (560b5a9)
GPG Services 1.11.6 1056 (ad0c960)
MacGPG 2.2.10 921 (b487092)
GPG Suite Preferences 2.1.4 1077 (ad934a9)
Libmacgpg 0.8.7 895 (78f424a)
pinentry 1.1.0 10 (1ff8803)
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Steve on 22 Jul, 2019 01:45 PM
Hi Stephen,
welcome to the GPGTools support platform. Sorry you are having problems using GPG Suite.
Unfortunately there are a variety of reasons why a key search can fail.
Is there any chance that you are using Little Snitch or any other firewall on your Mac? If so, please temporarily disable that software and repeat your search.
Can you let us know which key server address you see in GPG Keychain > Preferences > Key Server. What happens if you switch to the other default key servers in the list?
In an upcoming release we will switch the default key server to keys.openpgp.org. Our nightly build includes MacGPG 2.2.17 and adds support for the new key server.
We have two KB articles covering this:
All the best,
Steve
Disclaimer: This is a development version which has not been thoroughly tested yet - bugs or crashes are to be expected. Thanks for helping us test.
2 Posted by gpg_dude on 26 Aug, 2019 05:43 PM
I'm able to reproduce this issue on a fresh install of GPGTools 2019.1 & 2018.5 (it's OK in 2506n, but stops working sometime before 2539).
It seems like the newer version of the GPGTools.Org suite fails to assume tcp port numbers for hkp as 11371 & hkps as 443 if a DNS SRV query to determine the published port number fails. Setting the port number manually in the keyserver seems to work around this:
NO GOOD: hkps://hkps.pool.sks-keyservers.net
GOOD: hkps://hkps.pool.sks-keyservers.net:443
NO GOOD: hkp://pool.sks-keyservers.net
GOOD: hkp://pool.sks-keyservers.net:11371
Support Staff 3 Posted by Steve on 26 Aug, 2019 06:27 PM
@gpg_dude Can you please try to reproduce the problem using the current nightly (2541n).
Both
hkps://hkps.pool.sks-keyservers.net
hkp://pool.sks-keyservers.net
worked as expected in a test.
4 Posted by gpg_dude on 26 Aug, 2019 06:50 PM
This comment was split into a new private discussion: GPG Keychain: unable to access keyserver
I get the same behavior with 2541n - here is the exact message reported by the GUI:
"The key server you have entered is not working. Please check the key server address. It should look something like this hkp://some.key.server.org
The key server could also be offline. In that case, please use another key server"
Support Staff 5 Posted by Steve on 02 Sep, 2019 11:45 AM
Hi gpg_dude,
I have split your case into a separate discussion as I think you are seeing a different problem from the original poster. Let's continue your case here: https://gpgtools.tenderapp.com/discussions/problems/101674-gpg-keyc...
@Stephen: Are you still seeing your problem after updating to GPG Suite 2019.1 and macOS 10.14.6 including the Supplement Updates from Apple?
All the best,
Steve
6 Posted by Stephen Rosenfe... on 03 Sep, 2019 02:30 PM
On September 2, 2019 at 7:45:57 AM, Steve ([email blocked]) wrote:
Support Staff 7 Posted by Steve on 04 Sep, 2019 02:48 PM
Glad this is solved for you. I'm closing this discussion. Should you need further assistance or have questions you can re-open this discussion here or open a new one any time.
Best,
Steve
Steve closed this discussion on 04 Sep, 2019 02:48 PM.