# Unable to start discourse due to rubygems rate limiting

**URL:** <https://meta.discourse.org/t/unable-to-start-discourse-due-to-rubygems-rate-limiting/66381>\
**Category:** Product Support\
**Created:** [18.Июль.2017 12:00:51 UTC](https://meta.discourse.org/t/unable-to-start-discourse-due-to-rubygems-rate-limiting/66381 "2017-07-18T12:00:51Z")\
**Posts on this page:** 1\
**Showing post:** 24

<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:** [19.Июль.2017 10:04:40 UTC](https://meta.discourse.org/t/unable-to-start-discourse-due-to-rubygems-rate-limiting/66381/24 "2017-07-19T10:04:40Z")

</div>

I’ve never, ever been rate limited by rubygems during a rebuild in literally _years_ of running Discourse droplets on Digital Ocean. I wonder if AWS shares IP addresses among large numbers of machines, that would also be hitting Rubygems?

---

_[View the full topic](https://meta.discourse.org/t/unable-to-start-discourse-due-to-rubygems-rate-limiting/66381)._
