How to Eliminate Browser “Not Secure” Warnings with Self‑Signed Certificates on Windows

Background

In today’s digital era, every online interaction relies on trust, and a browser warning that a site is “not secure” instantly erodes that trust. For many small‑and‑medium enterprises, buying expensive SSL certificates is not feasible, but a properly configured self‑signed certificate can resolve the warning and improve user confidence.

Current Situation

Test environments often use ingress + cert‑manager to generate certificates automatically, which saves maintenance time but still triggers “not secure” alerts in browsers.

Tip

For detailed ingress and cert‑manager configuration, refer to the article “cert‑manager: Kubernetes Certificate Request Practical Guide”.

Solution Overview

The following steps show how to create and import a self‑signed certificate on Windows using the MMC console.

Step 0: Prepare

Open the MMC console and add the Certificate snap‑in.

Open MMC Press Win+R , type mmc , and click OK.

Add Certificate Snap‑in In the MMC console, choose File → Add/Remove Snap‑in… , select Certificates , and click Add.

Select Store Choose Computer account , then Local computer , and finish.

Step 1: Import the Certificate

Open Trusted Root Certification Authorities

Add the Certificate Right‑click All Tasks → Import… and launch the Certificate Import Wizard.

Specify File Browse to the .cer file, click Next.

Choose Store Location Select the appropriate store (e.g., Trusted Root Certification Authorities) and click Next.

Finish Import Confirm the security warning and complete the wizard.

Conclusion

Using self‑signed certificates is an economical and effective way to eliminate browser “not secure” warnings, especially for budget‑constrained SMEs. While they may not provide the same level of trust as commercial certificates, they are suitable for internal or testing environments. Proper security practices and user education can further enhance site safety and brand confidence.