I usually get emails when a certificate is going to expire, for servers that I haven’t set the crontab to auto-renew for. Can we please get the the domains affected, Let’s Encrypt certainly knows which domains have used this, and it would be super helpful to help track down which server is using the…

Hi @scottconrad [image] scottconrad: Let’s Encrypt certainly knows which domains have used this your config files know the same. Check if your Certbot is new, so http is used check your config files if there is something like standalone or tls-sni

Ah, standalone. I’ll log into all the servers i guess and see. It would be nice if it told you the affected domain, i get expiration emails for domains, I don’t see why this couldn’t happen for this too.

I believe OP is talking about the email notification. If you are managing several domains, the email is not descriptive enough to point to the one that needs attention.

Indeed, the reply is not useful at all. I received the Action Required email, with no domain mentioned. So I did a run dry on the webserver that uses certbot, both websites report using http-01. So exactly what triggered the email??? Include the domain in the email, it’s not difficult to do!!

Agreed, just spent 30 minutes looking through logs on servers trying to work out who/what has triggered the email. For me it was anything setup standalone. eg certbot certonly --standalone and the renews are now certbot renew --preferred-challenges http-01 I’ll have to wait and see till a cert a…

Another vote for including either the domain or the IP address of the client that made the tls-sni-01 renewal request. With a handful of sites using letsencrypt, it’s easy enough to check configs. With hundreds or thousands across different environments with different setups, it’s much harder to fi…

Yes please identify the domain in the email, I have 25 domains using letsencrypt certs.

Please identify the offending domain names. Otherwise we’ll be wasting hours logging into every server to check.

Could not agree more that the email should include the affected domains. I manage a handful of servers with close to 100 sites in total, and it’s impractical for me to go searching through that many config files when the information could have been reported in a detailed manner at the start.

I don’t think there has been any proper validation done to insure the email provided is in fact the one responsible for the domain(s) in question. So that may pose legal problems (GDPR, etc.) when notifying unknown parties about maybe someone else’s domain and information. And doing so through yet…

ACME TLS-SNI-01 Email.. can we please include the domain

Help

jsha January 18, 2019, 7:46pm 14

We’re planning to do a second run with domain names included. Thanks for all the feedback!

Topic		Replies	Views
"Your Let’s Encrypt client used ACME TLS-SNI-01..." Which one? Feature Requests	16	6904	January 21, 2019
Suggestion Tell me the domain! - Action required: Let's Encrypt certificate renewal Feature Requests	1	1147	January 20, 2019
Domain not listed on TLS-SNI-01 notifications Help	1	1031	January 19, 2019
Delaying the TLS-SNI-01 validation deprecation? Feature Requests	5	1541	January 18, 2019
TLS-SNI-01 deprecation mail: which domain(s)? Help	8	1356	January 18, 2019

ACME TLS-SNI-01 Email.. can we please include the domain

Related topics