Tim:
> No, I sanitised it. I've found, in the past, that exposing
real
> addresses gets it abused (extra spam and hacking attempts), since such
> people harvest mailing lists and newsgroups.
Samuel Sieb:
Then that was a very misleading post... I assumed that it was some
sort
of check that your DNS was functioning properly. But if it's actually
the domain you're trying to create the certificate for, then that makes
a very different situation. If you're making up names, you should at
least say that's what you're doing.
Sorry, forgot to mention it at the time.
To explain the situation again, properly:
I have a real domain name, cpanel's auto-ssl renewal system was
using let's encrypt for the certificates, I stripped my domain name out
of my posting. I don't know how the hosting service actually handles
it, there's no configuration files I can actually see, I only get to
see the cpanel interface. The site works (has for many years), the
certificates work (has for many years), they get renewed.
Recently my hosting service either changed to using let's encrypt - or
changed how they interact with them.
I was wondering if anyone had seen similar bogus error messages that
something might have been wrong, or maybe not, but nothing is wrong
afterwards. Patrick, also using let's encrypt, said he hadn't. So I'm
assuming it's some peculiarity with how my hosting service is doing
things. Rather than let's encrypt, itself.
--
uname -rsvp
Linux 3.10.0-1160.90.1.el7.x86_64 #1 SMP Thu May 4 15:21:22 UTC 2023 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.