gpg: keyserver refresh failed: No keyserver available

[Dmitry Alexandrov]

Jerry <jerry at seibercom.net> wrote:
> I have not been able to refresh the keys on my system. I have run the following command with the error as shown.
>
> 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

> I don't believe it is a firewall problem, since there is no entry in the firewall log to even suggest that gpg2 tried to access anything.

That is, your have not tried to check the connection on the same machine but with some other tool first?  Why?  FWIW, HKP is HTTP on port 11371.

> I have a Windows 10 machine that is using Kleopatra, on the same network, and it is working perfectly.

I do not remember for sure, but is not it, at least, preconfigured to use HKPS, i. e. HTTP/TLS on port 443, if not some proprietary keyserver instead of SKS pool?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 247 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20200706/451d8950/attachment.sig>