Always getting fallback-*.perm files!

[testit]

Hallo Jürgen,

obviously I have the same problem like another poster here:

Connectivity issues to acme-v02.api.letsencrypt.org

W…

Because

traceroute acme-v02.api.letsencrypt.org

prints out following:

traceroute acme-v02.api.letsencrypt.org
traceroute to ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com (172.65.32.248), 64 hops max, 40 byte packets
1 static.161.89.9.5.clients.your-server.de (5.9.89.161) 1.478 ms 0.625 ms 0.777 ms
2 * core23.fsn1.hetzner.com (213.239.245.109) 2.249 ms
core24.fsn1.hetzner.com (213.239.245.149) 2.412 ms
3 core0.fra.hetzner.com (213.239.252.41) 11.276 ms
core0.fra.hetzner.com (213.239.252.37) 31.772 ms 9.580 ms
4 core9.fra.hetzner.com (213.239.252.18) 33.877 ms 24.049 ms 10.778 ms
5 162.158.84.254 (162.158.84.254) 6.324 ms 6.580 ms 9.497 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * *
...

In httpd-error-log I find the same detailed information like in the posted output od mod_md (detail:):

[Mon Apr 13 19:38:56.803885 2020] [md:error] [pid 5899] (20014)Internal error (specific information not available): AH10056: processing www.asp-services.de: Unsuccessful in contacting ACME server at https://acme-v02.api.letsencrypt.org/directory. If this problem persists, please check your network connectivity from your Apache server to the ACME server. Also, older servers might have trouble verifying the certificates of the ACME server. You can check if you are able to contact it manually via the curl command. Sometimes, the ACME server might be down for maintenance, so failing to contact it is not an immediate problem. Apache will continue retrying this.

Viele Grüße
testit