# Postman CLI - ssl certificate not picked up

**URL:** <https://community.postman.com/t/postman-cli-ssl-certificate-not-picked-up/89871>\
**Category:** Help Hub\
**Tags:** client-certificate, postmancli\
**Created:** [April 14, 2026, 2:54pm UTC](https://community.postman.com/t/postman-cli-ssl-certificate-not-picked-up/89871 "2026-04-14T14:54:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![adam-cimoch-d8f487b0](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@adam-cimoch-d8f487b0](https://community.postman.com/u/adam-cimoch-d8f487b0)\
**Post date:** [April 14, 2026, 2:54pm UTC](https://community.postman.com/t/postman-cli-ssl-certificate-not-picked-up/89871/1 "2026-04-14T14:54:44Z")

</div>

I’m encountering an issue when trying to execute a Postman collection run via the CLI that requires SSL client certificates.

While I’ve successfully configured and used these `.pem` certificate and key files (`1cert.pem`, `1key.pem`) within the Postman Desktop application to send requests, the same certificates don’t seem to be picked up or utilized when I run the collection using the Postman CLI command:

```bash
postman collection run postman/collections/Scenarios 
 --environment postman/environments/test.environment.yaml
 --ssl-client-cert certs/1cert.pem 
 --ssl-client-key certs/1key.pem

```

The CLI command completes without any explicit feedback or error messages indicating an issue with the certificates, even when I intentionally provide incorrect file paths for `--ssl-client-cert` or `--ssl-client-key`.