# 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:** 13

<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:** [18.Июль.2017 14:34:24 UTC](https://meta.discourse.org/t/unable-to-start-discourse-due-to-rubygems-rate-limiting/66381/13 "2017-07-18T14:34:24Z")

</div>

> [@zogstrip](#):
>
> Pretty sure it will unless your IP has been blacklisted. The only way to know for certain is to contact [rubygems.org](http://rubygems.org).

When I’ve contacted them I’ve gotten no response.

> [@zogstrip](#):
>
> From what I’ve seen, it only happens when using a VPS (where you don’t know what the other/previous tenants are doing) and/or when you rebuild your Discourse several times in a row in a short period of time.
> 
> FYI: we’ve never been rate limited, even when we deploy all our customers.

I can’t make rhyme or reason of the cause when I’ve been rate limited. It also doesn’t make sense that you guys have never been rate limited when I have on several occasions. Stranger still, sometimes I see the rate limit errors, but the build appears to complete successfully.

But yes, @shaneoh, it should work eventually.

---

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