# 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:** [2015 年5 月 21 日 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:** 2

<div class="post-metadata">

作者： ![mshappe](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mshappe/32/104819_2.png) [@mshappe](https://meta.discourse.org/u/mshappe)\
发布日期： [2015 年5 月 22 日 00:10 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/2 "2015-05-22T00:10:34Z")

</div>

If you’re using HTTPS via ELB, you **do not** need to use it within the Docker or Discourse. Have your ELB back-end to HTTP/80 and let it handle all the HTTPS proxying itself.

Put another way: as far as Discourse and Docker are concerned, they’re still just HTTP. ELB will act as a secure proxy, using the key you set up under AWS.

---

_[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)._