# 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:** [June 16, 2017, 9:32pm 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:** 23

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [June 16, 2017, 11:12pm UTC](https://meta.discourse.org/t/update-failing-due-to-rate-limiting-by-rubygems/64636/23 "2017-06-16T23:12:58Z")

</div>

1. If you get rate-limited by rubygems, **you need to talk to rubygems**. They explain how in [their rate-limiting documentation](http://guides.rubygems.org/rubygems-org-api/#rate-limits). We can do absolutely nothing to help with rate-limiting problems. (This doesn’t just apply to the OP; everyone giving advice on this problem any time it occurs needs to refer people to rubygems, loudly, explicitly, and using words of no more than two syllables.)

2. I can’t see any specific error messages relating to the dropbox plugin in this thread. Without a complete error message and backtrace (if displayed in the logs), @Falco isn’t going to be able to do anything to fix whatever error might be going wrong.

---

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