How to Fix NET::ERR_CERT_INVALID Error in WordPress

Expired or Invalid SSL Certificate on WordPress Website

SSL certificates typically expire every 90 days for free certificates (such as Let’s Encrypt) or every 1 to 2 years for paid certificates. When the expiration date passes, browsers immediately reject the certificate and show the error.

An expired certificate is one of the most common causes of this error. If your hosting provider manages auto-renewal, a failed renewal process can leave your site with an expired certificate without warning. Always monitor your SSL certificate’s expiration date and set up renewal alerts.

SSL Certificate Domain Name Mismatch Issues

Name mismatch occurs when the website’s address does not match the name on the certificate. For example, if your certificate covers www.example.com but a visitor accesses example.com (without www), The browser sees a mismatch and throws the error.

Domains may be listed incorrectly in the certificate, resulting in validation failure. This often happens when a wildcard certificate or multi-domain certificate is configured incorrectly during setup.

Incorrect SSL Certificate Installation or Configuration

A certificate that is not installed properly on the web server will fail validation. This includes uploading the wrong certificate files, skipping required configuration steps in cPanel or your hosting panel, or using a certificate generated for the wrong server.

If you recently reinstalled your SSL certificate or migrated your hosting, double-check that the certificate files are correctly placed and linked to your domain.

Missing Intermediate SSL Certificate Chain

SSL certificates work within a chain of trust. Your certificate must be linked back to a trusted root certificate authority through one or more intermediate certificates. If the intermediate certificate is missing from your server configuration, browsers cannot complete the chain validation and display the error.

The certificate authority that issued your certificate provides the intermediate bundle. It must be installed alongside your main certificate. Many server configurations omit this step, which is a frequent cause of the error.

Mixed Content Issues After Moving WordPress From HTTP to HTTPS

When you move WordPress from HTTP to HTTPS, some resources, images, scripts, or stylesheets may still load over HTTP. This creates a mixed content issue. While mixed content alone usually shows a browser warning rather than a full block, it can contribute to SSL validation failures in certain configurations.

Learning how to force HTTPS on WordPress is a critical step after SSL installation. If your WordPress site has lingering HTTP references in the database or theme files, they need to be updated.

WordPress URL Configuration Issues After SSL Installation

WordPress stores its site URL in the database. After SSL installation, if the siteurl and home values in the database still point to http:// instead of https://, WordPress may serve mixed or incorrect URLs. This can cause the browser to receive conflicting signals about the certificate, leading to the error.

This is one of the first settings to verify after enabling SSL on a WordPress site.

CDN, Hosting, or Firewall SSL Configuration Problems

If your WordPress site uses a CDN (Content Delivery Network) like Cloudflare, the CDN handles SSL termination between the browser and its edge servers. A mismatch between the CDN’s SSL mode and your origin server’s configuration can trigger certificate errors.

Similarly, a web server firewall or security plugin that intercepts HTTPS traffic may conflict with the certificate presented to the browser. Errors can occur if the website uses a certificate that the browser does not trust when it is filtered by a proxy or firewall.

A Cloudflare error code 522 is related but distinct; it indicates a connection timeout between Cloudflare and the origin server and can sometimes accompany SSL misconfigurations.

Browser Cache or Outdated SSL Information Causing Certificate Errors

Browsers store SSL certificate information in a local cache. If you recently renewed or replaced your certificate, the browser may still be reading the old, invalid cached version. This causes the error to persist even after the server certificate issue has been resolved.

A corrupt browser cache can interfere with the SSL handshake and cause errors. Clearing the SSL state and browser cache is often the fastest and easiest fix when the server-side configuration is confirmed to be correct.

How to Check What is Causing NET::ERR_CERT_INVALID Error in WordPress?

Before applying any fix, identify the exact source of the problem. Jumping straight to solutions without diagnosis wastes time and can introduce new issues.

Verify SSL Certificate Status and Details in Browser

When the error appears in Chrome, click the “Not Secure” or warning icon in the address bar. Chrome will display a brief message about the certificate. Click on “Certificate (Invalid)” or “Your connection is not private” to see the full certificate details.

This panel shows whether the certificate is expired, untrusted, or mismatched. It also tells you which certificate authority issued it and the domain it covers.

Check SSL Certificate Expiry Date, Domain, and Issuer Information

Inside the certificate viewer, look for three key fields:

• Valid From/Valid To: Check the expiration dates. If today’s date is past the “Valid To” date, the certificate has expired.
• Issued To: Confirm this matches your website’s domain exactly, including whether it covers the www version.
• Issued By: Confirm the issuing certificate authority is a trusted CA (such as Let’s Encrypt, DigiCert, or Comodo). If it shows your own domain or server name, you may have a self-signed certificate.

Test SSL Configuration Using Online SSL Checker Tools

Free tools like SSL Labs (ssllabs.com/ssltest) let you run a full SSL analysis on your domain. These tools check the validity of your certificate, the completeness of its chain, protocol support, and configuration. They grade your SSL setup and flag specific problems.

Running a check here is the most reliable way to confirm whether the issue is a missing intermediate certificate, a weak cipher suite, or a misconfiguration on your web server.

Identify Whether the Issue is From WordPress, Hosting, or Browser Settings

To isolate the source of the error:

• Open the site in an incognito window. If it loads correctly, a browser extension may be causing the issue. Opening a site in incognito mode can help determine if extensions are causing SSL problems.
• Try opening the page in different browsers (Firefox, Edge, Safari). If the error appears in all major browsers, the problem is on the server. If it only appears in Chrome, it may be a local browser issue.
• Ask another person on a different network to check the site. If they see the site fine, the issue may be related to your local network, VPN, or antivirus software.
• Check if WordPress maintenance tasks, such as a recent plugin update, coincided with the error first appearing.

Methods to Fix NET::ERR_CERT_INVALID Error in WordPress

Once you know the cause, apply the matching fix. Work through the relevant steps in order.

On your server, ensure NTP (Network Time Protocol) is enabled to keep the time synchronized automatically. The correct time zone is also important. Check your server’s time zone in the hosting control panel, and confirm it is set correctly.

For local device issues, an incorrect date on your computer can cause a valid certificate to appear expired or not yet valid. On Windows, right-click the clock in the taskbar and select Adjust date/time.

On Mac, go to System Preferences via the Apple menu and open Date and Time. Enable “Set date and time automatically,” then confirm the correct time zone is selected.

Update Browser and Operating System Certificate Settings

Outdated browsers may not trust SSL certificates issued by newer certificate authorities. Update Google Chrome to the latest version by going to Help → About Google Chrome. Chrome will check for and apply updates automatically. Keeping your browser current ensures its built-in CA trust store is up to date.

Your operating system also maintains a certificate trust store. On Windows, updates to the root certificate program are distributed via Windows Update. On macOS, they come through system updates. If your OS is significantly outdated, it may be missing trust entries for newer CAs.

Running the latest OS updates resolves many persistent SSL errors that appear only on specific devices. This is particularly relevant when major browsers work fine for other users but show errors on your machine. Performing a WordPress security audit on your site also flags outdated configurations that may contribute to SSL problems.

Temporarily Disable Antivirus or Firewall SSL Inspection

Antivirus software and firewalls can interfere with SSL verification. Many security suites include a feature called SSL inspection or HTTPS scanning. This feature intercepts HTTPS traffic and re-signs it with the antivirus software’s own certificate. If your browser does not trust that certificate, it displays the error.

To test whether your antivirus software is causing the issue, temporarily disable HTTPS scanning in the antivirus settings. Common options appear under names like “Web Shield,” “HTTPS Filtering,” or “SSL Scanning,” depending on the product.

If the error disappears after disabling this feature, re-enable it and look for an option to add your site as a trusted exception. This ensures the antivirus does not intercept SSL traffic for domains you trust.

Using a public network, such as a shared Wi-Fi connection at a café or airport, can also cause SSL certificate errors. Public networks often use proxies or redirect HTTPS traffic in ways that break certificate validation. Test your site on a private network or mobile data to rule this out.

Conclusion: Fix NET::ERR_CERT_INVALID Error

The NET::ERR_CERT_INVALID error in WordPress is almost always fixable once you know the root cause. Start by checking the certificate details in Chrome, running an SSL test, and identifying whether the problem is server-side, browser-side, or device-side.

The most common fixes include renewing an expired certificate, correcting a domain mismatch, installing the full certificate chain, updating WordPress URLs to HTTPS, and clearing the browser’s SSL state. For CDN-related issues, setting the correct SSL mode in Cloudflare resolves most conflicts quickly.

Proactive SSL management prevents this error from recurring. Monitor your certificate’s expiration date, automate renewals where possible, and include SSL checks in your regular WordPress website management routine.

If the error persists after working through these steps, the issue may require a deeper WordPress security checklist review or assistance from your hosting provider. A systematic approach, checking each potential cause one at a time, will get your site back online securely and quickly.

FAQs About Fixing NET::ERR_CERT_INVALID Error