Is this fixed in 2.650-1?
Iām also having trouble renewing my Letās Encrypt certificates after updating to Webmin 2.650.
Hereās the error again:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Renewing an existing certificate for xxx.yyyyyy.tld and 3 more domains
An unexpected error occurred:
AttributeError: can't set attribute
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
A fix, as has already been suggested here, would be great 
I think you should should create a new post, as it seem is maybe unrelated to the original post error. Things would get really confusing.
I got blocked by letsencrypt too:
There were too many requests of a given type :: too many certificates (5) already issued for this exact set of identifiers in the last 168h0m0s, retry after 2026-06-29 08:46:57
Reverted back to 2.641. For those asking I would stay away from upgrading to 2.65
You donāt need to install Webmin 2.650 for now. @Jamie and I are preparing a new 2.651 hotfix release to address this issue in particular.
I hope the hot fix lands soon 
For those of us that have installed 2.650 because it was an update what do we do?
downgrade?
Just install the patch mentioned in my first comment:
Just wanted to add something for anyone who applied the patch and is still getting renewal failure mails afterward ā donāt panic and donāt downgrade, it might not be the original bug anymore.
After applying Iliaās patch, my renewals started throwing this instead:
An unexpected error occurred:
AttributeError: can't set attribute
That looks scary, but itās actually a separate, known Certbot bug on Python 3.11 (Debian 12 ships Certbot 2.1.0 + Python 3.11.2) ā see certbot/certbot#9539. Certbot crashes while trying to display an ACME server error, so the actual error message gets swallowed and replaced by this generic AttributeError.
If you hit this, check the raw log instead of trusting the printed message:
bash
grep -B5 -A15 "rateLimited\|too many" /var/log/letsencrypt/letsencrypt.log | tail -100
In my case the real cause was sitting right there:
"detail": "too many certificates (5) already issued for this exact set of
identifiers in the last 168h0m0s, retry after ..."
Makes sense ā the original 2.650 bug had been retrying every hour for a while before I noticed, and apparently some of those retries actually succeeded in issuing real certs before failing on the path-parsing step, which ate into Letās Encryptās weekly ā5 certs per exact domain setā limit for the affected domain (something like xxx.yyyyyy.tld).
So if youāre still seeing failures after the patch: check the log for rateLimited before assuming the patch didnāt work. If it is a rate limit, itās domain-specific ā just disable auto-renew for the affected domain(s) in Virtualminās Letās Encrypt tab until the retry after timestamp passes, then re-enable.
Donāt forget to turn auto-renew back on afterward ā easy to disable it to stop the mail spam and then forget, which just sets you up for an expired cert down the line.
I did not apply the patch yet Iām waiting for official hot patch as stated by @Ilia
but thank you for the detailed report
I am having this issue in Virtalmin after the Webmin update. Both Web-based and DNS-based validation.
FYI , Webmin 2.651 is available for download now!
