> Paste a TLS certificate error from curl, OpenSSL, Java, Python, Node.js, Go, .NET, Chrome or Firefox and get the page that explains and fixes it. Source: https://pkizerotohero.com/tools/error-finder/ Browser tool # Paste your error Paste a certificate error from any tool, browser or log. We match it against our error pages and show the ones that explain it. Nothing you paste leaves your browser. *Interactive tool: Paste your error (runs in the browser at [/tools/](https://pkizerotohero.com/tools/))* ## How to use it 1. Copy the error from your terminal, log or browser. The whole message or a stack trace is fine. 2. Paste it into the box. Matching pages appear as you type, the closest first. 3. Open the page, check the likely causes in order, and use the matching tool to check your certificate or chain. ## Questions My error is not found. What now? Pick your tool from the list: each page also lists other messages the same problem produces. Most certificate errors come from a few causes: a missing intermediate, a root the client does not trust, a name that is not in the certificate, or a date outside the validity period. Is it safe to paste an error message? The matching runs in your browser and nothing is sent anywhere. Still, remove passwords and tokens from logs before you paste them anywhere. ## Learn what it checks - [Certificate chains and path validation](https://pkizerotohero.com/handbook/certificate-chains/) - [Who do we trust? CAs, trust stores and self-signed certificates](https://pkizerotohero.com/handbook/trust-stores/)