RubyGems Forward-Proxy Configuration

RubyGems has its own proxy inputs. A browser or IDE using the company proxy does not establish the endpoint selected by the gem command.

For one fetch:

gem fetch rake --http-proxy http://proxy.example:8080

Replace the endpoint with the approved service. For public gem downloads where public intermediaries are permitted, the HTTP proxy list provides candidates. This command downloads the named gem.

Repeated commands

RubyGems documents HTTP_PROXY, HTTP_PROXY_USER, and HTTP_PROXY_PASS for proxy discovery. Use the interface supported by the installed release and your environment's normal credential handling.

Existing terminals retain their environment after a persistent setting changes; a build service can have another environment again. Check the process running the failed command.

What failed?

Malformed address

Check the URI scheme, host, and port. Shell quotation and URI encoding solve different problems.

Authentication challenge

Check the required method and account form. A domain-shaped username does not add NTLM or another unsupported mechanism.

Certificate failure

Identify the certificate and trust store involved, keeping verification enabled.

Instructions for Ruby 1.8 and early RubyGems can describe different bugs and command behavior. Use the installed version's interface rather than modifying its implementation around an old workaround.

The gem source identifies where packages are published; the forward proxy identifies the route to that source. Change the setting responsible for the failed stage.