# Certificate not generating. OpenSSL installed, restarted application

**URL:** <https://community.postman.com/t/certificate-not-generating-openssl-installed-restarted-application/27724>\
**Category:** Help Hub\
**Tags:** certificates, ssl, https\
**Created:** [September 10, 2021, 8:24pm UTC](https://community.postman.com/t/certificate-not-generating-openssl-installed-restarted-application/27724 "2021-09-10T20:24:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![suchasaltylemon](https://avatars.discourse-cdn.com/v4/letter/s/b5e925/32.png) [@suchasaltylemon](https://community.postman.com/u/suchasaltylemon)\
**Post date:** [September 10, 2021, 8:24pm UTC](https://community.postman.com/t/certificate-not-generating-openssl-installed-restarted-application/27724/1 "2021-09-10T20:24:43Z")

</div>

I am trying to read HTTPS requests through the proxy rather than the interceptor. To my understanding, after installing OpenSSL and restarting the application, Postman should be generating its own cert, but it is not generating any.

Explorer

 ![image](https://us1.discourse-cdn.com/getpostman/original/2X/0/0ce2db387f24b4ecaeed4b5348eb946e783dc418.png)

OpenSSL  
 ![image](https://us1.discourse-cdn.com/getpostman/original/2X/1/10ac9666e59f3cfa9d824994251f06516d6fe7d3.png)

It is very likely I am just misunderstanding how this works, but either way, I need help. Apologies if this question appears obvious.

---

<div class="post-metadata">

**Author:** ![Yentis](https://avatars.discourse-cdn.com/v4/letter/y/838e76/32.png) [@Yentis](https://community.postman.com/u/Yentis)\
**Post date:** [September 14, 2021, 4:05pm UTC](https://community.postman.com/t/certificate-not-generating-openssl-installed-restarted-application/27724/2 "2021-09-14T16:05:05Z")

</div>

I had the same issue but after installing the 1.1.1 version it managed to generate a certificate.

---

<div class="post-metadata">

**Author:** ![suchasaltylemon](https://avatars.discourse-cdn.com/v4/letter/s/b5e925/32.png) [@suchasaltylemon](https://community.postman.com/u/suchasaltylemon)\
**Post date:** [September 15, 2021, 4:23pm UTC](https://community.postman.com/t/certificate-not-generating-openssl-installed-restarted-application/27724/3 "2021-09-15T16:23:44Z")

</div>

Thank you for your help. Wish it made it clearer on the post. For future readers, 1.1.1L works for me: [Win32/Win64 OpenSSL Installer for Windows - Shining Light Productions](https://slproweb.com/products/Win32OpenSSL.html)

---

<div class="post-metadata">

**Author:** ![Kurmavatar](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/kurmavatar/32/3026_2.png) [@Kurmavatar](https://community.postman.com/u/Kurmavatar)\
**Post date:** [September 16, 2021, 5:29am UTC](https://community.postman.com/t/certificate-not-generating-openssl-installed-restarted-application/27724/4 "2021-09-16T05:29:06Z")

</div>

It’s a known issue that is being tracked below:

> <https://github.com/postmanlabs/postman-app-support/issues/10299>
>
> \### Is there an existing issue for this?
> 
> \- \[X\] I have searched the existing iss…ues
> 
> \### Describe the Issue
> 
> Attempting to capture requests and cookies but we do not see any ca-files listed under \`%APPDATA%\\Postman\\proxy\` even though the OpenSSL has been installed and verified.
> 
> \### Steps To Reproduce
> 
> 1) Navigate to \`%APPDATA%\\Postman\\proxy\` to find the certificate files.
> 
> !\[image\](https://user-images.githubusercontent.com/47771757/133248077-9f63af2b-a8f4-439e-8fbd-58eb366354ed.png)
> 
> 2) Install OpenSSL and verify.
> 
> !\[image\](https://user-images.githubusercontent.com/47771757/133248148-c6032ef0-3d1f-4453-9ec2-e73c061072d1.png)
> 
> 3) Reinstall the Postman app, yet the files are missing.​
> 
> \### Screenshots or Videos
> 
> \_No response\_
> 
> \### Environment Information
> 
> \`\`\`markdown
> \- Operating System: Windows
> \- Platform Type: Native App
> \- Postman Version: v.8.11.1
> \- Open SSL version: v.3.x
> \`\`\`
> 
> 
> \### Additional Context?
> 
> Note: \*\*Downgrading of OpenSSL to v.1.x \[from here\](https://slproweb.com/products/Win32OpenSSL.html) resolves the issue.\*\*
> 
> \_Filed by Product Support\_
> 
> This issue is already being tracked by the team internally, this issue is to let users who are facing a similar issues be notified upon the fix.