# Certbot makes ecc certificate problem

**URL:** <https://community.letsencrypt.org/t/certbot-makes-ecc-certificate-problem/29079>\
**Category:** Help\
**Created:** [March 3, 2017, 7:43am UTC](https://community.letsencrypt.org/t/certbot-makes-ecc-certificate-problem/29079 "2017-03-03T07:43:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![58458314](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/58458314/32/11699_2.png) [@58458314](https://community.letsencrypt.org/u/58458314)\
**Post date:** [March 3, 2017, 7:43am UTC](https://community.letsencrypt.org/t/certbot-makes-ecc-certificate-problem/29079/1 "2017-03-03T07:43:25Z")

</div>

Will certbot can be used to create ecc certificate? How to operate! Please help me, thank you very much!

---

<div class="post-metadata">

**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\
**Post date:** [March 3, 2017, 7:52am UTC](https://community.letsencrypt.org/t/certbot-makes-ecc-certificate-problem/29079/2 "2017-03-03T07:52:59Z")

</div>

I usually do this with one of the [alternative clients](https://letsencrypt.org/docs/client-options/), which certainly works.

With certbot I think this can only be done using certonly and specifying the csr ( which you create using an ecc key.

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [March 3, 2017, 11:00am UTC](https://community.letsencrypt.org/t/certbot-makes-ecc-certificate-problem/29079/3 "2017-03-03T11:00:37Z")

</div>

> [@58458314](#):
>
> Will certbot can be used to create ecc certificate?

Yes. There is a [Pull Request](https://github.com/certbot/certbot/pull/2660) for `certbot` to get ECC keys into the CSR (and therefore certificate). (You might even use the forked 'ecdsa' branch from that PR for yourself, although it's obviously work in progress.) But there's an ongoing discussion about the storage of the certificate. Currently, there is no difference between the filenames of the certificates despite different public key algorithms used. That's obviously very confusing, but _how_ we're going to make that distinction hasn't been decided yet.

When that decision has been made, we can start coding again and hopefully ECDSA support will be available soon.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [April 2, 2017, 11:00am UTC](https://community.letsencrypt.org/t/certbot-makes-ecc-certificate-problem/29079/4 "2017-04-02T11:00:45Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.