Mets Minor League Blog

Music theory, instruments and musicians

Mets Minor League Blog

Music theory, instruments and musicians

How to Fix a Not Secure Website in Chrome

By metsPosted on Posted in Sport Gear

How to Fix a Not Secure Website in Chrome

Seeing a “Not Secure” warning when visiting your website can deter visitors and harm your site’s credibility. This guide will walk you through the steps to fix this issue, ensuring your website is safe and trustworthy in Chrome. Before starting, make sure you have access to your website’s hosting account or server, and the ability to modify its SSL/TLS settings. Having a basic understanding of SSL certificates and your website’s backend will make the process smoother.

What You’ll Need

  • Access to your website hosting control panel or server
  • Ability to install or manage SSL certificates
  • Basic knowledge of your website platform (e.g., WordPress, HTML, etc.)
  • Optional: a valid SSL certificate (free or paid)

Step-by-Step

  1. Check Your Current SSL Status: Open Chrome and visit your website. Click the padlock icon in the address bar to view certificate details. If it shows “Not Secure” or no SSL info, proceed to the next step.
  2. Obtain an SSL Certificate: If your site lacks an SSL certificate, you’ll need to acquire one. Many hosting providers offer free SSL certificates via Let’s Encrypt. Log into your hosting control panel and locate the SSL/TLS section.
  3. Install the SSL Certificate: Follow your hosting provider’s instructions to install the SSL certificate. This often involves selecting your domain and clicking an install button. If installing manually, generate a CSR (Certificate Signing Request) and submit it to your SSL provider, then upload the issued certificate.
  4. Configure Your Website to Use HTTPS: After installing the SSL, ensure your website loads over HTTPS. Update your website URLs in your platform settings or configuration files to start with https:// instead of http://.
  5. Redirect HTTP to HTTPS: To prevent visitors from accessing your site via the insecure HTTP link, set up a redirect. For example, add the following code to your .htaccess file if using Apache: 
    RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://yourdomain.com/$1 [R=301,L]

    Alternatively, many hosting providers offer a toggle to enforce HTTPS automatically.

  6. Update Internal Links and Resources: Ensure all internal links, images, scripts, and stylesheets use HTTPS URLs. This prevents mixed content warnings, which can cause the “Not Secure” message even after installing SSL.
  7. Clear Cache and Test: Clear your browser cache and revisit your site. Confirm the padlock icon appears without warnings. Use online tools like SSL Labs’ SSL Server Test to verify your SSL configuration.

Common Mistakes

  • Not installing a valid SSL certificate — using self-signed certificates can cause warnings.
  • Forgetting to redirect HTTP traffic to HTTPS, leading to mixed content issues.
  • Not updating internal links to HTTPS, which can still trigger security warnings.
  • Using outdated SSL protocols or weak ciphers, compromising security.
  • Failing to renew or update the SSL certificate before expiration.

Tips

  • Always use a trusted SSL provider like Let’s Encrypt or a commercial SSL vendor.
  • Set up automatic renewal for your SSL certificates to avoid expiration issues.
  • Use tools like Qualys SSL Labs to test your SSL setup regularly.
  • Update your website platform and plugins to support the latest security standards.
  • Inform your team or developers about the importance of HTTPS and secure content.

Troubleshooting

If your website still shows as “Not Secure” after following these steps, consider the following:

  • Clear browser cache and cookies: Sometimes, cached data can cause outdated warnings. Clear your cache and revisit the site.
  • Check for mixed content: Use browser developer tools (F12) to identify resources loaded over HTTP. Update these to HTTPS.
  • Verify SSL installation: Use online SSL checkers like SSL Labs to confirm your certificate is correctly installed and trusted.
  • Ensure redirect rules are correct: Misconfigured redirects can cause loops or warnings. Double-check your server settings.
  • Update your DNS records: Make sure your domain points to the correct server with the SSL installed.
  • Consult your hosting provider: If issues persist, contact your host for support or guidance.

Frequently Asked Questions

1. Why does my website show “Not Secure” even after installing SSL?

This often happens due to mixed content—some resources like images, scripts, or stylesheets are loaded over HTTP. Updating all links to HTTPS usually fixes this.

2. Can I get a free SSL certificate?

Yes, providers like Let’s Encrypt offer free SSL certificates that are trusted by most browsers. Many hosting providers also include free SSL options.

3. How long does it take to install an SSL certificate?

Installation can be quick—usually within a few minutes to an hour—depending on your hosting provider and whether you’re installing manually or automatically.

4. Is it necessary to renew my SSL certificate?

Yes, SSL certificates have expiration dates, typically every 90 days to 1 year. Set up automatic renewal whenever possible to avoid lapses in security.

5. Will fixing SSL issues improve my website’s SEO?

Yes, Google favors secure websites, and having HTTPS can boost your search rankings and improve user trust.

6. What if I don’t see the padlock after fixing SSL?

Clear your browser cache, ensure all resources load over HTTPS, and verify your SSL installation with online tools. Sometimes, browser cache causes stale warnings.

Related

How to Fix a Not Secure Website in Chrome
Scroll to top