search

tmatilai / vagrant-proxyconf

Vagrant plugin that configures the virtual machine to use proxies
MIT License
531 stars 74 forks source link

Proxy Windows 10 #226

Closed nyukers closed 4 years ago

nyukers commented 4 years ago

As for me execution "vagrant plugin install vagrant-proxyconf" is needed proxy too. Am I right?

`Installing the 'vagrant-proxyconf' plugin. This can take a few minutes... Vagrant failed to load a configured plugin source. This can be caused by a variety of issues including: transient connectivity issues, proxy filtering rejecting access to a configured plugin source, or a configured plugin source not responding correctly. Please review the error message below to help resolve the issue:

no such name (https://gems.hashicorp.com/specs.4.8.gz)

Source: https://gems.hashicorp.com/`

nyukers commented 4 years ago

set http_proxy=http://ourproxyserver:port set https_proxy=https://ourproxyserver:port vagrant plugin install vagrant-proxyconf ... C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.6.0/net/http/response.rb:122:in `error!': 407 "authenticationrequired" (Net::HTTPServerException)

chucknelson commented 4 years ago

@nyukers - Yep, you're right - while proxyconf will take care of proxy settings in your VM, it won't handle any proxy setup you may already need on your host.

C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.6.0/net/http/response.rb:122:in `error!': 407 "authenticationrequired" (Net::HTTPServerException)

Whatever proxy you're behind may require explicit authorization credentials when used by Vagrant (which is really using Ruby behind the scenes). In most cases you can use your company/school (or whatever organization's proxy you're behind) user credentials in the proxy URL, for example:

http_proxy=http://user:password@my.proxy.server:port
nyukers commented 4 years ago

Your idea is good with http_proxy=http://user:password@my.proxy.server:port. But I have error, as above, in this case too(.

codylane commented 4 years ago

@nyukers - You are using the wrong installation source.

It looks as though someone has modified your installation source to be https://gems.hashicorp.com/ instead of https://rubygems.org/. The gem vagrant-proxyconf does not exist at https://gems.hashicorp.com/ it only exists publicly at https://rubygems.org/.

Since this is a user error and not a bug with this plugin I'm afraid there isn't much further help I can provide for you.

  1. I would try uninstalling Vagrant and installing Vagrant 2.2.9 from the official hashicorp downloads.
  2. Configure your Windows machine to use proxies.
  3. Ensure your machine can reach the internet with a web browser and from the command line.
  4. Then attempt to install vagrant-proxyconf from the proper sources https://rubygems.org/.

Since your Vagrant installation has been modified and because the problem you are experiencing is not related to this plugin I would recommenced you file an issue with Vagrant for further help. Perhaps there is another user or another open issue that can help address this problem. You can open an issue here: https://github.com/hashicorp/vagrant/issues.

Please also work with your IT staff/team member/class mate if you have the luxury to do so to ensure your machine is properly setup to work behind a proxy. I know proxies are a pain and not easy to understand but the goal of this plugin is not educate the world how to use/configure proxies. Some basic understanding of your environment, it's proxy setup is needed prior to installing/using this plugin.

I'm more than happy to help you resolve errors as long as they are related to this plugin.

To keep this project on track, I'm going to close this issue as it is not related to this plugin.