Unable to communicate with websites using command prompt while attempting to use command "bundle"

[baumga34]

Hello,

I am having an issue communicating with the outside world using the command prompt.

Here is a copy of the command prompts return message after I try "bundle":

C:\OpenStudioSoftware\NREL\OpenStudio-analysis>bundle <--- Command Prompt Entry

DL is deprecated, please use Fiddle <--- Command Prompt response
Fetching source index from http://rubygems.org/
Retrying source fetch due to error (2/3): Bundler::HTTPError Could not fetch specs from http://rubygems.org/
Retrying source fetch due to error (3/3): Bundler::HTTPError Could not fetch specs from http://rubygems.org/
Could not fetch specs from http://rubygems.org/

[nllong]

This issue is typically a communication error between you and RubyGems.org. Few things to check:

1. Are you behind a proxy? If so, then check if the proxy is system wide or just your web browsers. Typically easies to open up your favorite browser and look in the settings.
2. Is there any web site restrictions at your location? If so, then it is possible that your IT department is blocking access. Note that RubyGems is only the first hurdle, you will also need access to AWS (meaning Amazon).

If you think that the above is happening. Then it is best to talk to your IT department and explain the situation. The general explanation for the "situation" is that you are trying to run a large number of simulations using Amazon Web Services. Some good questions may be:

1. How can I access the internet through a command line (or terminal) using our companies proxy?
2. When I ping aws.amazon.com, it times out, is there something that may be restricting access to the site?
3. Can we set the proxy to be machine wide, instead of just on the web browsers?
4. Can you open up unrestricted access over port 80 and 443 to *.amazon.com, *.amazonaws.com, github.com, and rubygems.org?

[rHorsey]

@baumga34 Hi there! I'm assuming from the 2014 time stamp that this issue has been resolved. If that's not the case please reopen the issues. Many thanks.