Help
Can't access cxmate.io?
If your browser shows “Your connection is not private” or a similar warning, here's what's happening and how to fix it.
The short answer
CX Mate's site is secure. Our SSL certificate is valid (issued by Let's Encrypt) and our infrastructure runs on Vercel with HSTS preload and full security headers. You can verify this independently at SSL Labs.
If you're seeing a security warning, it's coming from your own network or computer, not from us. Here's why.
Why this happens (NET::ERR_CERT_AUTHORITY_INVALID)
Most company networks run a security tool that inspects all HTTPS traffic for data-loss prevention. To do that, the tool replaces every website's real certificate with one signed by the company's own authority. On managed work laptops, IT installs that authority as a trusted root so the swap is invisible.
When something in that chain is missing — the laptop isn't fully managed, the root certificate didn't install, a contractor / BYOD machine — your browser sees the re-signed certificate and correctly refuses to trust it.
The warning is real for that connection, but the underlying site is fine. Visiting cxmate.io from your phone on mobile data is the fastest way to confirm.
Fixes, in order of likelihood
- Try mobile data or a personal device. If cxmate.io loads fine from your phone (not on company Wi-Fi) or a personal laptop, the issue is your work network. Continue to step 2.
- Ask IT to allow cxmate.io through SSL inspection. Send them this:
Please add
cxmate.ioand*.cxmate.ioto the SSL/TLS inspection bypass list on our proxy (Zscaler / Netskope / Check Point / Forcepoint / Palo Alto / Fortinet, etc.). The site uses a valid Let's Encrypt certificate; the bypass is needed because our endpoint device isn't presenting the corporate root CA correctly for this domain. - Check your antivirus. Kaspersky, ESET, Bitdefender, and Avast can do their own HTTPS scanning. Temporarily disable “HTTPS scanning” or “Web shield” and reload cxmate.io. If it works, your antivirus is the cause — reinstall it or update its root certificate.
- Check your system clock. If your computer's date is wrong by more than a few weeks, every site will show a certificate error. Set the clock to automatic and reload.
- Try a different browser. Firefox uses its own trust store separate from Windows. If Firefox loads cxmate.io fine but Chrome doesn't, it's a Windows root-store issue — running Windows Update usually fixes it.
Still stuck?
Email us at hello@cxmate.io with a screenshot of the error and the network you're on (office Wi-Fi, home, mobile data). We'll help you confirm whether it's an inspection proxy and give your IT team the exact bypass language.