• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Could not retrieve an OCSP response

H

hostking

Regular Pleskian
Could not retrieve an OCSP response.

The Failure Reason is: REASON_OCSP_RESPONSE_RETRIEVAL_ERROR
The OCSP Url is: http://r11.o.lencr.org
The previous OCSP response contained the following times:
ThisUpdate: ‎1601‎-‎01‎-‎01T00:00:00.000000000Z
NextUpdate: ‎1601‎-‎01‎-‎01T00:00:00.000000000Z

The attached data contains the certificate.

So from what I understand the above error is due to Letsencrypt disabling OSCP responders in Aug 2025: Ending OCSP Support in 2025

So does that mean we should just disable it now in powershell?

Thoughts?
 
You must log in or register to reply here.

Similar threads

I
Resolved Preventing bot brute force probes against Postfix/SMTP
Replies
5
Views
2K
iainh
I
Zalvatore Dela
Issue Outlook and Gmail block my clients emails! DKIM too long
Replies
8
Views
9K
Zalvatore Dela
Zalvatore Dela
Bitpalast
Input Let's Encrypt false positive 403 response when used with certain e-mail addresses
Replies
3
Views
1K
Bitpalast
Bitpalast
F
Issue Let's encrypt - unable to renew *some* subdomains
2
Replies
20
Views
15K
ChristophRo
ChristophRo
Ian Bowden
Issue 'Clone' actually seems to be functioning more like 'merge'
Replies
0
Views
2K
Ian Bowden
Ian Bowden
Back
Top