Dear gnupg developers, I keep getting a timeout for "gpg -v --keyserver hkp:// p80.pool.sks-keyservers.net:80 --recv-key 702353E0F7E48EDB" as follows:
tail -F /home/lpapp/dirmngr.log 2018-04-10 11:58:03 dirmngr[11735.6] DBG: chan_6 -> ERR 167805060 Connection timed out <Dirmngr> 2018-04-10 11:58:03 dirmngr[11735.6] DBG: chan_6 <- BYE 2018-04-10 11:58:03 dirmngr[11735.6] DBG: chan_6 -> OK closing connection 2018-04-10 11:58:03 dirmngr[11735.6] handler for fd 6 terminated 2018-04-10 12:08:04 dirmngr[11735.0] running scheduled tasks 2018-04-10 12:18:04 dirmngr[11735.0] running scheduled tasks 2018-04-10 12:28:04 dirmngr[11735.0] running scheduled tasks 2018-04-10 12:38:05 dirmngr[11735.0] running scheduled tasks 2018-04-10 12:47:30 dirmngr[11735.0] SIGTERM received - shutting down ... 2018-04-10 12:47:31 dirmngr[11735.0] dirmngr (GnuPG) 2.2.5 stopped 2018-04-10 12:48:15 dirmngr[14734.0] permanently loaded certificates: 136 2018-04-10 12:48:15 dirmngr[14734.0] runtime cached certificates: 0 2018-04-10 12:48:15 dirmngr[14734.0] trusted certificates: 136 (135,0,0,1) 2018-04-10 12:48:15 dirmngr[14734.6] handler for fd 6 started 2018-04-10 12:48:15 dirmngr[14734.6] DBG: chan_6 -> # Home: /home/lpapp/.gnupg 2018-04-10 12:48:15 dirmngr[14734.6] DBG: chan_6 -> # Config: /home/lpapp/.gnupg/dirmngr.conf 2018-04-10 12:48:15 dirmngr[14734.6] DBG: chan_6 -> OK Dirmngr 2.2.5 at your service 2018-04-10 12:48:15 dirmngr[14734.6] connection from process 14733 (1000:1000) 2018-04-10 12:48:15 dirmngr[14734.6] DBG: chan_6 <- GETINFO version 2018-04-10 12:48:15 dirmngr[14734.6] DBG: chan_6 -> D 2.2.5 2018-04-10 12:48:15 dirmngr[14734.6] DBG: chan_6 -> OK 2018-04-10 12:48:15 dirmngr[14734.6] DBG: chan_6 <- KEYSERVER --clear hkp:// p80.pool.sks-keyservers.net:80 2018-04-10 12:48:15 dirmngr[14734.6] DBG: chan_6 -> OK 2018-04-10 12:48:15 dirmngr[14734.6] DBG: chan_6 <- KS_GET -- 0x702353E0F7E48EDB 2018-04-10 12:48:15 dirmngr[14734.6] DBG: dns: libdns initialized 2018-04-10 12:48:25 dirmngr[14734.6] DBG: dns: resolve_dns_name( p80.pool.sks-keyservers.net): Success 2018-04-10 12:48:25 dirmngr[14734.6] DBG: dns: resolve_dns_addr(): Success 2018-04-10 12:48:25 dirmngr[14734.6] resolve_dns_addr for ' p80.pool.sks-keyservers.net': '212.51.156.40' 2018-04-10 12:48:25 dirmngr[14734.6] DBG: dns: resolve_dns_addr(): Success 2018-04-10 12:48:25 dirmngr[14734.6] resolve_dns_addr for ' p80.pool.sks-keyservers.net': '212.47.242.101' 2018-04-10 12:48:25 dirmngr[14734.6] DBG: dns: resolve_dns_addr(): Success 2018-04-10 12:48:25 dirmngr[14734.6] resolve_dns_addr for ' p80.pool.sks-keyservers.net': '192.167.206.241' 2018-04-10 12:48:25 dirmngr[14734.6] DBG: dns: resolve_dns_addr(): Success 2018-04-10 12:48:25 dirmngr[14734.6] resolve_dns_addr for ' p80.pool.sks-keyservers.net': '192.94.109.73' 2018-04-10 12:48:25 dirmngr[14734.6] DBG: dns: resolve_dns_addr(): Success 2018-04-10 12:48:25 dirmngr[14734.6] resolve_dns_addr for ' p80.pool.sks-keyservers.net': '185.95.216.79' 2018-04-10 12:48:25 dirmngr[14734.6] DBG: dns: resolve_dns_addr(): Success 2018-04-10 12:48:25 dirmngr[14734.6] resolve_dns_addr for ' p80.pool.sks-keyservers.net': '85.25.235.230' 2018-04-10 12:48:25 dirmngr[14734.6] DBG: dns: resolve_dns_addr(): Success 2018-04-10 12:48:25 dirmngr[14734.6] resolve_dns_addr for ' p80.pool.sks-keyservers.net': '80.108.201.53' 2018-04-10 12:48:25 dirmngr[14734.6] DBG: dns: resolve_dns_addr(): Success 2018-04-10 12:48:25 dirmngr[14734.6] resolve_dns_addr for ' p80.pool.sks-keyservers.net': '69.164.220.134' 2018-04-10 12:48:25 dirmngr[14734.6] DBG: dns: resolve_dns_addr(): Success 2018-04-10 12:48:25 dirmngr[14734.6] resolve_dns_addr for ' p80.pool.sks-keyservers.net': '24.134.103.65' 2018-04-10 12:48:25 dirmngr[14734.6] DBG: dns: resolve_dns_addr(): Success 2018-04-10 12:48:25 dirmngr[14734.6] resolve_dns_addr for ' p80.pool.sks-keyservers.net': '18.9.60.141' 2018-04-10 12:48:25 dirmngr[14734.6] number of system provided CAs: 153 2018-04-10 12:48:25 dirmngr[14734.6] DBG: http.c:connect_server: trying name='24.134.103.65' port=80 2018-04-10 12:48:25 dirmngr[14734.6] DBG: dns: resolve_dns_name(24.134.103.65): Success 2018-04-10 12:50:37 dirmngr[14734.6] can't connect to '24.134.103.65': Connection timed out 2018-04-10 12:50:37 dirmngr[14734.6] error connecting to ' http://24.134.103.65:80': Connection timed out 2018-04-10 12:50:37 dirmngr[14734.6] selecting a different host due to a timeout 2018-04-10 12:50:37 dirmngr[14734.6] DBG: http.c:connect_server: trying name='80.108.201.53' port=80 2018-04-10 12:50:37 dirmngr[14734.6] DBG: dns: resolve_dns_name(80.108.201.53): Success 2018-04-10 12:52:48 dirmngr[14734.6] can't connect to '80.108.201.53': Connection timed out 2018-04-10 12:52:48 dirmngr[14734.6] error connecting to ' http://80.108.201.53:80': Connection timed out 2018-04-10 12:52:48 dirmngr[14734.6] selecting a different host due to a timeout 2018-04-10 12:52:48 dirmngr[14734.6] DBG: http.c:connect_server: trying name='185.95.216.79' port=80 2018-04-10 12:52:48 dirmngr[14734.6] DBG: dns: resolve_dns_name(185.95.216.79): Success 2018-04-10 12:54:59 dirmngr[14734.6] can't connect to '185.95.216.79': Connection timed out 2018-04-10 12:54:59 dirmngr[14734.6] error connecting to ' http://185.95.216.79:80': Connection timed out 2018-04-10 12:54:59 dirmngr[14734.6] selecting a different host due to a timeout 2018-04-10 12:54:59 dirmngr[14734.6] DBG: http.c:connect_server: trying name='80.108.201.53' port=80 2018-04-10 12:54:59 dirmngr[14734.6] DBG: dns: resolve_dns_name(80.108.201.53): Success 2018-04-10 12:57:10 dirmngr[14734.6] can't connect to '80.108.201.53': Connection timed out 2018-04-10 12:57:10 dirmngr[14734.6] error connecting to ' http://80.108.201.53:80': Connection timed out 2018-04-10 12:57:10 dirmngr[14734.6] command 'KS_GET' failed: Connection timed out 2018-04-10 12:57:10 dirmngr[14734.6] DBG: chan_6 -> ERR 167805060 Connection timed out <Dirmngr> 2018-04-10 12:57:10 dirmngr[14734.6] DBG: chan_6 <- BYE 2018-04-10 12:57:10 dirmngr[14734.6] DBG: chan_6 -> OK closing connection 2018-04-10 12:57:10 dirmngr[14734.6] handler for fd 6 terminated However, when I try to run wget via those ip addresses, they seem to communicate ok as follows: wget -4 -v -O/dev/null http://24.134.103.65:80 --2018-04-10 12:49:10-- http://24.134.103.65/ ... Proxy request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘/dev/null’ /dev/null [ <=> ] 1.27K --.-KB/s in 0s 2018-04-10 12:49:11 (95.7 MB/s) - ‘/dev/null’ saved [1304] wget -4 -v -O/dev/null http://80.108.201.53:80 --2018-04-10 13:00:37-- http://80.108.201.53/ ... Proxy request sent, awaiting response... 200 OK Length: 17 [text/html] Saving to: ‘/dev/null’ /dev/null 100%[==========================================================================================================================================>] 17 --.-KB/s in 0s 2018-04-10 13:00:38 (1.98 MB/s) - ‘/dev/null’ saved [17/17] wget -4 -v -O/dev/null http://185.95.216.79:80 --2018-04-10 13:00:49-- http://185.95.216.79/ ... Proxy request sent, awaiting response... 200 OK Length: 5004 (4.9K) [text/html] Saving to: ‘/dev/null’ /dev/null 100%[==========================================================================================================================================>] 4.89K --.-KB/s in 0.001s 2018-04-10 13:00:49 (4.98 MB/s) - ‘/dev/null’ saved [5004/5004] Yes, I do have a corporate proxy, however, the environment variables are set up properly. Other applications work. Having said that, port 80 is used here for simple verification. I will provide some more information that you might find useful: dirmngr (GnuPG) 2.2.5 gpg (GnuPG) 2.2.5 cat ~/.gnupg/dirmngr.conf debug ipc,dns,network verbose log-file /home/lpapp/dirmngr.log disable-ipv6 connect-timeout 0 Could you please advise me how to get dirmngr working? Best regards, Laszlo Papp
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
