# Too many redirects after enabling https

**URL:** https://meta.discourse.org/t/too-many-redirects-after-enabling-https/92338
**Category:** Self-hosting
**Created:** [July 14, 2018, 5:09am UTC](https://meta.discourse.org/t/too-many-redirects-after-enabling-https/92338 "2018-07-14T05:09:37Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![KevinWorkman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kevinworkman/32/122364_2.png) [@KevinWorkman](https://meta.discourse.org/u/KevinWorkman)
#### Post date: [July 14, 2018, 5:09am UTC](https://meta.discourse.org/t/too-many-redirects-after-enabling-https/92338/1 "2018-07-14T05:09:37Z")

</div>

I’m trying to enable https on an existing forum using this guide: [Set up HTTPS support with Let's Encrypt](https://meta.discourse.org/t/setting-up-lets-encrypt/40709)

I ran `./discourse-setup` and entered my email address for Let’s Encrypt, and then rebuilt the app.

However, now when I visit my server I’m getting this errors:

```plaintext
forum.happycoding.io redirected you too many times.
ERR_TOO_MANY_REDIRECTS

```

I’ve manually inspected `app.yml` and it appears that all of my settings are correct. I’m not using cloudflare or anything.

Is there a step I’m missing? Is there something special I need to consider when running my discourse on a subdomain?

As always, thanks for your time, and I appreciate any help anybody can offer!

---

<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: [July 14, 2018, 5:31am UTC](https://meta.discourse.org/t/too-many-redirects-after-enabling-https/92338/2 "2018-07-14T05:31:07Z")

</div>

I’m not sure what the problem could be. Could you try the unannounced discourse doctor and see if it sheds light?

```
git pull
./discourse-doctor

```

---

<div class="post-metadata">

### Author: ![KevinWorkman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kevinworkman/32/122364_2.png) [@KevinWorkman](https://meta.discourse.org/u/KevinWorkman)
#### Post date: [July 14, 2018, 5:30pm UTC](https://meta.discourse.org/t/too-many-redirects-after-enabling-https/92338/3 "2018-07-14T17:30:23Z")

</div>

As always it turns out that I’m an idiot. I had some upper-case letters in my domain (`forum.HappyCoding.io`). Modifying the `app.yml` file to only user lower-case letters (`forum.happycoding.io`) solved the problem.

I noticed this when I looked at the output for `disocurse-doctor`, so thanks very much!

Btw, I found a similar thread with a similar problem [here](https://meta.discourse.org/t/too-many-redirects-setting-up-lets-encrypted/55346).

---

<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: [July 14, 2018, 5:44pm UTC](https://meta.discourse.org/t/too-many-redirects-after-enabling-https/92338/4 "2018-07-14T17:44:11Z")

</div>

Great! That’s what it’s supposed to do!

Was it just printing the configuration information or was it something else?

---

<div class="post-metadata">

### Author: ![KevinWorkman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kevinworkman/32/122364_2.png) [@KevinWorkman](https://meta.discourse.org/u/KevinWorkman)
#### Post date: [July 14, 2018, 7:28pm UTC](https://meta.discourse.org/t/too-many-redirects-after-enabling-https/92338/5 "2018-07-14T19:28:08Z")

</div>

Yeah, the `discourse-doctor` tool printed out the config data, which is where I saw the upper-case letters. That coupled with seeing [this post](https://meta.discourse.org/t/too-many-redirects-setting-up-lets-encrypted/55346) and remembering encountering [another problem](https://meta.discourse.org/t/embedded-comments-iframe-height/51129) with upper-case letters finally clicked everything into place in my brain.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [July 14, 2018, 9:44pm UTC](https://meta.discourse.org/t/too-many-redirects-after-enabling-https/92338/6 "2018-07-14T21:44:30Z")

</div>

Maybe you can extend doctor to warn, or we can add a stop warning in setup, when people put uppercase characters in the domain name?

---

<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: [July 15, 2018, 5:20am UTC](https://meta.discourse.org/t/too-many-redirects-after-enabling-https/92338/7 "2018-07-15T05:20:15Z")

</div>

Or launcher could downcase the domain main name.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [July 15, 2018, 8:04am UTC](https://meta.discourse.org/t/too-many-redirects-after-enabling-https/92338/8 "2018-07-15T08:04:04Z")

</div>

Sure, whatever works and is easy!

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [August 14, 2018, 8:04am UTC](https://meta.discourse.org/t/too-many-redirects-after-enabling-https/92338/9 "2018-08-14T08:04:20Z")

</div>

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