WeWP
ComparePricingFeaturesContact UsLoginTry For Free
  • Knowledge Base
  • How to Fix "Not Secure" or "Not Private" Connection Errors
  • How to Add Cron Jobs
  • Connect to Your Server via SSH on Windows
  • Keeping Servers and Sites Secure
  • Troubleshooting Cloudflare Issues
  • Install WordPress Themes and Plugins with Composer
  • How To Fix Mixed Content Issue For WordPress
  • What Is a DDoS Attack and How to Prevent It?
  • How to Enable WordPress Debug Mode
  • How to Fix the “MySQL server has gone away” Error
  • How to Configure WP Mail SMTP Plugin to Send Emails
  • How To Fix the “HSTS Missing From HTTPS Server” Error
  • How to Check Your Domain's Expiration Date
  • How to Use and Serve WebP Images in WordPress
  • Email security best practices for using SPF, DKIM, and DMARC
  • What is a LEMP (Linux, Nginx, MySql, PHP) Stack?
  • Deploying Web Applications with NGINX HTTP Server
  • How to Configure WP Rocket Plugin for WordPress
  • How to Check SPF and DKIM Records with WeWP
  • Understanding FTP vs SFTP: Which Should You Use for Secure File Transfers?
  • What is a DMARC record and How to Set it Up?
  • How to Set Up Cloudflare’s Free CDN for WordPress
  • How to check your Ubuntu version (Using the command line and GUI)
  • How to Download Backups from WeWP panel
  • How to Change the PHP Version of Your Hosting Plan
  • Troubleshooting Cloudflare Universal SSL
  • How to Fix “Your Domain Is Not Pointing” Error
  • SSH vs SSL: What’s the Difference?
  • WordPress Search and Replace
  • How to Force HTTPS on WordPress Websites
  • How to Fix a Failed Lifetime SSL Installation
  • How to Redirect HTTP to HTTPS
  • How to Monitor System Processes Using htop Command
  • Varnish vs Nginx FastCGI Cache: Which is Best for WordPress?
  • What Is the Database information_schema on phpMyAdmin?
  • How to Disable WP-Cron for Faster Performance
  • How to fix the ERR_SSL_PROTOCOL_ERROR
  • How to fix the NET::ERR_CERT_AUTHORITY_INVALID error
  • How to Add Expires Headers in WordPress
  • How to fix the “There has been a critical error on your website” error
  • How to Fix ERR_QUIC_PROTOCOL_ERROR in Chrome Browser
  • What Is Localhost? And How Does It Apply to WordPress?
  • How to Fix a Mixed Content Warning on Your Website
  • How to Fix the "Connection Timed Out" Error in WordPress
Powered by GitBook
On this page
  • What Do "Not Secure" and "Not Private" Errors Mean?
  • Causes of "Not Secure" or "Not Private" Errors
  • How to Fix "Not Secure" or "Not Private" Errors
  • Preventing "Not Secure" or "Not Private" Errors as a Website Owner
  • Conclusion:

Was this helpful?

How to Fix "Not Secure" or "Not Private" Connection Errors

When browsing the web, you may encounter warnings such as "Not Secure" or "Not Private" in your browser's address bar. These warnings indicate that the connection between your browser and the website is not encrypted or that there is an issue with the website's security certificate. This article explains the causes of these errors and provides step-by-step solutions to resolve them.

What Do "Not Secure" and "Not Private" Errors Mean?

  1. "Not Secure" Warning:

  • This warning appears when a website is using HTTP instead of HTTPS. HTTP is not encrypted, meaning any data you send or receive (e.g., passwords, credit card information) can be intercepted by attackers.

  • Modern browsers like Google Chrome, Firefox, and Microsoft Edge display this warning to alert users about potential risks.

  1. "Not Private" Warning:

  • This warning indicates an issue with the website's SSL/TLS certificate. SSL/TLS certificates are used to establish a secure, encrypted connection (HTTPS) between your browser and the website.

  • Common causes include an expired, invalid, or misconfigured certificate.

Causes of "Not Secure" or "Not Private" Errors

  1. Website Uses HTTP Instead of HTTPS:

  • The website does not have an SSL/TLS certificate installed, or it is not configured to use HTTPS.

  1. Expired or Invalid SSL/TLS Certificate:

  • The website's SSL/TLS certificate has expired or is not issued by a trusted Certificate Authority (CA).

  1. Misconfigured SSL/TLS Certificate:

  • The certificate is not properly configured for the domain or subdomain.

  1. Browser or System Date/Time Incorrect:

  • If your device's date and time are incorrect, the browser may think the certificate is invalid.

  1. Network Issues:

  • Interference from firewalls, proxies, or antivirus software can disrupt secure connections.

  1. Outdated Browser:

  • An outdated browser may not support modern security protocols or recognize newer certificates.

How to Fix "Not Secure" or "Not Private" Errors

1. Check the Website URL

  • Ensure the website URL starts with https:// instead of http://.

  • If the website only supports HTTP, avoid entering sensitive information.

2. Verify the SSL/TLS Certificate

  • Click on the padlock icon in the browser's address bar to view the certificate details.

  • Check if the certificate is valid and issued by a trusted CA.

3. Update Your Browser

  • Ensure your browser is up to date. Outdated browsers may not support modern security standards.

  • Go to your browser's settings and check for updates.

4. Check Your System Date and Time

  • Incorrect date and time settings can cause SSL/TLS errors.

  • On Windows:

  1. Right-click on the clock in the taskbar.

  2. Select "Adjust date/time."

  3. Enable "Set time automatically" and "Set time zone automatically."

  • On macOS:

  1. Go to System Preferences > Date & Time.

  2. Check "Set date and time automatically."

5. Clear Browser Cache and Cookies

  • Cached data can sometimes cause connection issues.

  • Clear your browser's cache and cookies:

  1. Open your browser settings.

  2. Navigate to "Privacy and Security."

  3. Select "Clear browsing data."

6. Disable Firewalls, Proxies, or Antivirus Temporarily

  • Security software or network settings may interfere with secure connections.

  • Temporarily disable these tools to see if the issue resolves.

  • If the error disappears, adjust the settings of your security software to allow secure connections.

7. Try a Different Network

  • Network issues, such as those caused by public Wi-Fi or corporate networks, can trigger these errors.

  • Switch to a different network (e.g., mobile hotspot) to see if the problem persists.

8. Contact the Website Owner

  • If the issue is specific to a particular website, the problem may be on their end.

  • Contact the website owner or administrator and inform them about the SSL/TLS issue.

9. Use a Different Browser or Device

  • Test the website on a different browser or device to rule out browser-specific issues.

Preventing "Not Secure" or "Not Private" Errors as a Website Owner

If you own a website, follow these steps to ensure your visitors do not encounter these errors:

  1. Install an SSL/TLS Certificate:

  • Obtain an SSL/TLS certificate from a trusted Certificate Authority (CA).

  • WeWP offers free SSL certificates via Let's Encrypt.

  1. Configure Your Website to Use HTTPS:

  • Ensure all traffic is redirected from HTTP to HTTPS.

  • Update internal links and resources to use HTTPS.

  1. Renew Certificates Before Expiry:

  • Set up reminders to renew your SSL/TLS certificates before they expire.

  1. Use a Web Application Firewall (WAF):

  • A WAF can help protect your website from attacks and ensure secure connections.

  1. Test Your Website's SSL Configuration:

Conclusion:

"Not Secure" or "Not Private" errors are important warnings that should not be ignored. By following the steps outlined above, you can resolve these errors and ensure a secure browsing experience. If you are a website owner, taking proactive measures to secure your site will help build trust with your visitors and protect their data.

PreviousKnowledge BaseNextHow to Add Cron Jobs

Last updated 2 months ago

Was this helpful?

Use tools like to check your website's SSL configuration.

SSL Labs' SSL Test