With the latest windows VM using deSEC with LetsEncrypt I keep getting these e-mails:
Subject:
Cron root@domainname /var/scripts/letsencryptrenew.sh
Body:
###################################
With the latest windows VM using deSEC with LetsEncrypt I keep getting these e-mails:
Subject:
Body:
###################################
Anybody know? Iād hate for the certificate to expire if this is supposed to be a warning of some kind.
I donāt understand the question as itās to little information. Sorry.
Are you getting an email which looks like that just because you enabled deSEC? Impossible since deSEC isnāt setup to send emails at all - script wise.
To be honest, Iām not sure why Iām getting these e-mails. I donāt know if they are a warning or no problem. I checked my deSEC account to see if my server is ātouchingā the account, and itās been over a month.
I donāt know what or why these e-mails are being sent (What I posted is the exact e-mail I get (with the exception of the domain name).
I donāt know how the system is supposed to reach out and touch the my deSEC account or LetsEncypt. Perhaps the system only reaches out when there is an IP change?
I did not received these e-mails using the older VM. I believe with the same setup options. (E-Mail Notification Enabled)
Thanks for all your help.
Just check in the browser the details of your certificate. If configured properly, they should be renewed automatically once their expiration date is less than 30 days.
For such security-related stuff, itās nice to have mails but some just are fake. So itās better you check that by yourself independently (not by clicking any links etc.).
You shouldnāt worry. Certificates are updated automatically in the background.
It would still be interesting to know what triggers them thoughā¦ I donāt recognize it, and Iām the founder of the VM. I know it inside out so to speak.
Maybe itās a new thing in the Certbot Snap? I run it myself though and Iāve never seen such an email before.
Ok, thanks guys. Iāll just ignore the e-mails, as I donāt know enough to figure out the āwhyāsā, and to shut them offā¦
The only thing similar I found was this:
But it shouldnāt trigger an email.
That has to be it. That hash string is Exactly what is being sent in the body.
The following PR should fix it in the future.
Awesome, Thank you.
Thanks for reporting!