# Let's Encrypt won't work with a mixed-case domain name

**URL:** <https://meta.discourse.org/t/lets-encrypt-wont-work-with-a-mixed-case-domain-name/101707>\
**Category:** Bug\
**Created:** [November 10, 2018, 12:13am UTC](https://meta.discourse.org/t/lets-encrypt-wont-work-with-a-mixed-case-domain-name/101707 "2018-11-10T00:13:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [November 10, 2018, 12:13am UTC](https://meta.discourse.org/t/lets-encrypt-wont-work-with-a-mixed-case-domain-name/101707/1 "2018-11-10T00:13:20Z")

</div>

I think that I’ve said this before, but I can’t find ti.

If you use [MyCoolDomain.com](http://MyCoolDomain.com) and turn on Let’s Encrypt you get stuck in a redirect loop, as something downcases the name and something else wants the mixed case name.

We should change `discourse-setup` (me), `launcher` (@sam), or `web.letsencrypt.ssl.template.yml` (@tgxworld) so that people can’t shoot themselves in the foot.

---

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [November 10, 2018, 3:23am UTC](https://meta.discourse.org/t/lets-encrypt-wont-work-with-a-mixed-case-domain-name/101707/2 "2018-11-10T03:23:09Z")

</div>

Domains aren’t case-sensitive, why would we enter any upper case characters in that field?

Surely this is a bug, rather than a feature?

---

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [November 10, 2018, 4:19am UTC](https://meta.discourse.org/t/lets-encrypt-wont-work-with-a-mixed-case-domain-name/101707/3 "2018-11-10T04:19:55Z")

</div>

I think that it’s nginx that’s the one redirecting.

---

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [November 10, 2018, 4:27am UTC](https://meta.discourse.org/t/lets-encrypt-wont-work-with-a-mixed-case-domain-name/101707/4 "2018-11-10T04:27:18Z")

</div>

So we just knock any input down to lower case during discourse setup? Seems like a bug with an easy fix?