English

বাংলা
हिन्दी

English

বাংলা
हिन्दी

Appearance

Browser insecure connection ​

Symptoms ​

  • The browser shows "Not secure" or a warning before the page loads.
  • Visitors see a warning on some pages but not others.
  • Forms or logins are flagged as insecure.

Common causes ​

  • The site has no certificate installed for the address being visited.
  • Some pages or images load over http:// (mixed content).
  • The certificate does not match the exact name, for example www is missing.
  • An old cached page or old link still uses http://.

Safe initial checks ​

  1. Test both addresses in a private window: http://yourdomain.com and https://yourdomain.com.
  2. Look for mixed content in the browser's developer console. Messages name each insecure resource.
  3. Check the certificate names against the address you visit, with and without www.

Step-by-step solutions ​

  1. No certificate. Install a valid certificate for the domain. See Choosing and buying an SSL certificate.
  2. Name mismatch. Reissue or add the missing name, then reinstall. See Validation and CSR.
  3. Mixed content. Update links, scripts and images to https://, or use relative paths. See SSL and HTTPS settings.
  4. Forced HTTPS redirect. Turn on a redirect from http:// to https:// so visitors always reach the secure version.

How to confirm the issue is fixed ​

  • The address bar shows a padlock on every page, in a private window.
  • The browser console shows no mixed content warnings.

When to contact support ​

Contact support if the certificate is valid for every name you visit, and the warning still appears with clean links.

Information to include in a support ticket ​

  • The exact warning text, and a screenshot of the console message.
  • The page address and the list of insecure resources.

Last reviewed ​

2026-10-27