Connection is Not Private Warning in Browser when Accessing Instance

Published Date: March 2, 2026

Audience: Everyone

Products and Versions Covered: 

• Self-hosted, Replicated - KOTS

Summary

This article provides guidance on resolving the 'Connection is not private' error that can appear in browsers caused by certificate issues.

Resolution

Ensure that all certificates are updated before expiration and cover all necessary domains. This includes all certificates in the uploaded PEM chain. You can see in the information of the 'Validity' Section of the decoded certificate:

   Validity:
            Not Before: Mar 02 22:33:02 2025 GMT
            Not After : Mar 02 22:33:02 2026 GMT

The certificate will also need to cover all places you will access the application, this is usually just the Fully Qualified Domain Name, but can also include the hostname of the server:

Extensions:
kfieldsjamadomain.com, kfieldsjamadomain

Additional Resources 

• Retrieve TLS Certificate Used by Jama Connect® in Self-Hosted Environments
• KOTS: Manually Updating Admin TLS Certificate
• Success Programs
• Success Catalog
• Datasheets
• Request a Solution Offering or Training from the Success Catalog

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or improvement ideas below.