also:
traceroute -I4 acme-v02.api.letsencrypt.org
traceroute -I6 acme-v02.api.letsencrypt.org
It didn't want the argument "l4". So I ran the following:
:~$ traceroute acme-v02.api.letsencrypt.org
traceroute to ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com (172.65.32.248), 64 hops max
1 192.168.1.1 0.247ms 0.004ms 0.134ms
And it stops there...
That statement conflicts with the attempts:
It should not have much of an effect on your problem, but we should disable IPv6 within the docker container - so that we can focus on only IPv4.
Certainly. You have a good point there. If IPv6 is somehow enabled in the Docker vm, it won't travel very far with that in this enviroment.
I shall have a look... Then I'll post an update when I've checked/disabled all IPv6 networking on the VM. Thank you very much ! 