Skip to content

ERR_CERT_WEAK_SIGNATURE_ALGORITHM: Obsolete SHA-1/MD5

TL;DR:

ERR_CERT_WEAK_SIGNATURE_ALGORITHM means the SSL certificate is signed with an obsolete algorithm (SHA-1, MD5, MD2). Chrome blocks such certificates since 2017. Fix: reissue with SHA-256 or stronger. All modern CAs (Let's Encrypt, DigiCert) default to SHA-256.

This error is a frequent issue in SSL debugging. We cover the causes and step-by-step fix.

Check your site's SSL →

What ERR_CERT_WEAK_SIGNATURE_ALGORITHM means

ERR_CERT_WEAK_SIGNATURE_ALGORITHM means the SSL certificate is signed with an obsolete algorithm (SHA-1, MD5, MD2). Chrome blocks such certificates since 2017. Fix: reissue with SHA-256 or stronger. All modern CAs (Let's Encrypt, DigiCert) default to SHA-256.

The error can appear in Chrome, Edge, Opera, Brave (all Chromium-based), and partially in Firefox and Safari. Different browsers display the same code differently, but the underlying issue is the same.

How to fix (step-by-step)

  1. Check the SSL certificate online — the Enterno.io checker shows the grade, expiry, chain, and specific cause.
  2. If the issue is server-side — reissue the certificate via certbot or your chosen CA.
  3. Update nginx/apache config (enable TLS 1.2/1.3, fullchain, correct ciphers).
  4. Check kernel OpenSSL — an outdated openssl < 1.1 can break handshakes.
  5. After deploy: recheck via SSL checker + clear the browser SSL cache.

Check SSL now →

Related SSL errors

TL;DR

The ERR_CERT_WEAK_SIGNATURE_ALGORITHM error indicates that the SSL certificate uses a cryptographic signature algorithm deemed insecure, such as SHA-1. To resolve this issue, update your SSL certificate to use a stronger signature algorithm like SHA-256 or SHA-384. Ensure your server configuration supports these algorithms and consider obtaining a new certificate from a trusted Certificate Authority (CA) that complies with current security standards.

Understanding the ERR_CERT_WEAK_SIGNATURE_ALGORITHM Error

The ERR_CERT_WEAK_SIGNATURE_ALGORITHM error occurs when a web browser, such as Chrome or Firefox, encounters an SSL certificate that employs a weak signature algorithm. This typically involves algorithms like SHA-1, which have been deprecated due to vulnerabilities that make them susceptible to attacks. As of 2026, modern web standards require the use of stronger algorithms like SHA-256 or SHA-384 to ensure secure communications.

This error can lead to significant issues, including warnings in the browser that discourage users from proceeding to the website. Therefore, it is essential for web administrators and developers to rectify this error promptly to maintain the integrity and security of their sites.

To identify if your SSL certificate is using a weak signature algorithm, you can utilize online SSL checkers or commands such as:

openssl s_client -connect yourdomain.com:443 -servername yourdomain.com

In the output, look for the line that starts with Signature Algorithm:. If it mentions SHA-1 or another weak algorithm, an update is necessary.

Fixing the ERR_CERT_WEAK_SIGNATURE_ALGORITHM Error

To fix the ERR_CERT_WEAK_SIGNATURE_ALGORITHM error, follow these steps:

  1. Check Your Current SSL Certificate: Use the openssl command as mentioned earlier to verify the signature algorithm of your existing SSL certificate.
  2. Obtain a New SSL Certificate: Contact your Certificate Authority (CA) to request a new SSL certificate that uses a strong signature algorithm. Ensure that the CA supports SHA-256 or SHA-384. Popular CAs include Let's Encrypt, DigiCert, and Comodo.
  3. Update Your Server Configuration: Once you have the new certificate, update your server configuration to use the new certificate files. Depending on your server type, the process may vary:
  • For Apache: Update your httpd.conf or ssl.conf files:
SSLCertificateFile /path/to/your_domain.crt
SSLCertificateKeyFile /path/to/your_private.key
SSLCertificateChainFile /path/to/chain_file.crt
  • For Nginx: Update your server block configuration:
ssl_certificate /path/to/your_domain.crt;
ssl_certificate_key /path/to/your_private.key;
  1. Test Your Configuration: After updating your server configuration, restart your web server and test the SSL certificate using the openssl command again to ensure the weak signature algorithm error is resolved.
  2. Monitor for Future Issues: Regularly check your SSL certificate and server configurations to ensure compliance with the latest security standards, and consider implementing automated monitoring tools to alert you of any issues.

By following these steps, you can effectively resolve the ERR_CERT_WEAK_SIGNATURE_ALGORITHM error and enhance the security of your web infrastructure.

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

Is it safe to ignore ERR_CERT_WEAK_SIGNATURE_ALGORITHM?

No. This error indicates a real SSL certificate problem. Ignoring it (via chrome://flags or "thisisunsafe") makes the connection vulnerable to man-in-the-middle attacks. Fix it on the server side.

How can I catch this error early?

Use the <a href="/en/ssl">Enterno.io SSL/TLS checker</a>, or <a href="/en/monitors">set up monitoring</a> with 14-day expiry alerts. Receive an email/Telegram notification before your users see the error.

Does clearing cookies / cache help?

Sometimes, for transient cached SSL errors. Steps: chrome://net-internals/#sockets → Flush sockets, chrome://net-internals/#hsts → Delete domain security policies (carefully, for debugging only). But if the issue is server-side, cache clearing will not help.

Is Let's Encrypt free — and is the certificate trusted?

Yes, Let's Encrypt certificates are in every modern trust store (Chrome, Firefox, Safari, Edge). 90-day validity with automatic renewal via certbot. No reason to use a paid CA for a standard website.

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.