Das Thema hat sich leider noch nicht “allein” erledigt.
Ich weiß zwar nicht wie ich es geschafft habe das es einmal lief aber
da heute Stromausfall war musste ich feststellen, dass nach einem Reboot der Proxmox VM immer der Port 8090 (AIO Interface) nicht da ist.
Zum Glück hatte ich noch ein Snapshot vergessen zu löschen.
Wenn ich diesen zurückspiele, wird die VM ja im Betrieb fortgesetzt und da ist der Port erreichbar.
Dann bin ich auf Ursachenforschung gegangen:
root@docker:~# docker logs nextcloud-aio-apache
Schnipp
{"level":"error","ts":1758047135.25133,"logger":"tls","msg":"failed updating renewal info from ACME CA","identifiers":["domain.de"],"cert_hash":"653e7ddd7313a0780ae426b7e233fce6b90a342fa9e960f1b89e7395558db236","ari_unique_id":"nytfzzwhT50Et-0rLMTGcIvS1w0.BYmx04-RIdVPN47deA5Eq3Y6","cert_expiry":1763277215,"issuer":"acme-v02.api.letsencrypt.org-directory","error":"provisioning client: performing request: Get \"https://acme-v02.api.letsencrypt.org/directory\": dial tcp: lookup acme-v02.api.letsencrypt.org on 127.0.0.11:53: server misbehaving"}
{"level":"error","ts":1758047135.251726,"logger":"tls","msg":"updating ARI upon managing","error":"could not fully update ACME renewal info: either no issuer supporting ARI is configured for certificate, or all such failed (make sure the ACME CA that issued the certificate is configured)"}
{"level":"error","ts":1758047735.2351687,"logger":"tls.cache.maintenance","msg":"failed updating renewal info from ACME CA","identifiers":["domain.de"],"cert_hash":"653e7ddd7313a0780ae426b7e233fce6b90a342fa9e960f1b89e7395558db236","ari_unique_id":"nytfzzwhT50Et-0rLMTGcIvS1w0.BYmx04-RIdVPN47deA5Eq3Y6","cert_expiry":1763277215,"issuer":"acme-v02.api.letsencrypt.org-directory","error":"provisioning client: performing request: Get \"https://acme-v02.api.letsencrypt.org/directory\": dial tcp: lookup acme-v02.api.letsencrypt.org on 127.0.0.11:53: server misbehaving"}
{"level":"error","ts":1758047735.23545,"logger":"tls.cache.maintenance","msg":"updating ARI","error":"could not fully update ACME renewal info: either no issuer supporting ARI is configured for certificate, or all such failed (make sure the ACME CA that issued the certificate is configured)"}
{"level":"error","ts":1758048335.2284513,"logger":"tls.cache.maintenance","msg":"failed updating renewal info from ACME CA","identifiers":["domain.de"],"cert_hash":"653e7ddd7313a0780ae426b7e233fce6b90a342fa9e960f1b89e7395558db236","ari_unique_id":"nytfzzwhT50Et-0rLMTGcIvS1w0.BYmx04-RIdVPN47deA5Eq3Y6","cert_expiry":1763277215,"issuer":"acme-v02.api.letsencrypt.org-directory","error":"provisioning client: performing request: Get \"https://acme-v02.api.letsencrypt.org/directory\": dial tcp: lookup acme-v02.api.letsencrypt.org on 127.0.0.11:53: server misbehaving"}
{"level":"error","ts":1758048335.2287273,"logger":"tls.cache.maintenance","msg":"updating ARI","error":"could not fully update ACME renewal info: either no issuer supporting ARI is configured for certificate, or all such failed (make sure the ACME CA that issued the certificate is configured)"}
{"level":"error","ts":1758048935.245399,"logger":"tls.cache.maintenance","msg":"failed updating renewal info from ACME CA","identifiers":["domain.de"],"cert_hash":"653e7ddd7313a0780ae426b7e233fce6b90a342fa9e960f1b89e7395558db236","ari_unique_id":"nytfzzwhT50Et-0rLMTGcIvS1w0.BYmx04-RIdVPN47deA5Eq3Y6","cert_expiry":1763277215,"issuer":"acme-v02.api.letsencrypt.org-directory","error":"provisioning client: performing request: Get \"https://acme-v02.api.letsencrypt.org/directory\": dial tcp: lookup acme-v02.api.letsencrypt.org on 127.0.0.11:53: server misbehaving"}
{"level":"error","ts":1758048935.2456105,"logger":"tls.cache.maintenance","msg":"updating ARI","error":"could not fully update ACME renewal info: either no issuer supporting ARI is configured for certificate, or all such failed (make sure the ACME CA that issued the certificate is configured)"}
Aha, es liegt also am Zertifikat.
Und da bin ich wieder an einer Stelle wo ich Hilfe brauchen könnte.
Wie erneuere ich das Zertifikat bzw. warum erneuert sich das nicht selbst???
PS: Die domain ist im Log geändert.
VG