Certificate Problems

“Not Secure” / cert warning in browser

The CA is installed but not explicitly trusted. macOS requires a manual trust step for any locally-generated root CA:

1. Open Keychain Access, find “TonyProxy CA” (in the login keychain).
2. Double-click it → expand Trust → set When using this certificate to Always Trust.
3. Restart the app/browser you’re testing — some cache trust decisions per-process.

Certificate warning after reinstalling TonyProxy

Reinstalling generates a new CA — TonyProxy never reuses a previous CA’s key. The old trusted entry in Keychain is now for a CA that no longer matches what TonyProxy signs with.

• Remove the old “TonyProxy CA” entry from Keychain Access.
• Go to Settings → Certificate → Install again, then re-trust it (steps above).
• Repeat the install/trust step on every device you’d connected previously — they each need the new CA too.

Still failing after trusting

• Confirm you trusted the cert in the right keychain — if you have multiple TonyProxy environments installed (Dev/Sandbox/Production), each has its own CA with a distinct name (e.g. “TonyProxy CA (dev - yourhost)”), and trusting one doesn’t cover the others.
• Some apps ship their own trust store separate from the OS (common in Java, some Electron apps) — the OS-level trust step above won’t help those; the app needs the CA added to its own trust store directly.
• If the app pins certificates rather than trusting any CA, no amount of trust configuration will work — see HTTPS Decryption Issues.