"keyserver receive failed: Try again later" on macOS

[Walt Mankowski]

Hi C.J.,

Good to see you too.

I didn't run any tests since I installed the binary using homebrew. I suppose trying to install from source will be my next step.

I couldn't find any similar error reports on gnupg-users or gnupg-devel. It does make searching a bit tough, though, when I keep finding it referred to as "OSX" or "OS X" even though Apple changed the name to "macOS" back in 2016.

Walt

On Sat, Jun 14, 2025, at 9:32 PM, C.J. Collier wrote:
> Hey waltman!  Good seeing you here.  I've been working on a Perl project lately and have been thinking of the irc channel as I do so.
> 
> I thought I saw a similar error report recently for gpg on osx.  I haven't owned one since around '10, so I can't try first hand...
> 
> Did you try running the unit tests when you were building?  Is there even a make test?  I imagine a world where there is...
> 
> Cheers,
> 
> C.J.
> 
> 
> 
> On Sat, Jun 14, 2025, 14:58 Walt Mankowski via Gnupg-users <gnupg-users at gnupg.org> wrote:
>> __
>> Hi,
>> 
>> I recently got a new MacBook Air and I'm having trouble setting up gpg on it. I'm running macOS Sequoia 15.5 and the laptop has an Apple M4 chip.
>> 
>> 
>> I installed gpg 2.4.8 using homebrew and copied my .gnupg directory from my older Intel-based MacBook Pro. It can use existing keys just fine, but it fails to import any new keys.
>> 
>> 
>> Every time I try to import a key, it fails almost immediately with the error
>> 
>> 
>> gpg: keyserver receive failed: Try again later
>> 
>> I've tried a number of different keyservers and keep getting the same error. I have an Ubuntu box on the same network. I've run the same command on each box, for example:
>> 
>> gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 77D4D81DC47D68FA9E9E6A7C5DF19E2B67A7B584
>> 
>> This imports the key on Ubuntu but gives me the "Try again later" error on macOS.
>> 
>> I looked online for help but didn't find very much. I've set ~/.gnupg/dirmngr.conf to
>> 
>> log-file ~/.gnupg/dirmngr.log
>> debug-level guru
>> standard-resolver
>> 
>> and restarted dirmngr, but that had very little effect. In particular nothing gets logged to dirmngr.log.
>> 
>> Has anyone else seen this behavior before and know how to fix it? If not, I'd appreciate some advice on how to get it to log more diagnostic info, because I'm pretty much stuck now.
>> 
>> Thanks.
>> 
>> Walt
>> _______________________________________________
>> Gnupg-users mailing list
>> Gnupg-users at gnupg.org
>> https://lists.gnupg.org/mailman/listinfo/gnupg-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250615/7c1b73af/attachment.html>