| SYSTEM INFORMATION | |
|---|---|
| OS type and version | Debian Linux 13 |
| Webmin version | 2.651 |
| Usermin version | 2.550 |
| Virtualmin version | 8.1.0 Professional |
| Theme version | 26.50.2 |
| Apache version | 2.4.68 |
| Package updates | All installed packages are up to date |
I’m really not wanting to be this needy guy with all the quirky problems, but it is what it is. I am running out of edge cases, though.
So I have three domains/top-level virtual servers right now on my new main Proliant server, each with subdomains/sub-servers. The initial virtual server was made without importing it directly from the old server; it’s the one that’s pestering LetsEncrypt. The other two domains were imported from my old Ubuntu server; they were a one-and-done with getting their certificates.
A few days ago, I tried to get this to stop by:
- using the VM interface to Remove SSL Certificate from Services,
- uncheck DNS features and
- uncheck SSL website for both the domain and subdomain.
I also deleted the SSL certificate with the interface where I could.
This might be irrelevant, but the imported domains didn’t have the certs stored in the VM default locations. Whenever I see that, I click the thing to move the certificates to the default location. On the old Proliant server, I solved some problems by moving them into the domains folder above the websites folder.
I waited for a little while and then turned the features back on.
(A red herring side note is that the subdomain didn’t have its BIND entries disappear, but the checkbox was unchecked. It wouldn’t let me check it because it was already there, but it stayed unchecked. I went to BIND and timidly removed its zone. After that, the checkbox worked as expected.)
With all features reactivated, I went to the Setup SSL Certificate and got new ones. It was immediately doing the unnecessary retry looping again.
I only found out about this about a week ago because I was using usermin again and had very full maliboxes from the failure notices. This could have been going on for a month or more.
My temporary solution was to alter the LetsEncrypt page’s settings to don’t auto renew and only update renewal. Right now, it appears not to be asking for a new cert.