Hi, The box is loaded on the host, while vagrant-proxyconf currently only configures the guest. I’ve planned adding some host side support too, but untill then you need to specify the standard HTTP_PROXY and HTTPS_PROXY environment variables on the host yourself.
On May 12, 2014 at 18:27:47, NitinVerma ([email protected]) wrote: Nothing works for me behind corp proxy: # pwd /cygdrive/c/cygwin/home/vagrant_home # echo $VAGRANT_HTTP_PROXY http://172.19.243.11:8090 # tail Vagrantfile # chef.validation_client_name = "ORGNAME-validator" # Setup Proxy Vagrant.configure("2") do |config| if Vagrant.has_plugin?("vagrant-proxyconf") config.proxy.http = "http://172.19.243.11:8090/"; config.proxy.no_proxy = "localhost,127.0.0.1" end end # end # vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Box 'puppetlabs/centos-6.5-64-puppet' could not be found. Attempting to find and install... default: Box Provider: virtualbox default: Box Version: >= 0 The box 'puppetlabs/centos-6.5-64-puppet' could not be found or could not be accessed in the remote catalog. If this is a private box on Vagrant Cloud, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://vagrantcloud.com/puppetlabs/centos-6.5-64-puppet";] Error: Failed connect to vagrantcloud.com:443; Timed out # vagrant plugin list vagrant-login (1.0.1, system) vagrant-proxyconf (1.3.1) vagrant-share (1.0.1, system) # vagrant -v Vagrant 1.6.0 # Pls advise. On Tuesday, March 16, 2010 7:47:00 PM UTC+11, Mitchell Hashimoto wrote: Russell, While this works, it could be nice to also build in HTTP proxy support straight into Vagrant since Net::HTTP seems to support it. I'll keep this in mind for the future. Mitchell On Tue, Mar 16, 2010 at 1:45 AM, Russell <[email protected]> wrote: Hi, Thanks for the response. In the end that is what I did (downloaded with browser and used local box). Thanks again Russell On Mar 15, 5:33 pm, John Bender <[email protected]> wrote: > Russel, > > You're link was translated oddly so its hard to tell whats happening, but if > the company firewall doesn't let the tool access the site to download the > base box (which is what I assume is failing) you can download it manually > and use the local file. > > Just hit > > http://files.vagrantup.com/base.box > > in your web browser and save the file to somewhere you'll remember. With > that done you can issue: > > vagrant box add base path/to/your/base.box > > And continue on with the quick start. Hope that helps. > > Best > > John > > > > On Mon, Mar 15, 2010 at 8:24 AM, Russell <[email protected]> wrote: > > Hi, > > In corporate firewall hell all http traffic goes through an http proxy > > that requires authentication. I added an HTTP_PROXY env var so that > > rubygems would work, what do I need to do to make vagrant box add > >http://xxxxxxxxxwork, please? > > > Many thanks in advance > > > Russell -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
