It produced this output:
Invalid OCSP response status for /etc/letse ncrypt/live/bluebear.network/cert.pem: OCSPResponseStatus.UNAUTHORIZED
Invalid OCSP response status for /etc/letsencrypt/live/forums.bluebear.network/cert.pem: OCSPResponseStatus.UNAUTHORIZED
My web server is (include version): Nginx 1.10.3
The operating system my web server runs on is (include version): Ubuntu 16.04
My hosting provider, if applicable, is: - Proxmox VM on Dedicated Server by Zade Servers
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):
no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if youâre using Certbot): Certbot 0.35.0
The response "unauthorized" is returned in cases where the client is not authorized to make this query to this server or the server is not capable of responding authoritatively (cf. [RFC5019], Section 2.2.3).
Unauthorized is corroborated when using crt.sh as the OCSP client for the most recent certificate of that domain: crt.sh | 1557308103
Hopefully the ops people will see it on their graphs ...
Oh yeah, didnât notice the expiry. That also reminds me that this has been discussed before and resulted in this issue: https://github.com/certbot/certbot/issues/7152 . The Certbot error message seems to have changed again.