You are experiencing one of the following issues
- I am getting self signed certificate in certificate chain error
- I am getting OPENSSL_internal error
Self-signed certificate in certificate chain
- If you are using a corporate firewall and/or VPN, try disabling them, or try using a different network. If you’re not able to replicate the error, it is likely that it is the VPN or proxy installed on your computer that is preventing your request from connecting to the API service.
- If you are using a self-signed certificate, make sure to add correct client certificate files (CRT, KEY, or PFX) from Settings > Certificates > Client Certificates > Add Certificate. Note: You can check for certificate data being used from the Network response pop-up or from the console as explained here.
Note: This error is usually a result of a handshake failure due to incorrect certificate files being used, which means that the server and browser were unable to establish a secure connection.
- Go to Settings > Certificates and add the correct client certificate file (PEM for CA certificates, or CRT, KEY, or PFX for self-signed certificates). You can check for certificate data being used from the Network response pop-up or from the console as explained here.
- Another potential workaround is to use the Newman CLI tool to send a request. See our GitHub repo for various options, including the ones to add client certificates.
If you are still facing issues after trying the options above, submit a support request with the result of each of the following steps in the ticket:
- Whether or not the issue persists when sending a request after toggling off Enable SSL certificate verification in the Settings tab of your request.
- Open your terminal, copy and paste each of the following commands in turn (Replace
postman-echo.comwith your API endpoint). Then share the verbose log (make sure to remove any sensitive details) for each.
curl -v -k https://postman-echo.com
openssl s_client -state -connect postman-echo.com:443 | openssl x509 -text