Skip to content

ERR_SSL_OCSP_INVALID_RESPONSE

Key idea:

ERR_SSL_OCSP_INVALID_RESPONSE — Chrome received an OCSP response but it is corrupted, expired (> 7 days), or signed by the wrong responder cert. Fix: disable ssl_stapling_verify (if the responder is problematic) or refresh OCSP cache. CA outage — wait it out.

Below: causes, fixes, FAQ.

Check your site's SSL →

Common Causes

  • OCSP response expired — nextUpdate passed
  • CA OCSP responder returns stale data
  • Cache invalidation delay on CDN
  • Wrong OCSP signer cert
  • Clock skew on server (> 1 hour)

Step-by-Step Fix

  1. Check system clock: timedatectl status
  2. Force OCSP refresh: reload nginx, wait 5 min
  3. Temporarily disable verify: ssl_stapling_verify off;
  4. Update chain: ssl_trusted_certificate with fresh CA chain
  5. CA outage — valid within an hour

Check SSL Certificate →

Related SSL Errors

TL;DR

The ERR_SSL_OCSP_INVALID_RESPONSE error in Chrome indicates a failure in the Online Certificate Status Protocol (OCSP) response verification, often due to a misconfigured server or network issues. To resolve this, ensure your server is correctly configured to provide OCSP responses, check for firewall or proxy interference, and verify the SSL certificate's validity using tools like openssl or online SSL checkers.

Understanding ERR_SSL_OCSP_INVALID_RESPONSE

The ERR_SSL_OCSP_INVALID_RESPONSE error occurs when a browser fails to validate an SSL certificate's revocation status through OCSP. This protocol allows browsers to check if a certificate has been revoked by the Certificate Authority (CA) without having to download the entire Certificate Revocation List (CRL). When this validation fails, users are presented with this error message.

Common causes include:

  • Server Misconfiguration: The web server may not be correctly set up to respond to OCSP requests.
  • Network Issues: Firewalls or proxies may block OCSP requests or responses, causing validation failures.
  • Expired or Invalid Certificates: If the SSL certificate itself is expired or not properly issued, OCSP responses may be invalid.

To diagnose the issue, you can use the following command to check the OCSP response directly:

openssl ocsp -issuer issuer_cert.pem -cert user_cert.pem -url http://ocsp.example.com

This command checks the OCSP response for a given user certificate against its issuer. If the response is valid, you will see confirmation; if it fails, you may need to troubleshoot further.

Fixing the ERR_SSL_OCSP_INVALID_RESPONSE Error

To effectively resolve the ERR_SSL_OCSP_INVALID_RESPONSE error, follow these steps:

  1. Check Your SSL Certificate: Use SSL checker tools like SSL Shopper to confirm that your SSL certificate is valid and properly configured.
  2. Verify OCSP Settings: Ensure your web server is set up to handle OCSP requests. For Apache, you can add the following lines to your configuration:
SSLUseStapling on
SSLStaplingCache "shmcb:/var/run/ocsp-status(128000)"

These directives enable OCSP stapling and specify a cache location for OCSP responses.

  1. Check Network Configuration: Make sure that firewalls or proxies are not blocking OCSP traffic. You may need to allow outbound traffic on port 80 (HTTP) and port 443 (HTTPS).
  2. Test OCSP Response: Use the curl command to test the OCSP response directly:
curl -v http://ocsp.example.com

This will show you the response headers and any potential issues. Look for the HTTP/1.1 200 OK status to ensure the OCSP responder is reachable.

  1. Consult Your Certificate Authority: If issues persist, contact your CA for assistance. They can provide insights into potential revocation issues or misconfigurations.

By systematically following these steps, you can effectively troubleshoot and resolve the ERR_SSL_OCSP_INVALID_RESPONSE error, ensuring secure connections for your users.

CertificateExpiry, issuer, domains (SAN)
ChainIntermediate and root CA validation
TLS ProtocolTLS version and cipher suite
VulnerabilitiesHeartbleed, POODLE, weak ciphers

Why teams trust us

TLS 1.3
supported
Full
CA chain check
<2s
result
30/14/7
days-to-expiry alerts

How it works

1

Enter domain

2

TLS chain verified

3

Expiry date & vulnerabilities

What Does the SSL Check Cover?

SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.

Certificate Details

Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).

Chain of Trust

Full chain verification: from leaf certificate through intermediates to root CA.

TLS Analysis

Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.

Expiry Alerts

Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.

DV vs OV vs EV Certificates

DV (Domain Validation)
  • Confirms domain ownership only
  • Issued in minutes automatically
  • Free via Let's Encrypt
  • Suitable for most websites
  • Most common certificate type
OV / EV
  • Organization (OV) or Extended Validation (EV)
  • Issued in 1-5 business days
  • Costs $50 to $500/year
  • For finance, e-commerce, government sites
  • Increases user trust

Who uses this

DevOps

SSL certificate monitoring

Security

TLS config audit

SEO

HTTPS as ranking factor

E-commerce

customer trust

Common Mistakes

Expired certificateBrowsers block sites with expired SSL. Set up auto-renewal or monitoring.
Incomplete certificate chainWithout intermediate CA, some browsers and bots cannot verify the certificate.
Mixed content on HTTPS siteHTTP resources on an HTTPS page — the browser lock icon disappears, reducing trust.
Using TLS 1.0/1.1Legacy TLS versions have known vulnerabilities. Use TLS 1.2+ or 1.3.
Domain mismatch in certificateThe certificate must cover all site domains, including www and subdomains.

Best Practices

Set up auto-renewalLet's Encrypt + certbot with cron — certificate renews automatically every 60-90 days.
Enable HSTSStrict-Transport-Security header forces browsers to always use HTTPS.
Use TLS 1.3TLS 1.3 is faster (1-RTT handshake) and safer — legacy ciphers removed.
Monitor expiration datesCreate a monitor on Enterno.io — get notified well before expiration.
Verify chain after renewalAfter certificate renewal, confirm that intermediate certificates are installed.

Get more with a free account

SSL certificate monitoring, check history and alerts 30 days before expiry.

Sign up free

Learn more

Sources

Frequently Asked Questions

OCSP vs CRL?

OCSP — real-time status check, CRL — list of revoked. OCSP faster (one cert), CRL — all revoked at once. Modern — OCSP stapling.

Short-lived certs killing OCSP?

Let's Encrypt 90d, then 6d (2026+). Cert shorter than CRL refresh — OCSP not needed. Industry trend.

Does Chrome disable OCSP?

By default yes, since 2012 (too slow, privacy). Stapling works, raw OCSP calls do not.

Why this error now?

Usually a single-client issue: stale local cache. Clear Chrome SSL state: chrome://net-internals/#hsts → Delete domain.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.