πŸ“„
Webhosting

Fixing Browser SSL Warnings: Causes & Solutions

πŸ“… 9 October 2026 ✏️ 9 October 2026 ⏱ 4 min leestijd

Browser showing ‘not secure’ or an SSL warning? Discover the most common causes and how to fix them step by step.

Getting a message in Chrome, Firefox, or Safari that your connection isn’t private or secure, even though you thought your SSL certificate was fine? This is almost always caused by one of a few recognizable issues: an expired or incorrectly installed certificate, a name that doesn’t match your domain, mixed content, or an outdated certificate chain. In this article, you’ll go step by step through where things go wrong and how to fix them.

What the SSL warning actually means

Every time a browser visits a website, it checks whether the SSL/TLS certificate is valid, trusted, and matches the domain. If something’s wrong, the browser shows a warning such as ‘Your connection is not private’ or ‘NET::ERR_CERT_AUTHORITY_INVALID’. This isn’t a message visitors can simply click away: it’s off-putting and can even prevent search engines from properly indexing your site.

Browser→Certificate→Server

The browser checks the certificate before marking the connection as secure.

The 5 most common causes

Before looking for a solution, it’s useful to know which cause is most likely behind your warning.

  • Name mismatch: the certificate was issued for example.com, but you’re visiting www.example.com (or vice versa), without both variants being included.
  • Expired certificate: SSL certificates have a limited validity period and aren’t always renewed automatically.
  • Incomplete certificate chain: the server only sends its own certificate, without the associated intermediate certificates.
  • Mixed content: the page itself loads via HTTPS, but contains images, scripts, or stylesheets that are still fetched via HTTP.
  • Wrong server or configuration: the certificate is installed on the wrong domain or subdomain, or the DNS (still) points to a different server.
πŸ’‘ Tip: First ask yourself whether the warning occurs for all visitors, or only for you. In the latter case, it could also be due to an outdated browser cache or system clock.

Step-by-step checking and fixing

1

Check the certificate’s validity

Click the padlock icon next to the address bar in your browser and review the certificate details: which domain was it issued for, and until when is it valid?

2

Compare domain name with certificate

Make sure both the domain without www and with www are covered, or use a certificate that supports both variants.

3

Check for mixed content

Open the browser console (developer tools) and look for warnings about insecure resources still loading via HTTP.

4

Reinstall or renew the certificate

In Plesk, go to the SSL/TLS certificate for your domain and reinstall it or request a new free certificate. Also check that the full certificate chain is included.

5

Test again in an incognito window

Open your site in a private window to make sure you’re not seeing an outdated cache from your own browser.

Are you stuck because your domain was recently moved or the DNS isn’t set up correctly yet? Read more about how to manage domain names and their settings, or find out how switching to Tandata works if you’re considering a new hosting environment.

How to prevent this in the future

Most SSL warnings can be prevented by setting a few things up properly from the start. Make sure your certificate renews automatically instead of manually, preferably use a single certificate that covers both the main domain and www, and after every major change to your website (such as a new theme or plugin), check that all resources load via HTTPS. A quick periodic check via the padlock icon in the browser takes little time and prevents unpleasant surprises for your visitors.

πŸ’‘ Tip: In Plesk, you can see at a glance whether a certificate is about to expire and whether automatic renewal is active, so you’re never caught off guard.

Frequently Asked Questions

Why do I only see the warning on my own computer?

This often points to an outdated browser cache, an incorrect system clock, or local DNS settings still pointing to an old server. Test the site on another device or network to rule this out.

Can a free SSL certificate offer the same protection as a paid certificate?

In terms of encryption, there’s no difference: both use the same technical standards. The difference mainly lies in extra validation levels and additional guarantees that come with some paid certificates.

Does my SSL certificate also work for subdomains?

Only if the certificate was specifically issued for that subdomain or as a wildcard. A standard certificate for your main domain doesn’t automatically cover subdomains.

Conclusion

An SSL warning is usually caused by a domain name mismatch, an expired certificate, an incomplete certificate chain, or mixed content. Check the certificate via the padlock icon in your browser, look for insecure resources, and reinstall the certificate in Plesk where needed. With automatic renewal and a properly configured certificate, you can prevent this structurally.

View web hosting β†’

Was dit artikel nuttig?