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

<div class="post-metadata">

**Author:** ![shaneoh](https://avatars.discourse-cdn.com/v4/letter/s/4af34b/32.png) [@shaneoh](https://meta.discourse.org/u/shaneoh)\
**Post date:** [18.Июль.2017 12:00:51 UTC](https://meta.discourse.org/t/unable-to-start-discourse-due-to-rubygems-rate-limiting/66381/1 "2017-07-18T12:00:51Z")

</div>

I ran some standard updates on the Ubuntu machine I have hosting my discourse instance. Now I cannot start discourse again.

I’m not a docker user, but the instructions I inherited from a previous staff member who set this up are to run:

```
./launcher stop app
./launcher rebuild data
./launcher rebuild app
./launcher start app

```

But when I run

`./launcher rebuild app`

It takes forever and finally fails. The reason for the failure seems to be below:

```
URGENT: could not connect to server: No route to host
         Is the server running on host "172.17.0.1" and accepting
         TCP/IP connections on port 5432

```

Can anyone please help with this? I’ve been messing around for hours now.

---

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