Autorenewal of SSL certificates, through Let's Encrypt, stopped working for a web site operating under aaPanel.
According to one source, a recent software change in aaPanel leads to a problem, that requires old certificates to be removed, and new ones requested.
I removed SSL from the web site, and then requested a new certificate, through the ACME client, from Let's Encrypt.
I am using DNS verification, with manual record entry, and automatic combination of "pan-domain names".
I updated records on the name server three days ago. Now, every host, including the local host running aaPanel, is now receiving the new value, in answers to queries, for the subdomain _acme-challenge.
Yet, attempting to request a new certificate in aaPanel, invoking the ACME client, the following messages is displayed:
"A wrong TXT record was found on ['_acme-challenge.<mydomain>']: ['<old_challenge>'], please check whether the TXT resolution is correct, if it is applied by DNSAPI, please try again in 10 minutes! "
The message is embedded into a larger JSON-encoded data structure. The structure has fields both for the new and old values, of the challenge string, and it shows the old value as still being retrieved, from the queries to the name server, even though actual queries are now answered always with the new value.
Again, the updates in the records on the name server were completed three days ago, and all hosts, even the one running aaPanel, is retrieving the new value, for example, when tested with dig.
How can aaPanel be forced to recognize the new, updated value, already definitely propagated across the name servers?
