# 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:** [6월 16, 2017, 9: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:** 31

<div class="post-metadata">

### Author: ![dmitry\_fedyuk](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dmitry_fedyuk/32/293153_2.png) [@dmitry\_fedyuk](https://meta.discourse.org/u/dmitry_fedyuk)
#### Post date: [8월 6, 2017, 1:55오전 UTC](https://meta.discourse.org/t/update-failing-due-to-rate-limiting-by-rubygems/64636/31 "2017-08-06T01:55:26Z")

</div>

Has anybody solved the problem?  
I have the same issue: every attempt to run `./launcher rebuild <container>` fails with the « **429 Too Many Requests** » from **[rubygems.org](http://rubygems.org)**:

 ![01](https://global.discourse-cdn.com/meta/original/3X/7/2/724e15181387741e46cd66dc03100df738aefa74.png)

Here is the only solution I have found: [The only solution I have found to workaround «429 Too Many Requests» failure from rubygems.org](https://meta.discourse.org/t/the-only-solution-i-have-found-to-workaround-429-too-many-requests-failure-from-rubygems-org/67544)

---

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