Hello Team,
Somehow our system is not able to save the certificate details. We can download the PEM file from the below URL. Can you please help us to find the chain.pem file so that we can get our domain up and running asap as we are not able to request a new one due to the max weekly limit.
My domain is: demo.mindmemastery.com
I ran this command: We are generating a certificate via c# library.
Thanks
[crt.sh provides the PEM file with a .crt extension]
The simplest way is to open that downloaded cert file with Windows.
Once open, you can easily follow the chain and export each of the elements.
Thanks @rg305
I imported the certificate in Windows mmc and tried to save the file there but it is always exporting with the .crt extension. I need below 3 files to use with my node js app
Can you please help a bit in more details that could save my day here 
That's even easier!
@rg305 Can you please explain?
I thought you found an easy way to get the chain from crt.sh
Did you open the cert file with Windows?
@rg305 yes but when I tried to export it is exporting with .crt extension. The snippet that I attached is the old file I have. Just tried to let you know that I need these 3 files. Can we create from the exported file from crt.sh | demo.mindmemastery.com
Did you try renaming the file?
Without the private key, which was well, private, you can't actually use the certificate, with or without a chain.
Yes but it is keeping the extension as .crt
This option also saves file with .crt extension
@rg305 this issue was due to Link and we have many domains for which max limit reached. Is there is a way to increase the limit so that we can generate new certificate?
Why would that be an issue? It's childs play to change the extension in Windows. If you don't know it yourself, it would be a very quick Google search to learn how to do it.
Not on a short term.
The easiest thing to do wait for your rate limit to expire and try again. There are workarounds such as adding a subdomain to a certificate in order to convince Let's Encrypt you're not asking for exactly the same certificate, or use a different CA (I'd imagine that's difficult if you are using an in-house developed certificate renewal system).
Thanks @webprofusion the trick given by you worked for us
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
