Ping acme-v02.api.letsencrypt.org Unavailable from server

Help
1

ping acme-v02.api.letsencrypt.org

PING ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com (172.65.32.248) 56(84) bytes of data.
^C
— ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com ping statistics —
151 packets transmitted, 0 received, 100% packet loss, time 149999ms

DOKUWIKI-01P (0.0.0.0) Mon Oct 14 17:00:27 2019
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev

  1. 10.126.240.253 0.0% 9 0.2 0.2 0.1 0.3 0.0
  2. 10.15.0.1 0.0% 9 1.2 0.8 0.6 1.2 0.0
    185.173.3.3
  3. 185.173.3.3 0.0% 9 0.7 0.8 0.7 1.4 0.0
  4. 10.45.9.17 0.0% 9 1.2 11.5 1.0 34.9 13.9
  5. 10.45.2.5 0.0% 8 28.9 12.1 1.2 28.9 10.3
  6. 95.167.231.134 0.0% 8 5.3 11.6 5.3 19.3 4.2
  7. 188.254.26.51 0.0% 8 25.9 26.0 25.8 27.1 0.0
  8. ???

~# traceroute acme-v02.api.letsencrypt.org
traceroute to acme-v02.api.letsencrypt.org (172.65.32.248), 30 hops max, 60 byte packets
1 gateway (10.126.240.253) 0.100 ms 0.084 ms 0.066 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * *^C

From another server everything is ok

2

Hi @intervisionlord

then ask your hoster. Looks like your server can't talk with Letsencrypt.

Then 10.* is a private address, not a public ip.

3

However, this could also be a problem with Let’s Encrypt’s CDN.

And even some colocated servers have NAT with a private IP address (with port forwarding from a public address).

@intervisionlord, should we assume you also can’t make TCP connections to this service with a Let’s Encrypt client or with curl? Is there anything about this hosting environment that intends to restrict outbound connections in any way?