Webmail TLS certficate issue after v-add-letsencrypt-host

I was using webmail for the main domain of HestiaCP until i chose to add Let’s Encrypt certificate to the host to get the GUI over HTTPS.
Now webmail.maindomain.com is giving me certificate error.

How can i sort it out?


Via mail domain you are able to generate a valid ssl for it.

That’s been failing from i installed the panel with_
Error: Let’s Encrypt validation status 400 (mail.maindomain.com). Details: Unable to update challenge :: authorization must be pending

Both webmail and mail.maindomain.com has correct A record to the panel so i wonder what i might be missing?

Please use the search function for LE400, you need to check why it fails, there are a lot of threads handling it and also a section in our docs.

==[Step 5]==

  • status: 400
  • nonce:
  • validation:
  • details: Unable to update challenge :: authorization must be pending
  • answer: HTTP/2 400
    server: nginx
    date: Sun, 14 Aug 2022 13:06:26 GMT
    content-type: application/problem+json
    content-length: 144
    boulder-requester: 642607966
    cache-control: public, max-age=0, no-cache
    link: https://acme-v02.api.letsencrypt.org/directory;rel=“index”

“type”: “urn:ietf:params:acme:error:malformed”,
“detail”: “Unable to update challenge :: authorization must be pending”,
“status”: 400

==[Abort Step 5]==
=> Wrong status

Sorted out.
The problem was that there was a web domain under admin for mail.maindomain.com which is HestiaCP was installed under.
I removed that and it solved the LE issue and now webmail.maindomain.com works with TLS.


1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.