# No Certificates Generated. Let's Encrypt (Catalog version) & Load Balancing **URL:** \ **Category:** Rancher 1.x\ **Created:** [February 8, 2018, 2:55pm UTC](https://forums.suse.com/t/no-certificates-generated-lets-encrypt-catalog-version-load-balancing/9388 "2018-02-08T14:55:14Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mobicycle](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/mobicycle/32/3635_2.png) [@mobicycle](https://forums.suse.com/u/mobicycle)\ **Post date:** [February 8, 2018, 2:55pm UTC](https://forums.suse.com/t/no-certificates-generated-lets-encrypt-catalog-version-load-balancing/9388/1 "2018-02-08T14:55:15Z")
Hello. I have spent three days just trying to get my [subdomain.example.com](http://subdomain.example.com) to work using the Let’s Encrypt catalog. It still isn’t working. Here are my steps: go to the Rancher UI go to Admin =\> Settings =\> Community Catalog locate the Let’s Encrypt template in the Catalog section of the UI template version = latest (0.5.0) stack name = letsencrypt description = subdomain https I agree to the …… = yes API version = production email address = certificate name = subdomains domain names: \*.example.com domain validation method: HTTP start services after creating? no click the Launch button at the bottom of the page go to stacks select the letsencrypt stack go to “Add Service” dropdown click on the dropdown icon select Add load balancer select Always run one instance of this container on every host scale = ensure the number of instances is less than or equal to the number of hosts name = public-load-balancer description = public facing web load balancer port rules access = Public protocol = HTTP request host = \*.example.com port = 80 path = /.well-known/acme-challenge target = letsencrypt port = 80 go to the Stacks menu choose the let’s encrypt stack press the Start button wait 5 to 15 minutes go to Infrastructure go to Certificates page refresh the page (if necessary) But still no Certificates! ---
**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\ **Post date:** [February 8, 2018, 6:21pm UTC](https://forums.suse.com/t/no-certificates-generated-lets-encrypt-catalog-version-load-balancing/9388/2 "2018-02-08T18:21:41Z")
Posting the same question at the same time in multiple places (Slack) just makes it harder to follow up with you. > If you’re actually requesting `*.`, LetsEncrypt is adding support for wildcards but it’s not out yet. And it is part of the v2 API so I doubt it would start working without changes to the catalog item once it is out of testing. ---
**Author:** ![mobicycle](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/mobicycle/32/3635_2.png) [@mobicycle](https://forums.suse.com/u/mobicycle)\ **Post date:** [February 8, 2018, 6:39pm UTC](https://forums.suse.com/t/no-certificates-generated-lets-encrypt-catalog-version-load-balancing/9388/3 "2018-02-08T18:39:46Z")
Hi, I will continue the question here. I closed the Slack question. I ran the same steps again, only I changed the domain to [subdomain.example.com](http://subdomain.example.com) instead of \*.example.com but still no certificates generated… **stacks** - healthcheck - ipsec - letsencrypt - network-services - scheduler I created the load balancer off the letsencrypt stack. I am not sure if the load balancer needs its own stack? ---
**Author:** ![mobicycle](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/mobicycle/32/3635_2.png) [@mobicycle](https://forums.suse.com/u/mobicycle)\ **Post date:** [February 12, 2018, 3:59pm UTC](https://forums.suse.com/t/no-certificates-generated-lets-encrypt-catalog-version-load-balancing/9388/4 "2018-02-12T15:59:43Z")
Hi, I am going to post the question on Slack since it has been 4 days. Thanks