The certificate is signed by itself, not by a trusted CA chain. Firefox cannot verify authenticity and blocks the page. For production: get a real cert (Let's Encrypt is free, certbot takes 5 minutes). For dev/staging: use mkcert (creates a local CA + system-trusted certs) or add a per-host exception in Firefox.
Below: details, example, related terms, FAQ.
Free online tool — SSL certificate checker: instant results, no signup.
# 1. Production fix — Let's Encrypt (Ubuntu, nginx)
sudo apt install certbot python3-certbot-nginx
sudo certbot --nginx -d example.com -d www.example.com
# Auto-renew is already in /etc/cron.d/certbot
# 2. Dev fix — mkcert (macOS / Linux / Windows)
brew install mkcert # or choco install mkcert
mkcert -install # installs the local CA in the system trust store
mkcert example.local localhost 127.0.0.1
# Outputs: example.local+2.pem (cert) + example.local+2-key.pem
# nginx: ssl_certificate /path/example.local+2.pem; ssl_certificate_key ...
# 3. Detect cert type
openssl x509 -in cert.pem -noout -issuer -subject
# If issuer == subject — self-signedTo resolve the MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT error in Firefox, you need to ensure that your website's SSL certificate is trusted. This can be achieved by either obtaining a valid SSL certificate from a trusted Certificate Authority (CA) or manually adding the self-signed certificate to Firefox's certificate store. For detailed steps, see the sections below.
The MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT error occurs when Firefox encounters a self-signed SSL certificate that it cannot verify against a trusted Certificate Authority (CA). This indicates that the certificate is not trusted by default, which is a common scenario in development environments or when using self-signed certificates for testing purposes.
When a browser connects to a website, it checks the SSL certificate presented by the server. If the certificate is self-signed, the browser will not find a chain of trust leading to a recognized CA, triggering the MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT error. This is a security measure to prevent man-in-the-middle attacks and ensure secure communications.
To resolve this issue, there are two primary approaches:
If you decide to use a self-signed certificate, you can add it to Firefox's certificate store to eliminate the MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT error. Follow these steps:
openssl x509 -in your_certificate.crt -out your_certificate.pem -outform PEMAfter completing these steps, navigate back to the website that previously gave you the error. The MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT should no longer appear, allowing you to establish a secure connection without issues.
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.
Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).
Full chain verification: from leaf certificate through intermediates to root CA.
Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.
Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.
SSL certificate monitoring
TLS config audit
HTTPS as ranking factor
customer trust
www and subdomains.Strict-Transport-Security header forces browsers to always use HTTPS.SSL certificate monitoring, check history and alerts 30 days before expiry.
Sign up freeNo — every visitor sees a warning, search engines flag the site as unsafe, forms fail (mixed content). Let's Encrypt is free and automated.
mkcert puts a local CA in the OS trust store — browsers trust automatically. openssl self-sign — you have to manually add an exception in every browser on every machine.
If the domain is in the HSTS preload list — Firefox blocks hard (even the exception button is gone). Only preload after you have a real cert.
Free plan — 20 monitors, 5-minute checks, no card required. Upgrade for 1-minute interval and multi-region monitoring.