STEP-BY-STEP GUIDE

Firefox: Troubleshoot SEC_ERROR_UNKNOWN_ISSUER Safely

What to do first

Check publisher for single site or multiple sites without adding exceptions.

This is a general troubleshooting guide, not an announcement of a current outage.

Affected products and symptoms

Product
Mozilla Firefox
Versions and conditions
Firefox Desktop
Error codes and identifiers
SEC_ERROR_UNKNOWN_ISSUERMOZILLA_PKIX_ERROR_MITM_DETECTED

Symptoms

  • A certificate issuer is unknown
  • Warning appears on multiple HTTPS sites

Causes and conditions

Possible causes include a missing intermediate certificate, an incomplete certificate chain, or HTTPS inspection on the device or network.

Before you start

  • Record URLs, codes, and times
  • Cancel login/payment

Precautions

  • do not create certificate exceptions
  • Do not stop encrypted communication inspection without permission

Tools and official pages used in this guide

Mozilla Firefox troubleshooting sequence: see code; divide the range; See basic condition; Identify the inspection source; Request correction
Procedure overview created by FaultNote. Read the precautions and full instructions before changing settings. Read the full steps

Step-by-step instructions

  1. 01

    see code

    #

    Record the code and issuer name in the alert's Details and do not add a permanent exception.

    If the certificate issuer information is displayed, also note the name. Although we cannot conclude that it is malware or a PC malfunction just because of the unknown issuer code, we cannot confirm the trust relationship, so do not enter credentials.

    Open [Details] or [Error details] at the bottom of the error page and record SEC_ERROR_UNKNOWN_ISSUER and the failure URL. Even if the Add Exception button appears, do not select it until you verify the certificate issuer and site administrator.

  2. 02

    divide the range

    #

    Open another HTTPS site such as Mozilla official website. If there is one site, suspect the server; if there are multiple sites, suspect the terminal/network.

    Check if the same URL can be opened on another device, and record whether it is only available on a specific device. If it only occurs on your company's network, inform your administrator that it may be related to your organization's HTTPS inspection or certificate distribution.

  3. 03

    See basic condition

    #

    Check the OS date and time, update Firefox, and restart.

    Open the Firefox menu → [Help] → [About Firefox], and when updates are presented, restart after completion. If your PC's clock is off, first correct the date and time on the Windows side and then reopen the page.

  4. 04

    Identify the inspection source

    #

    If the issuer is a protected product or organization name, confirm HTTPS inspection and certificate distribution using the administrator's regular procedures.

    Even on personal PCs, check to see if the problem occurred immediately after installing or updating an antivirus product. Check your product's official support for instructions regarding certificates, and avoid loading certificate files from unknown sources.

  5. 05

    Request correction

    #

    For a single site, notify the administrator; for multiple sites, notify the administrator of the publisher, code, and Firefox version.

    If the problem affects only one site, ask its administrator, ask them to confirm the certificate chain settings. Include the Firefox version, network type, and results from other sites and devices in the reproduction information, and do not choose a permanent workaround by adding an exception.

Check the result

  • HTTPS site opens without exception
  • Issuer and trust chain as intended

If the problem continues

  • For home devices, consult a protection product vendor.
  • Do not import a CA certificate yourself on an organization-managed device.

Scope of this guide

Troubleshooting guide — General diagnostic and recovery procedures based on official support. It does not describe a specific current incident.

Frequently asked questions

Is it fake?

I can't say for sure. Check the issuer and scope as there may be insufficient configuration or regular inspection.

Can I use it by adding an exception?

This is not recommended as it allows connections that have not been verified to be secure.

Official sources and dates

Source publication or resolution date: 2026-03-31. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.

Related troubleshooting guides

Get more from Mozilla Firefox

← Search English guides