gpg: keyserver refresh failed: No keyserver available

[Werner Koch]

On Mon,  6 Jul 2020 09:11, Jerry said:

> gpg2 --refresh-keys
> gpg: enabled debug flags: memstat
> gpg: refreshing 168 keys from hkp://pool.sks-keyservers.net
> gpg: keyserver refresh failed: No keyserver available

Please add in the error case always the --verbose option which may yield
more diagnostics.

For network related problems, it is best to enable logging for dirmngr:
Put

--8<---------------cut here---------------start------------->8---
log-file /foo/bar/dirmngr.log
verbose
debug ipc
--8<---------------cut here---------------end--------------->8---

into ~/.gnupg/dirmngr.conf and

  gpgconf --kill dirmngr

(see watchgnupg(1) for a consolidated debug output of all components)
If the output does not show anything helpful, add more debug options:

  debug ipc,network,dns

will give you a trace of all requests to dirmngr (ipc), Network
conenctions and data (network), and DNS lookups (dns).

  dirmngr --debug help

gives a list of such debug options.

Sometimes it is required to either add the option
"disable-ipv4" or "disable-ipv6" to dirmngr.conf.  After changing any
dirmngr option better restart dimngr as described above.


Salam-Shalom,

   Werner


-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20200707/060ec04c/attachment.sig>