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

Bug
1

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

If you use 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.

2

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?

3 Likes
3

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

4

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

3 Likes