# Rubygems: Too Many Requests problem returns!

**URL:** <https://meta.discourse.org/t/rubygems-too-many-requests-problem-returns/102499>\
**Category:** Support\
**Created:** [November 21, 2018, 10:33pm UTC](https://meta.discourse.org/t/rubygems-too-many-requests-problem-returns/102499 "2018-11-21T22:33:57Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![fuerst](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fuerst/32/120729_2.png) [@fuerst](https://meta.discourse.org/u/fuerst)\
**Post date:** [December 9, 2018, 10:33am UTC](https://meta.discourse.org/t/rubygems-too-many-requests-problem-returns/102499/15 "2018-12-09T10:33:05Z")

</div>

I got around this problem by temporary limiting the server’s bandwidth using [wondershaper](https://github.com/magnific0/wondershaper). This is just a shell script which simplifies handling of iproute’s `tc` command.

Example at Ubuntu 18.04: limit bandwidth to ancient 2048 kBit download and 512 kBit upload like this:

```plaintext
wondershaper -a eth0 -d 2048 -u 512

```

Don’t forget to reset it after successfully bootstrapping Discourse:

```plaintext
wondershaper -c -a eth0

```

You just need the shell script `wondershaper` by the way. No need to install any service.

---

_[View the full topic](https://meta.discourse.org/t/rubygems-too-many-requests-problem-returns/102499)._