← RetroEP · English · Türkçe

Connection not private / SSL errors

retroep.com serves a valid public TLS certificate (Let's Encrypt, RSA 2048). The live chain cross-signs to ISRG Root X1 (the widely trusted anchor in Windows, macOS, Firefox, and Chrome). Hostnames: retroep.com, www.retroep.com.

Why Chrome shows NET::ERR_CERT_AUTHORITY_INVALID

On managed corporate PCs this error is usually not a server misconfiguration. Common causes:

Quick test (takes 2 minutes)

  1. Open https://retroep.com/ on mobile data (not office Wi‑Fi).
  2. If it loads on mobile but fails on office network → corporate proxy/inspection is the cause.
  3. Also try Let's Encrypt ISRG Root X1 test site. If that fails too, the device trust store or proxy is blocking Let's Encrypt generally.

What to send your IT / security team

What you can do locally

Verify our certificate (openssl)

openssl s_client -connect retroep.com:443 -servername retroep.com </dev/null 2>/dev/null | openssl x509 -noout -subject -issuer -dates

Expected: subject=CN=retroep.com, issuer contains Let's Encrypt.

Still blocked?

Share this page URL with IT. RetroEP is a client-side retrospective board; no special ports beyond HTTPS (443). If inspection cannot be disabled, installing the corporate root CA on the workstation is the standard fix.