# Invalid response from https://acme-v02.api.letsencrypt.org
**URL:** https://community.letsencrypt.org/t/invalid-response-from-https-acme-v02-api-letsencrypt-org/106378
**Category:** Help
**Created:** [November 16, 2019, 12:24am UTC](https://community.letsencrypt.org/t/invalid-response-from-https-acme-v02-api-letsencrypt-org/106378 "2019-11-16T00:24:06Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@THZ](https://community.letsencrypt.org/u/THZ)
#### Post date: [November 16, 2019, 12:24am UTC](https://community.letsencrypt.org/t/invalid-response-from-https-acme-v02-api-letsencrypt-org/106378/1 "2019-11-16T00:24:07Z")
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [https://crt.sh/?q=example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: CBDHemp.news
I believe the issue is that there was an email address typo in my first lets encrypt attempt. The error below is subsequent attempts for a new lets encrypt. I have successfully used lets encrypt for the next two domains. I believe I need to back out and start again from scratch.
I ran this command: Lets Encrypt Entry Level Encryption from Media Temple Plesk Account.
It produced this output:Invalid response from [https://acme-v02.api.letsencrypt.org/acme/order/69915495/1333307709](https://acme-v02.api.letsencrypt.org/acme/order/69915495/1333307709).
Details:
Type: urn:ietf:params:acme:error:malformed
Status: 404
Detail: No order for ID 1333307709
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is: Media Temple DEV Server
I can login to a root shell on my machine (yes or no, or I don’t know): YES
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): PLESK
The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you’re using Certbot):
---
### Author:  [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)
#### Post date: [November 16, 2019, 1:28am UTC](https://community.letsencrypt.org/t/invalid-response-from-https-acme-v02-api-letsencrypt-org/106378/2 "2019-11-16T01:28:24Z")
Hi @THZ
> [@THZ](#):
>
> Detail: No order for ID
simple answer: That's a Plesk bug.
Read
[https://support.plesk.com/hc/en-us/articles/360020966774-Unable-to-install-a-Let-s-Encrypt-certificate-Order-s-status-pending-is-not-acceptable-for-finalization](https://support.plesk.com/hc/en-us/articles/360020966774-Unable-to-install-a-Let-s-Encrypt-certificate-Order-s-status-pending-is-not-acceptable-for-finalization)
> Previous attempt to install a Let's Encrypt certificate failed for some reason. As a result, the Let's Encrypt extension tries to finalize an order without actually having fulfilled the required authorizations.
There is a description what you can do.
---
### Author:  [@THZ](https://community.letsencrypt.org/u/THZ)
#### Post date: [November 16, 2019, 3:06pm UTC](https://community.letsencrypt.org/t/invalid-response-from-https-acme-v02-api-letsencrypt-org/106378/3 "2019-11-16T15:06:36Z")
That solved the problem. Thank you @JuergenAuer for the mulligan!
---
### Author:  [@system](https://community.letsencrypt.org/u/system)
#### Post date: [December 16, 2019, 3:21pm UTC](https://community.letsencrypt.org/t/invalid-response-from-https-acme-v02-api-letsencrypt-org/106378/4 "2019-12-16T15:21:00Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.