# Let's encrypt container

**URL:** <https://forums.suse.com/t/lets-encrypt-container/1186>\
**Category:** Rancher 1.x\
**Created:** [December 7, 2015, 9:25am UTC](https://forums.suse.com/t/lets-encrypt-container/1186 "2015-12-07T09:25:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![zauberertz](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/zauberertz/32/310_2.png) [@zauberertz](https://forums.suse.com/u/zauberertz)\
**Post date:** [December 7, 2015, 9:25am UTC](https://forums.suse.com/t/lets-encrypt-container/1186/1 "2015-12-07T09:25:41Z")

</div>

Hi,

I’d like to implement a container that runs letsencrypt ([https://letsencrypt.org/](https://letsencrypt.org/)) to acquire certificates for my domains and renew them automatically.  
I have found the rancher API calls to add a certificate and to set a network endpoint (domain / subdomain) but I can’t find a way to list all my configured endpoints.  
I’m going to implement a letsencrypt plugin for rancher.

Do you have any suggestions for me?

Regards, Thomas

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [December 7, 2015, 5:51pm UTC](https://forums.suse.com/t/lets-encrypt-container/1186/2 "2015-12-07T17:51:39Z")

</div>

There’s an open enhancement request in Github for this.

> <https://github.com/rancher/rancher/issues/2734>
>
> It would be great to add support of the Let's encrypt project https://letsencrypt.org/
> as option in the load balancer ssl settings if...

---

<div class="post-metadata">

**Author:** ![zauberertz](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/zauberertz/32/310_2.png) [@zauberertz](https://forums.suse.com/u/zauberertz)\
**Post date:** [December 8, 2015, 3:22pm UTC](https://forums.suse.com/t/lets-encrypt-container/1186/3 "2015-12-08T15:22:26Z")

</div>

@denise Thank you for the link to the bug.

But my question was more in how do you discover the url in the route 53 container.  
I have looked in the repository and have seen that you use the rancher-metadata service but I was not able to find out how to get the url.

Regards, Thomas

---

<div class="post-metadata">

**Author:** ![pwFoo](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/pwfoo/32/2884_2.png) [@pwFoo](https://forums.suse.com/u/pwFoo)\
**Post date:** [December 30, 2015, 4:32pm UTC](https://forums.suse.com/t/lets-encrypt-container/1186/4 "2015-12-30T16:32:09Z")

</div>

Sounds interesting. I would also be interested in such a solution.

I would use Rancher LB if it would support Let’s Encrypt, but a container (catalog service? 😉) to get an certificate and add / replace it would be a great Rancher LB improvement.