# RubyGems Problem

**URL:** <https://www.ruby-forum.com/t/rubygems-problem/179160>\
**Category:** Rails\
**Created:** [November 18, 2009, 6:34pm UTC](https://www.ruby-forum.com/t/rubygems-problem/179160 "2009-11-18T18:34:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mfeadler](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/f6c823/32.png) [@mfeadler](https://www.ruby-forum.com/u/mfeadler)\
**Post date:** [November 18, 2009, 6:34pm UTC](https://www.ruby-forum.com/t/rubygems-problem/179160/1 "2009-11-18T18:34:47Z")

</div>

Hello,

I am having problems updating anything with RubyGems. For example I get  
the following errors when trying to do anything using a remote server:

studiog5:~ Matt$ gem update —system  
Updating installed gems…  
ERROR: While executing gem … (Gem::RemoteSourceException)  
HTTP Response 403

studiog5:~ Matt$ gem update rails  
Updating installed gems…  
ERROR: While executing gem … (Gem::RemoteSourceException)  
HTTP Response 403

Always the same 403 error. Any ideas?

And for the record:

studiog5:~ Matt$ gem --version  
0.9.4

Thanks!

---

<div class="post-metadata">

**Author:** ![mfeadler](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/f6c823/32.png) [@mfeadler](https://www.ruby-forum.com/u/mfeadler)\
**Post date:** [November 18, 2009, 7:26pm UTC](https://www.ruby-forum.com/t/rubygems-problem/179160/2 "2009-11-18T19:26:24Z")

</div>

1. May be “gem environment” will output something special in “REMOTE  
SOURCES”

2. I had a problem with gem repo. It was its fault. I just hat to wait  
til it was fixed.

3. May be try  
[http://programmers-blog.com/2009/04/12/ruby-gem-update-system-is-disabled-on-debian](http://programmers-blog.com/2009/04/12/ruby-gem-update-system-is-disabled-on-debian)

---

<div class="post-metadata">

**Author:** ![mfeadler](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/f6c823/32.png) [@mfeadler](https://www.ruby-forum.com/u/mfeadler)\
**Post date:** [November 18, 2009, 7:42pm UTC](https://www.ruby-forum.com/t/rubygems-problem/179160/3 "2009-11-18T19:42:31Z")

</div>

Matthew Fordham wrote:

> Hello,
> 
> I am having problems updating anything with RubyGems. For example I get  
> the following errors when trying to do anything using a remote server:
> 
> studiog5:~ Matt$ gem update —system  
> Updating installed gems…  
> ERROR: While executing gem … (Gem::RemoteSourceException)  
> HTTP Response 403
> 
> studiog5:~ Matt$ gem update rails  
> Updating installed gems…  
> ERROR: While executing gem … (Gem::RemoteSourceException)  
> HTTP Response 403
> 
> Always the same 403 error. Any ideas?
> 
> And for the record:
> 
> studiog5:~ Matt$ gem --version  
> 0.9.4

That’s an antediluvian version of gem. The current version is something  
like 1.3.5.

> Thanks!

## Best,

Marnen Laibow-Koser  
[http://www.marnen.org](http://www.marnen.org)  
removed\_email\_address@domain.invalid

---

<div class="post-metadata">

**Author:** ![mfeadler](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/f6c823/32.png) [@mfeadler](https://www.ruby-forum.com/u/mfeadler)\
**Post date:** [November 18, 2009, 10:48pm UTC](https://www.ruby-forum.com/t/rubygems-problem/179160/4 "2009-11-18T22:48:46Z")

</div>

Matthew Fordham wrote:

> Marnen Laibow-Koser wrote:
> 
> > That’s an antediluvian version of gem. The current version is something  
> > like 1.3.5.
> 
> So how should I go about updating RubyGems if it is too old to update  
> itself???

Install a new version from your package manager, or from  
[http://www.rubygems.org](http://www.rubygems.org).

> Thanks!

## Best,

Marnen Laibow-Koser  
[http://www.marnen.org](http://www.marnen.org)  
removed\_email\_address@domain.invalid

---

<div class="post-metadata">

**Author:** ![mfeadler](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/f6c823/32.png) [@mfeadler](https://www.ruby-forum.com/u/mfeadler)\
**Post date:** [November 18, 2009, 9:23pm UTC](https://www.ruby-forum.com/t/rubygems-problem/179160/5 "2009-11-18T21:23:16Z")

</div>

Marnen Laibow-Koser wrote:

> That’s an antediluvian version of gem. The current version is something  
> like 1.3.5.

So how should I go about updating RubyGems if it is too old to update  
itself???

Thanks!