I have been getting the following email for about 1-2 years. And I dont know how to get rid of it.
I tried contacting my former hoster and he refered me here. Further I have no Idea what or where I would have set whatever this is up. And therefore am neither able to turn it of or login anywhere since I dont know the username/password it mostlikely.
Please someone help me with this...
"Could not secure domains of Alexander Braun (login xelanua1) with Let`s Encrypt certificates. Please log in to Plesk and secure the domains listed below manually.
Securing of the following domains has failed:
<none>
The following domains have been secured without some of their Subject Alternative Names:
<none>
Could not renew Lets Encrypt certificates for Alexander Braun (login xelanua1). Please log in to Plesk and renew the certificates listed below manually. Renewal of the following Lets Encrypt certificates has failed:
Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/354479197392.
Details:
Type: urn:ietf:params:acme:error:dns
Status: 400
Detail: DNS problem: NXDOMAIN looking up A for xela-nuarb.at - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for xela-nuarb.at - check that a DNS record exists for this domain
The following Let`s Encrypt certificates have been renewed without some of their Subject Alternative Names:
What services did you subscribe to back then where you requested these certs? That is the place you need to resolve this. You have to disable the cert request on that service or system.
I can see why the cert request fails. That domain name is not currently registered.
Another option is to setup a rule in your mail system to auto-delete this reminder email. It would be best if you can disable the faulty request though so you don't waste Let's Encrypt resources.
Yes, it sounds like what happened is this user used to have that domain name, stopped hosting it and let it expire, but there's still something on the hoster's system attempting to renew a certificate for it. Since that of course won't work, that client is emailing the user the problem.
But I have no idea why the hoster would try to refer the user here, there's nothing we can do and that email isn't coming from Let's Encrypt's systems.
You may benefit from examining the email headers to determine its origin, but as others have already indicated, the email does not come from Let's Encrypt, which leaves us unable to assist.