Skip to content

SEC_ERROR_CA_CERT_INVALID

Key idea:

SEC_ERROR_CA_CERT_INVALID — Firefox treats the intermediate/root CA cert as invalid. Causes: expired CA cert, malformed DER encoding, deprecated CA (Symantec 2018), root removed from NSS. Fix: replace chain with a fresh intermediate, or switch CA. Let's Encrypt ISRG Root X1 is 2026-valid with no issues.

Below: causes, fixes, FAQ.

Check your site's SSL →

Common Causes

  • Intermediate CA expired (Let's Encrypt X3 → X1 migration issues)
  • Root CA removed from NSS store (Symantec, TurkTrust)
  • Cert chain malformed — not DER/PEM standard
  • Self-signed root not imported into Firefox trust
  • Private CA with wrong CA:TRUE BasicConstraints

Step-by-Step Fix

  1. Reissue the cert — modern intermediate chained automatically
  2. For Let's Encrypt: apache2ctl graceful + manual renew
  3. Chain validator: Enterno SSL / SSLLabs
  4. nginx: ssl_certificate fullchain.pem; (fullchain, not cert alone)
  5. Private CA: BasicConstraints=CA:TRUE + valid pathLenConstraint

Check SSL Certificate →

Related SSL Errors

TL;DR: How to Fix SEC_ERROR_CA_CERT_INVALID in Firefox

The SEC_ERROR_CA_CERT_INVALID error in Firefox indicates that the browser cannot verify the certificate authority (CA) for the website you are trying to access. To resolve this issue, check the website's SSL certificate, ensure your system time and date are correct, and potentially clear your browser cache or update Firefox. If the issue persists, consider updating the certificate authority list or checking for any expired certificates.

Understanding SEC_ERROR_CA_CERT_INVALID

The SEC_ERROR_CA_CERT_INVALID error occurs when Firefox detects that the SSL certificate presented by a website is either self-signed, expired, or issued by an untrusted certificate authority. This error can prevent users from accessing secure websites, impacting both user experience and site credibility.

When encountering this error, it is essential to consider the following factors:

  • Certificate Authority Trust: Ensure that the SSL certificate is issued by a recognized and trusted CA. Certificates from untrusted sources will trigger this error.
  • Validity Period: Check if the SSL certificate has expired. Certificates typically have a validity period ranging from one to three years.
  • Intermediary Certificates: Some SSL certificates require intermediary certificates to establish a complete trust chain. Ensure these are correctly installed on the server.

To diagnose the issue, users can check the certificate details by clicking on the padlock icon in the address bar, then selecting 'More Information' and 'View Certificate'. This will display the issuer, validity dates, and trust level of the certificate.

Practical Steps to Resolve the Error

To effectively resolve the SEC_ERROR_CA_CERT_INVALID error, follow these practical steps:

  1. Check System Time and Date: An incorrect system time can cause SSL certificate validation issues. Ensure your system clock is accurate.
date

On Linux, use the date command to verify the current date and time.

  1. Clear Browser Cache: Cached data may interfere with SSL certificate validation. To clear the cache in Firefox:
  • Go to Options > Privacy & Security.
  • Under Cookies and Site Data, click Clear Data.
  1. Update Firefox: Ensure you are using the latest version of Firefox, as updates may include fixes for certificate validation issues. To update:
  • Click on the menu button and select Help, then About Firefox.
  • Firefox will automatically check for updates and download them.
  1. Manually Install Certificate: If the website uses a self-signed certificate or a CA not recognized by Firefox, you may need to manually add the certificate:
  • Download the certificate file (usually a .crt or .cer file).
  • Open Firefox and navigate to Options > Privacy & Security.
  • Scroll down to the Certificates section and click on View Certificates.
  • Under the Authorities tab, click Import and select the downloaded certificate file.

After following these steps, restart Firefox and try accessing the website again. If the issue persists, consider checking the server-side configuration or contacting the website administrator for further assistance.

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

ISRG Root X1 in 2026?

Active. 2021 → 2035. Cross-signed the old DST Root (expired 2024), but X1 self-trust in 99% of modern stacks.

nginx fullchain vs cert+chain?

Fullchain includes intermediate. nginx does not fetch intermediate automatically; it ships only the leaf cert → Firefox fails validation.

NSS trust store vs OS?

Firefox uses NSS (separate from OS), ~420 roots. Chrome uses OS trust (Windows/macOS) or the Chrome Root Store.

Private CA setup?

OpenSSL ca.cnf + valid extensions. Import .crt via about:preferences#privacy → View Certificates → Import.

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.