On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Unable to install a Let's Encrypt certificate: Order's status ("pending") is not acceptable for finalization or No order for ID

Follow

Comments

16 comments

  • Avatar
    Tom Heuts (Edited )

    This bug is really annoying.
    I've got several certificates that are (about to) expire.
    Running CentOS 7 and resolution doesn't work.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Tom,

    Usually, this workaround works without issues.

    If possible, consider creating a support request to us or to our partner, depending on where the license was purchased to check the issue deeper:

    https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-

     

    0
    Comment actions Permalink
  • Avatar
    Tom Heuts (Edited )

    Hi Ivan Postnikov, thank you for your response!

    Unfortunately Plesk is purchased via a partner (TransIP).

    They can't help me either...

     

    I solved it now by removing and reinstalling Let's Encrypt AND SSL It!

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Tom Heuts

    Glad to hear it's solved.

    Also, there's a way to contact Plesk Support directly with licenses purchased from our partners: https://support.plesk.com/hc/en-us/articles/213953025-How-to-get-support-directly-from-Plesk-

    0
    Comment actions Permalink
  • Avatar
    Eva Tarín

    ¿Como se sabe que fichero json es el que tiene problemas? me salen muchos....

    1
    Comment actions Permalink
  • Avatar
    Shawn K. Hall

    Deleting the existing JSON request didn't work for me, and being concerned about uninstalling the extension I opted to simply disable and reenable the LetsEncrypt extension. Tried reissuing a troublesome certificate afterwards and it worked again.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Shawn K. Hall,

    Thank you for sharing, it may be useful for other Pleskians.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Eva Tarín,

    The workaround is for domains one by one.

    The workaround is to be applied for each domain with such an error.

    The search for .json is described in "Resolution" section

     

    0
    Comment actions Permalink
  • Avatar
    Aitor Forner Cotillas

    Hola Eva Tarín

    igual ya lo has resuelto, pero por si acaso, con el comando

    # egrep -Ril [example.com] /usr/local/psa/var/modules/letsencrypt/orders

    donde [example.com] debe ser tu dominio, apuntará a un .json.

    Después para borrarlo copia la línea que te dió como resultado y ejecuta el comando:

    # rm [pegas la línea con el .json]

    0
    Comment actions Permalink
  • Avatar
    Haessler

    I used the workaround for Linux for the first domain, deleted the json file, assigned a new lets encrypt certificate und PUH !!! it worked.

    Now there are a dozen other domains where the certificate will end during the next weeks. Oha.

    Ulrike 

    0
    Comment actions Permalink
  • Avatar
    Yulia Plokhotnikova

    Hi @Haessler,

    It's not expected that workaround is needed here if you are using the latest Plesk version/update as bug is supposed to be fixed already. So just make sure your server is up to date. If yes, but still issue is not solved on your side and you have to apply the workaround, it worth reporting to our support team.

    Consider submitting a support request to Plesk directly or to a reseller, depending on where the license was purchased.
    0
    Comment actions Permalink
  • Avatar
    Haessler

    Hallo Yulia, 

    thank you for your answer. The error raised on the latest version of Plesk (Version 18.0.28 last month), but the domain was migrated from another Server, I guess this was the reason

    0
    Comment actions Permalink
  • Avatar
    Jason Koning

    the workaround (removing the json file) fixed the issue for me

    0
    Comment actions Permalink
  • Avatar
    Bob Benson

    Today I received an email from our Plesk server (Version 18.0.31 Update #2) with this error.  The Let's Encrypt extension version is "2.12.3-676".  I see there is an extension update released today (Dec 8 2020).  I will install that and see if the error reoccurs.

     

    0
    Comment actions Permalink
  • Avatar
    Andrey Bau

    Help please

    Error: Could not issue a Let's Encrypt SSL/TLS certificate for andrey-baugu.ch. Authorization for the domain failed.
    Details

    Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/25632859160.
    Details:
    Type: urn:ietf:params:acme:error:dns
    Status: 400
    Detail: No valid IP addresses found for andrey-baugu.ch
    0
    Comment actions Permalink
  • Avatar
    Shawn K. Hall

    Andrey Bau the DNS for your domain is not resolving. If DNS does not resolve then NO provider can generate a secure certificate for you. Fix your DNS and then the certificate generation will work.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request