I created a certificate using the dns challenge, now I would like to renew the cert using the /.well-known path, so I tryied to switch to --preferred-challenges http and authenticator standalone but it is failing as it try to renew the cert with the dns challenge…is there a way to renew the certificate with the /.well-known path? the renew i done by a cronjob…
At the end I just created a new certificate with http challenge, I use the dns challenge when I need to move a certificate without have any downtime but then I’m not able to renew it with http challenge…Are you surer that the wildcard certificates need the DNS challenge? I can be wrong but if I remember right I used the http challenge fir a wildcard domain