# Setting up Discourse with SSL on Docker with AWS ELB breaks and returns 503 Service Unavailable (Back-end server is at capacity)

**URL:** <https://meta.discourse.org/t/setting-up-discourse-with-ssl-on-docker-with-aws-elb-breaks-and-returns-503-service-unavailable-back-end-server-is-at-capacity/29098>\
**Category:** Self-hosting\
**Tags:** docker\
**Created:** [21. Mai 2015 um 23:52 UTC](https://meta.discourse.org/t/setting-up-discourse-with-ssl-on-docker-with-aws-elb-breaks-and-returns-503-service-unavailable-back-end-server-is-at-capacity/29098 "2015-05-21T23:52:05Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![kewubenduben](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kewubenduben/32/42675_2.png) [@kewubenduben](https://meta.discourse.org/u/kewubenduben)\
**Post date:** [22. Mai 2015 um 01:31 UTC](https://meta.discourse.org/t/setting-up-discourse-with-ssl-on-docker-with-aws-elb-breaks-and-returns-503-service-unavailable-back-end-server-is-at-capacity/29098/4 "2015-05-22T01:31:18Z")

</div>

How about not thinking it as “redirect http-\>https using ELB”?

Redirect it on the end point. Apache’s `htaccess`, Nginx `https redirect`, or App’s response header redirect.

I hope that helps.

---

_[View the full topic](https://meta.discourse.org/t/setting-up-discourse-with-ssl-on-docker-with-aws-elb-breaks-and-returns-503-service-unavailable-back-end-server-is-at-capacity/29098)._