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

Follow

Comments

8 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....

    0
    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

Please sign in to leave a comment.

Have more questions? Submit a request