Unable to update/install gems
I am getting the error below:
ERROR: http://rubygems.org/
does not appear to be a repository
ERROR: Could not find a valid gem 'rails' (>= 0) in any
repository
The gem env gives me the following:
RubyGems Environment:
- RUBYGEMS VERSION: 1.3.7 - RUBY VERSION: 1.8.7 (2008-08-11
patchlevel 72) [i386-mswin32] - INSTALLATION DIRECTORY:
c:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: c:/ruby/bin/ruby.exe -
EXECUTABLE DIRECTORY: c:/ruby/bin - RUBYGEMS PLATFORMS:
- ruby
- x86-mswin32-60
- GEM PATHS:
- c:/ruby/lib/ruby/gems/1.8
- Z:/.gem/ruby/1.8
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :benchmark => false
- :backtrace => false
- :bulk_threshold => 1000
- REMOTE SOURCES:
Support Staff 2 Posted by Luis Lavena on 11 May, 2011 07:44 PM
Please check your proxy settings:
http://help.rubygems.org/discussions/problems/555-problem-installim...
http://help.rubygems.org/discussions/problems/142-http-proxy-setup
Luis Lavena closed this discussion on 11 May, 2011 07:44 PM.
mgbeers re-opened this discussion on 11 May, 2011 07:54 PM
3 Posted by mgbeers on 11 May, 2011 07:54 PM
Actually this is what I've been trying to do all day. I am confused by the actual command reference, for one thing. Do I type the [no-] or is that referring to something else? I know what my http proxy server is and it's port as I have it working fine in my browser. What I've tried last:
C:>gem install heroku --http-proxy http://[the url from my browser]:8080, -p
ERROR: While executing gem ... (OptionParser::InvalidArgument)
4 Posted by Matthew Beers on 11 May, 2011 07:57 PM
I have
On Wed, May 11, 2011 at 3:45 PM, Luis Lavena <
[email blocked]> wrote:
5 Posted by Matthew Beers on 11 May, 2011 07:59 PM
I did not get much of an answer from you here and you closed the
discussion. Why? The problem isn't one that I cannot figure out how to
find the answers that you referred me to already, it's that I've already
been there, done that! You should at least give the poster a chance to
reply to that effect before closing it hastily.
On Wed, May 11, 2011 at 3:45 PM, Luis Lavena <
[email blocked]> wrote:
Support Staff 6 Posted by Luis Lavena on 11 May, 2011 09:18 PM
I did close the discussion because is a duplication of other discussion on the same thing: proxy
gem install heroku --http-proxy=http://user:password@server:port/is the correct syntax.If you had
HTTP_PROXYenvironment variable set, then --no-http-proxy will disable that.The
nopart is the negation of the first.Either you can use the
--http-proxyoption or setHTTP_PROXYenvironment variable.Please check again the command syntax and the URI syntax I shown above.
Let me know if that doesn't work.
7 Posted by Matthew Beers on 11 May, 2011 09:20 PM
Thank you for getting back to me. I will let you know, if you like.. if
this works or not. I feel like I've tried every angle though ;)
On Wed, May 11, 2011 at 5:18 PM, Luis Lavena <
[email blocked]> wrote:
8 Posted by Matthew Beers on 11 May, 2011 09:27 PM
I'm not sure why but it just doesn't work
our proxy server is like this: access.[a government org].gov:80
Support Staff 9 Posted by Luis Lavena on 11 May, 2011 09:31 PM
What protocol? HTTP?
the URL needs to be
http://access.[goverment org].gov:80/It is important the format.
Please provide a Pastie or Gist that shows the full output of the command:
gem install heroku --http-proxy=http://access.[a government org].gov:80/ --debug -V10 Posted by Matthew Beers on 11 May, 2011 09:40 PM
pastie:
http://pastie.org/1890714
On Wed, May 11, 2011 at 5:31 PM, Luis Lavena <
[email blocked]> wrote:
11 Posted by Matthew Beers on 11 May, 2011 09:41 PM
updated the pastie so as not to reveal the actual domain or organization.
Support Staff 12 Posted by Luis Lavena on 11 May, 2011 09:43 PM
You're getting a Forbbiden (403) response from the proxy:
This is most likely because the proxy requires an username and a password that you aren't providing in the URI for http-proxy.
Please see my previous comment on the URI structure for http proxy, add your username and password and try again.
Support Staff 13 Posted by Luis Lavena on 11 May, 2011 09:44 PM
BTW, is completely irrelevant for what organization you work for, what matters is help you solve the issue, which seems to be associated with not authorized proxy.
14 Posted by Matthew Beers on 11 May, 2011 09:44 PM
Ok i will try that, not sure if I have the right format for it since our
logins are domain\username
On Wed, May 11, 2011 at 5:43 PM, Luis Lavena <
[email blocked]> wrote:
Support Staff 15 Posted by Luis Lavena on 23 May, 2011 09:37 PM
Hello,
I haven't heard back from you you in 2 weeks. Did you manage to solve the correct URI of your corporate proxy?
Please respond to this and let us know.
Going to close this in a few days if no response is given.
Thank you.