Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Ruby

Error install gem money

Hi, I've been searching all over the internet the past few days to try to solve this issue. Everytime I try to run gem install with anything i get the error

Could not find a valid gem 'money' (>= 0) in any repository

I pinged the server and received 100% packet lost. What do I do?

thanks for your help in advance.

5 Answers

Jason Seifer
STAFF
Jason Seifer
Treehouse Guest Teacher

Hey Ronald Quan that's a strange error. It seems that rubygems can't connect. Try doing the following:

gem update --system

Then give it another shot.

Hi Jason, thanks for responding so fast. I just tried to do what you showed me and this time I received this error... ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError) too many connection resets (http://production.s3.rubygems.org/latest_specs.4.8.gz)

Jason Seifer
STAFF
Jason Seifer
Treehouse Guest Teacher

Does downloading that linked file work for you?

It says that safari doesn't have a a available application to open it.

It says that safari doesn't have a a available application to open it.

Jason Seifer
STAFF
Jason Seifer
Treehouse Guest Teacher

Was Safari able to download the file? If so, can you try doing a gem install again?

I know this is a year late but.... I just had a similar problem installing the money gem and it turns out it is because the rubygems.org site, where the gem would be downloaded from is down. Maybe that was the problem a year ago too...