How does nextcloud AIO generate ssl certificate and why is it IP based??

[eviscerat]

I just had a power outage that restarted both my server and router. Naturally a new public IP was assigned to the router by the provider. I have a script that automatically changes the A records in my DNS provider for the domain.

However when I accessed my nextcloud instance it wasn't working. So I restarted all containers from nextcloud AIO and looked inside the logs.

[06-May-2023 09:02:20] NOTICE: fpm is running, pid 102
[06-May-2023 09:02:20] NOTICE: ready to handle connections
{"level":"error","ts":1683405626.8094974,"logger":"http.acme_client","msg":"challenge failed","identifier":"80-112-123-123.provider.net","challenge_type":"http-01","problem":{"type":"urn:ietf:params:acme:error:dns","title":"","detail":"DNS problem: NXDOMAIN looking up A for 80-112-123-123.provider.net - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for 80-112-123-123.provider.net - check that a DNS record exists for this domain","instance":"","subproblems":[]}}
{"level":"error","ts":1683405626.8134615,"logger":"http.acme_client","msg":"validating authorization","identifier":"80-112-123-123.provider.net","problem":{"type":"urn:ietf:params:acme:error:dns","title":"","detail":"DNS problem: NXDOMAIN looking up A for 80-112-123-123.provider.net - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for 80-112-123-123.provider.net - check that a DNS record exists for this domain","instance":"","subproblems":[]},"order":"https://acme-v02.api.letsencrypt.org/acme/order/1096350177/180574124027","attempt":1,"max_attempts":3}

I noticed that the instance is trying to generate a certificate for the old public ip address (I anonimized the ip and the internet provider). Why does it matter what public ip I have for a domain certificate?

How does it work and what should I do to have nextcloud work regardless of the underlying public ip of the domain?

[eviscerat]

Nevermind, after the ip change in A record of dns provider propagated, the nextcloud instance recovered itself.