How do I update Ruby Gems from behind a Proxy (ISA-NTLM)

Ruby Problem Overview

The firewall I'm behind is running Microsoft ISA server in NTLM-only mode. Hash anyone have success getting their Ruby gems to install/update via Ruby SSPI gem or other method?

... or am I just being lazy?

Note: rubysspi-1.2.4 does not work.

This also works for "igem", part of the IronRuby project

Ruby Solutions

Solution 1 - Ruby

For the Windows OS, I used Fiddler to work around the issue.

Install/Run Fiddler from www.fiddler2.com

Run gem:

 $ gem install --http-proxy http://localhost:8888 $gem_name

Solution 2 - Ruby

I wasn't able to get mine working from the command-line switch but I have been able to do it just by setting my HTTP_PROXY environment variable. (Note that case seems to be important). I have a batch file that has a line like this in it:

SET HTTP_PROXY=http://%USER%:%PASSWORD%@%SERVER%:%PORT%

I set the four referenced variables before I get to this line obviously. As an example if my username is "wolfbyte", my password is "secret" and my proxy is called "pigsy" and operates on port 8080:

SET HTTP_PROXY=http://wolfbyte:secret@pigsy:8080

You might want to be careful how you manage that because it stores your password in plain text in the machine's session but I don't think it should be too much of an issue.

Solution 3 - Ruby

This totally worked:

gem install --http-proxy http://COMPANY.PROXY.ADDRESS $gem_name

Solution 4 - Ruby

I've been using cntlm (http://cntlm.sourceforge.net/) at work. Configuration is very similar to ntlmaps.

gem install --http-proxy http://localhost:3128 name_of_gem

Works great, and also allows me to connect my Ubuntu box to the ISA proxy.

Check out http://cntlm.wiki.sourceforge.net/ for more information

Solution 5 - Ruby

I tried some of these solutions, and none of them worked. I finally found a solution that works for me:

gem install -p http://proxy_ip:proxy_port rails

using the -p parameter to pass the proxy. I'm using Gem version 1.9.1.

Solution 6 - Ruby

Create a .gemrc file (either in /etc/gemrc or ~/.gemrc or for example with chef gem in /opt/chef/embedded/etc/gemrc) containing:

http_proxy: http://proxy:3128

Then you can gem install as usual.

Solution 7 - Ruby

This solved my problem perfectly:

gem install -p http://proxy_ip:proxy_port compass

You might need to add your user name and password to it:

gem install -p http://[username]:[password]@proxy_ip:proxy_port compass

Solution 8 - Ruby

If you are having problems getting authenticated through your proxy, be sure to set the environment variables in exactly the format below:

set HTTP_PROXY=some.proxy.com
set HTTP_PROXY_USER=user
set HTTP_PROXY_PASS=password

The user:password@ syntax doesn't seem to work and there are also some badly named environment variables floating around on Stack Overflow and various forum posts.

Also be aware that it can take a while for your gems to start downloading. At first I thought it wasn't working but with a bit of patience they started downloading as expected.

Solution 9 - Ruby

Quick answer : Add proxy configuration with parameter for both install/update

gem install --http-proxy http://host:port/ package_name

gem update --http-proxy http://host:port/ package_name

Solution 10 - Ruby

I tried all the above solutions, however none of them worked. If you're on linux/macOS i highly suggest using tsocks over an ssh tunnel. What you need in order to get this setup working is a machine where you can log in via ssh, and in addition to that a programm called tsocks installed.

The idea here is to create a dynamic tunnel via SSH (a socks5 proxy). We then configure tsocks to use this tunnel and to start our applications, in this case:

tsocks gem install ...

or to account for rails 3.0:

tsocks bundle install

A more detailed guide can be found under:

http://blog.byscripts.info/2011/04/bypass-a-proxy-with-ssh-tunnel-and-tsocks-under-ubuntu/

Despite being written for Ubuntu the procedure should be applicable for all Unix based machines. An alternative to tsocks for Windows is FreeCap (http://www.freecap.ru/eng/). A viable SSH client on windows is called putty.

Solution 11 - Ruby

Posts abound regarding this topic, and to help others save hours of trying different solutions, here is the final result of my hours of tinkering.

The three solutions around the internet at the moment are: rubysspi apserver cntlm

rubysspi only works from a Windows machine, AFAIK, as it relies on the Win32Api library. So if you are on a Windows box trying to run through a proxy, this is the solution for you. If you are on a Linux distro, you're out of luck.

apserver seems to be a dead project. The link listed in the posts I've seen lead to 404 page on sourceforge. I search for "apserver" on sourceforge returns nothing.

The sourceforge link for cntlm that I've seen redirects to http://cntlm.awk.cz/, but that times out. A search on sourceforge turns up this link, which does work: http://sourceforge.net/projects/cntlm/

After downloading and configuring cntlm I have managed to install a gem through the proxy, so this seems to be the best solution for Linux distros.

Solution 12 - Ruby

A workaround is to install http://web.archive.org/web/20060913093359/http://apserver.sourceforge.net:80/ on your local machine, configure it and run gems through this proxy.

Install: Just download apserver 097 (and not the experimental 098!) and unpack.
Configure: Edit the server.cfg file and put the values for your MS proxy in PARENT_PROXY and PARENT_PROXY_PORT. Enter the values for DOMAIN and USER. Leave PASSWORD blank (nothing after the colon) – you will be prompted when launching it.
Run apserver: cd aps097; python main.py
Run Gems: gem install—http-proxy http://localhost:5865/ library

Solution 13 - Ruby

I am working behind a proxy and just installed SASS by downloading directly from http://rubygems.org.

I then ran sudo gem install [path/to/downloaded/gem/file]. I cannot say this will work for all gems, but it may help some people.

Solution 14 - Ruby

If you are on a *nix system, use this:

export http_proxy=http://${proxy.host}:${port}
export https_proxy=http://${proxy.host}:${port}

and then try:

gem install ${gem_name}

Solution 15 - Ruby

This worked for me in a Windows box:

set HTTP_PROXY=http://server:port
set HTTP_PROXY_USER=username
set HTTP_PROXY_PASS=userparssword
set HTTPS_PROXY=http://server:port
set HTTPS_PROXY_USER=username
set HTTPS_PROXY_PASS=userpassword

I have a batch file with these lines that I use to set environment values when I need it.

The trick, in my case, was HTTPS_PROXY sets. Without them, I always got a 407 proxy authentication error.

Solution 16 - Ruby

rubysspi-1.3.1 worked for me on Windows 7, using the instructions from this page:

http://www.stuartellis.eu/articles/installing-ruby/

Solution 17 - Ruby

Rather than editing batch files (which you may have to do for other Ruby gems, e.g. Bundler), it's probably better to do this once, and do it properly.

On Windows, behind my corporate proxy, all I had to do was add the HTTP_PROXY environment variable to my system.

Start -> right click Computer -> Properties
Choose "Advanced System Settings"
Click Advanced -> Environment Variables
Create a new System variable named "HTTP_PROXY", and set the Value to your proxy server
Reboot or log out and back in again

Depending on your authentication requirements, the HTTP_PROXY value can be as simple as:

http://proxy-server-name

Or more complex as others have pointed out

http://username:password@proxy-server-name:port-number

Solution 18 - Ruby

If you want to use SOCKS5 proxy, you may try rubygems-socksproxy https://github.com/gussan/rubygems-socksproxy.

It works for me on OSX 10.9.3.

Solution 19 - Ruby

If behind a proxy, you can navigate to Ruby downloads, click on Download, which will download the specified update ( or Gem ) to a desired location.

Next, via Ruby command line, navigate to the downloaded location by using : pushd [directory]

eg : pushd D:\Setups

then run the following command: gem install [update name] --local

eg: gem install rubygems-update --local.

Tested on Windows 7 with Ruby update version 2.4.1.

To check use following command : ruby -v

Solution 20 - Ruby

for anyone tunnelling with SSH; you can create a version of the gem command that uses SOCKS proxy:

Install socksify with gem install socksify (you'll need to be able to do this step without proxy, at least)

Copy your existing gem exe

cp $(command which gem) /usr/local/bin/proxy_gem

Open it in your favourite editor and add this at the top (after the shebang)

require 'socksify'

if ENV['SOCKS_PROXY']
  require 'socksify'
  host, port = ENV['SOCKS_PROXY'].split(':')
  TCPSocket.socks_server = host || 'localhost'
  TCPSocket.socks_port = port.to_i || 1080
end

Set up your tunnel
```
ssh -D 8123 -f -C -q -N user@proxy
```

Run your gem command with proxy_gem

SOCKS_PROXY=localhost:8123 proxy_gem push mygem

Content Type	Original Author	Original Content on Stackoverflow
Question	Brett Veenstra	View Question on Stackoverflow
Solution 1 - Ruby	Peter Moresi	View Answer on Stackoverflow
Solution 2 - Ruby	Mike Minutillo	View Answer on Stackoverflow
Solution 3 - Ruby	SethRocker	View Answer on Stackoverflow
Solution 4 - Ruby	Jason Navarrete	View Answer on Stackoverflow
Solution 5 - Ruby	kfox	View Answer on Stackoverflow
Solution 6 - Ruby	lukapiske	View Answer on Stackoverflow
Solution 7 - Ruby	HomTom	View Answer on Stackoverflow
Solution 8 - Ruby	Benjamin Wootton	View Answer on Stackoverflow
Solution 9 - Ruby	Shantonu	View Answer on Stackoverflow
Solution 10 - Ruby	Christian F	View Answer on Stackoverflow
Solution 11 - Ruby	Aaron Craig	View Answer on Stackoverflow
Solution 12 - Ruby	Jarin Udom	View Answer on Stackoverflow
Solution 13 - Ruby	Zander	View Answer on Stackoverflow
Solution 14 - Ruby	Saikrishna Rao	View Answer on Stackoverflow
Solution 15 - Ruby	Pedro García Vigil	View Answer on Stackoverflow
Solution 16 - Ruby	moonpatrol	View Answer on Stackoverflow
Solution 17 - Ruby	testworks	View Answer on Stackoverflow
Solution 18 - Ruby	Qi Luo	View Answer on Stackoverflow
Solution 19 - Ruby	ArNumb	View Answer on Stackoverflow
Solution 20 - Ruby	Mike Campbell	View Answer on Stackoverflow