No certificates after starting caddy

Hello,
I was using your caddy container abisoft/caddy 1.0.0 on a ubuntu server 16.04LTS for month till my server broke down. it took me some time to buy a new one. I set it up today with the old Caddyfile.
Logs are showing now these lines in a loop and I am without any idea after googling for hours

Activating privacy features... 2019/06/23 10:03:11 [INFO][cache:0xc0000b7090] Started certificate maintenance routine
2019/06/23 10:03:12 [INFO] acme: Registering account for mymail@yahoo.de
2019/06/23 10:03:27 registration error: Post https://acme-v02.api.letsencrypt.org/acme/new-acct: net/http: timeout awaiting response headers
exit status 1

this is my container command:

docker run -d\
    --name caddy \
    --restart=always \
    -v /docker/config/caddyneu/Caddyfile:/etc/Caddyfile \
    -v /docker/config/caddyneu/log:/etc/log \
    -v /docker/config/caddyneu/.caddy:/root/.caddy \
    -v /docker/data/caddy/www/:/srv \
    -p 80:80 \
    -p 443:443 \
    -p 2015:2015 \
    -e ACME_AGREE=true \
    abiosoft/caddy:php

and this is my Caddyfile config:
mydns.my-wan.de {
#wordpress
proxy / 192.168.100.10:8090 {
transparent
}
header / {
Referrer-Policy “no-referrer”
Strict-Transport-Security “max-age=31536000; includeSubdomains”
X-XSS-Protection “1; mode=block”
X-Content-Type-Options “nosniff”
X-Frame-Options “SAMEORIGIN”
Referrer-Policy “same-origin”
}
log caddy.log
errors caddy.errors
tls mymail@yahoo.de
gzip
}

############################################
mydns.my-wan.de/gc-bilder {
root /srv/gc-bilder
log /etc/log/gcbilder-access.log
errors /etc/log/gcbilder-errors.log
gzip
}

############################################
mydns.my-wan.de/geo {
root /srv/geo

tls off

gzip
}

############################################
mydns.my-wan.de/oh2 {
root /srv/oh2

tls off

gzip
}

############################################
ebooks.mydns.my-wan.de {
#COPS
proxy / 192.168.100.10:8030
tls mymail@yahoo.de
log /etc/log/ebooks-access.log
errors /etc/log/ebooks-errors.log
gzip

}

############################################
nextcloud.mydns.my-wan.de, newname.my-wan.de {
#nextcloud
proxy / 192.168.100.10:8020 {
transparent
websocket
}
tls mymail@yahoo.de
gzip

client support (e.g. os x calendar / contacts)

redir /.well-known/carddav /remote.php/carddav 301
redir /.well-known/caldav /remote.php/caldav 301
header / {
Referrer-Policy “no-referrer”
Strict-Transport-Security “max-age=31536000; includeSubdomains”
X-XSS-Protection “1; mode=block”
X-Content-Type-Options “nosniff”
X-Frame-Options “SAMEORIGIN”
Referrer-Policy “same-origin”
}
log /etc/log/nextcloud-access.log
errors /etc/log/nextcloud-errors.log
}

############################################
sync.mydns.my-wan.de {
#Syncthing
proxy / 192.168.100.10:8384 {
transparent
}

errors /etc/log/sync-errors.log
gzip
tls mymail@yahoo.de
timeouts {
read none
write none
header none
}
}

############################################
syncserver.mydns.my-wan.de {
#firefox sync server
proxy / http://192.168.100.10:5000/token/1.0/sync/1.5 {
transparent
}
}

############################################
bw.mydns.my-wan.de {
#bitwarden
proxy / 192.168.100.10:8040 {
transparent
insecure_skip_verify
}
proxy /notifications/hub 192.168.100.10:3012 {
websocket
}
proxy /notifications/hub/negotiate 192.168.100.10:8040 {
transparent
}
errors /etc/log/bw-errors.log
gzip
tls mymail@yahoo.de
}

No path or an errant firewall would result the whole connection timing out, so given that you presumably got the request headers out and then fail at receiving, this looks more like network instability to me.