Skip to content

MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING

Key idea:

MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING — cert carries the tlsfeature extension (RFC 7633) with OCSP Must-Staple flag, but the server is not stapling an OCSP response in the TLS handshake. Fix: enable OCSP stapling on the server, or reissue cert without Must-Staple. nginx: ssl_stapling on + DNS resolver.

Below: causes, fixes, FAQ.

Check your site's SSL →

Common Causes

  • Cert issued with Must-Staple flag but nginx/Apache stapling disabled
  • OCSP responder unreachable (CA outage)
  • nginx ssl_stapling_verify on — fails → no staple
  • Resolver missing — resolver 8.8.8.8 1.1.1.1 required
  • Firewall blocks outgoing HTTP to OCSP endpoint

Step-by-Step Fix

  1. nginx: ssl_stapling on; ssl_stapling_verify on; resolver 1.1.1.1 valid=300s;
  2. ssl_trusted_certificate chain.pem; (for stapling verify)
  3. Reload nginx, wait ~5 min for prefetch
  4. Verify: openssl s_client -connect host:443 -status → "OCSP Response Data"
  5. Or reissue cert without Must-Staple (most CAs allow)

Check SSL Certificate →

Related SSL Errors

TL;DR: Fixing MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING

The MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING error indicates that the server is missing essential TLS features supported by modern browsers, such as TLS 1.3 or specific cipher suites. To resolve this, ensure your server configuration supports the required TLS version and ciphers. For example, if using Apache, update your ssl.conf with SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1 to enable TLS 1.2 and above.

Understanding the MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING Error

The MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING error commonly occurs when a web browser attempts to establish a secure connection with a server that does not meet the latest TLS requirements. This can be due to outdated server configurations or unsupported cipher suites. Modern browsers like Firefox and Chrome enforce strict security standards, and if a server fails to comply, users will encounter this error.

To effectively troubleshoot this issue, it is essential to understand the underlying causes:

  • Outdated TLS Versions: Many servers still operate on TLS 1.0 or TLS 1.1, which are considered insecure and deprecated.
  • Unsupported Cipher Suites: If a server does not support the latest cipher suites required by modern browsers, this error may occur.
  • Server Misconfiguration: Configuration errors in web servers like Apache or Nginx may lead to this issue.

To check the current TLS version and supported cipher suites, you can use tools such as SSL Labs. This tool provides a comprehensive report on your server’s SSL/TLS configuration, including details on supported protocols and cipher suites.

Practical Steps to Fix MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING

Resolving the MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING error typically involves updating your server's configuration to comply with modern security standards. Below are practical steps for common web servers:

For Apache Servers:

1. Open your Apache configuration file, typically located at /etc/httpd/conf/httpd.conf or /etc/apache2/sites-available/default-ssl.conf.

2. Update your SSL configuration to support TLS 1.2 and 1.3:

SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1

3. Ensure you are using recommended cipher suites. An example configuration might look like this:

SSLCipherSuite HIGH:!aNULL:!MD5

4. Restart Apache to apply the changes:

sudo systemctl restart apache2

For Nginx Servers:

1. Open your Nginx configuration file, typically located at /etc/nginx/nginx.conf or /etc/nginx/sites-available/default.

2. Add or update the following lines in your server block:

ssl_protocols TLSv1.2 TLSv1.3;

3. Specify secure cipher suites:

ssl_ciphers 'HIGH:!aNULL:!MD5';

4. Test your Nginx configuration for syntax errors:

sudo nginx -t

5. Restart Nginx:

sudo systemctl restart nginx

Final Verification:

After making these changes, use the SSL Labs test again to verify that your server now supports the required TLS features. Additionally, ensure that your browser is updated to the latest version to avoid compatibility issues.

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

What is Must-Staple?

A cert extension telling the client: "I expect a stapled OCSP response in the handshake". Missing → cert invalid, even if OCSP responder times out.

Does my CA set Must-Staple?

Let's Encrypt — no by default. DigiCert — optional. Became rare 2024+ because CA-level OCSP turned reliable.

Always enable stapling?

Yes, good practice. Reduces RTT, improves privacy (client does not contact CA directly).

How to verify?

<a href="/en/ssl">Enterno SSL</a> shows OCSP stapling status in report.

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.