Skip to main content

Certificate or connection errors

If your browser refuses to open TrackMyMachines with a security or certificate warning, the problem could be your company's network. This page explains how to confirm that and what to ask your IT team to change.

What you'll see​

Your browser shows a full-page warning instead of the app, such as:

  • NET::ERR_CERT_AUTHORITY_INVALID
  • "Your connection is not private"
  • "This site can't provide a secure connection"

Tell-tale signs that it's a network problem and not our site:

  • Everyone on the same office network hits it at the same time.
  • The site loads fine on mobile data or a phone hotspot, but fails on the office WiFi or wired network.

Why it happens​

info

Our certificate is valid. The warning appears because a corporate firewall or web filter is inspecting HTTPS traffic, and it has flagged the newer trackmymachines.app domain as newly seen or "unknown intent". When a firewall treats a domain that way, it either blocks it outright or substitutes its own certificate in place of ours — and your browser rightly rejects that certificate.

We've seen this specifically on Ubiquiti (UniFi) and Sophos firewalls, but any firewall that does HTTPS/TLS inspection can behave the same way.

Confirm it's the firewall​

  1. Open the same link on mobile data (turn WiFi off on your phone, or use a hotspot). If it works there but not on the office network, the office firewall is the cause.
  2. Optionally, on the warning page, view the certificate details (click the padlock or "Not secure" indicator). If the certificate was issued by your firewall vendor rather than our real certificate authority, the connection is being intercepted.

How to fix it​

:::tip For your IT or network administrator

On the firewall / web-filtering appliance, please:

  • Allowlist the domains trackmymachines.app and *.trackmymachines.app (and *.trackmymachines.com for organisation subdomains and the API).
  • Recategorise the domain from "newly registered" / "unknown" to a trusted or business category.
  • Add an HTTPS / TLS deep-inspection (decryption) exception for those domains so the firewall stops substituting its own certificate.

:::

Once the domain is allowlisted and excluded from inspection, reload the page — the warning should be gone.

Still stuck?​

If your IT team has allowlisted the domain and you're still seeing the warning, email support@trackmymachines.com with a screenshot of the error and the certificate details, and we'll help you track it down.