# Update failing due to rate limiting by RubyGems

**URL:** <https://meta.discourse.org/t/update-failing-due-to-rate-limiting-by-rubygems/64636>\
**Category:** Support\
**Created:** [2017年六月16日 21:32 UTC](https://meta.discourse.org/t/update-failing-due-to-rate-limiting-by-rubygems/64636 "2017-06-16T21:32:40Z")\
**Posts on this page:** 1\
**Showing post:** 39

<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:** [2018年六月12日 00:37 UTC](https://meta.discourse.org/t/update-failing-due-to-rate-limiting-by-rubygems/64636/39 "2018-06-12T00:37:56Z")

</div>

It sounds like this might be a solution

> [@Unable to start discourse due to rubygems rate limiting](https://meta.discourse.org/t/unable-to-start-discourse-due-to-rubygems-rate-limiting/66381/40):
>
> Yes, and we just went to Rails 5.2, so there is lots of updates. Meta is running this new image, if the weekend goes alright I will push it to all self-hosters (and force a terminal rebuild for everyone).

---

_[View the full topic](https://meta.discourse.org/t/update-failing-due-to-rate-limiting-by-rubygems/64636)._