Re: [vagrant-up] Re: Vagrant behind proxy - newbie question

[Geronimo Orozco]

avoid http:// just use hostnames or ips

On Thu, Aug 30, 2012 at 12:04 PM, ginzsa <gin...@gmail.com> wrote:
> Hi Avner,
>
> Sorry to bother you,
>
> I just having the same problem, with environment behind proxy, did you find
> the solution?
>
>
> Thanks..
>
>
>
> On Thursday, July 12, 2012 1:04:45 PM UTC+1, Avner Tamir wrote:
>>
>> Hi,
>>
>> I'm trying to set vagrant to run chef-solo behind proxy, according to the
>> documentation I was able to find settings should be:
>> Vagrant::Config.run do |config|
>> config.vm.box = "lucid32"
>> # Enable and configure the chef solo provisioner
>> config.vm.provision :chef_solo do |chef|
>> chef.http_proxy = "http://myproxy:8080/"
>> chef.https_proxy = "http://myproxy:8080/"
>> # We're going to download our cookbooks from the web
>> chef.recipe_url =
>> "http://files.vagrantup.com/getting_started/cookbooks.tar.gz"
>>
>> # Tell chef what recipe to run. In this case, the `vagrant_main`
>> recipe
>> # does all the magic.
>> chef.add_recipe("vagrant_main")
>>
>> end
>>
>> but I am getting the error below:
>>
>> [default] Running chef-solo...
>> stdin: is not a tty
>> /opt/vagrant_ruby/lib/ruby/1.8/net/http.rb:560:in `initialize': Connection
>> timed out - connect(2) (Errno::ETIMEDOUT)
>> from /opt/vagrant_ruby/lib/ruby/1.8/net/http.rb:560:in `open'
>> from /opt/vagrant_ruby/lib/ruby/1.8/net/http.rb:560:in `connect'
>> from /opt/vagrant_ruby/lib/ruby/1.8/timeout.rb:53:in `timeout'
>> from /opt/vagrant_ruby/lib/ruby/1.8/timeout.rb:101:in `timeout'
>> from /opt/vagrant_ruby/lib/ruby/1.8/net/http.rb:560:in `connect'
>> from /opt/vagrant_ruby/lib/ruby/1.8/net/http.rb:553:in `do_start'
>> from /opt/vagrant_ruby/lib/ruby/1.8/net/http.rb:542:in `start'
>> from /opt/vagrant_ruby/lib/ruby/1.8/open-uri.rb:242:in `open_http'
>> from /opt/vagrant_ruby/lib/ruby/1.8/open-uri.rb:616:in
>> `buffer_open'
>> from /opt/vagrant_ruby/lib/ruby/1.8/open-uri.rb:164:in `open_loop'
>> from /opt/vagrant_ruby/lib/ruby/1.8/open-uri.rb:162:in `catch'
>> from /opt/vagrant_ruby/lib/ruby/1.8/open-uri.rb:162:in `open_loop'
>> from /opt/vagrant_ruby/lib/ruby/1.8/open-uri.rb:132:in `open_uri'
>> from /opt/vagrant_ruby/lib/ruby/1.8/open-uri.rb:518:in `open'
>> from /opt/vagrant_ruby/lib/ruby/1.8/open-uri.rb:30:in `open'
>> from
>> /opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-0.10.10/bin/../lib/chef/application/solo.rb:178:in
>> `reconfigure'
>> from
>> /opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-0.10.10/bin/../lib/chef/application/solo.rb:177:in
>> `open'
>> from
>> /opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-0.10.10/bin/../lib/chef/application/solo.rb:177:in
>> `reconfigure'
>> from
>> /opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-0.10.10/bin/../lib/chef/application.rb:68:in
>> `run'
>> from
>> /opt/vagrant_ruby/lib/ruby/gems/1.8/gems/chef-0.10.10/bin/chef-solo:25
>> from /opt/vagrant_ruby/bin/chef-solo:19:in `load'
>> from /opt/vagrant_ruby/bin/chef-solo:19
>> Chef never successfully completed! Any errors should be visible in the
>> output above. Please fix your recipes so that they properly complete.
>>
>>
>> Please advice...

[Radu Micu]

Even so it is not going to work, chef solo doesn't support proxy settings as far as I know. Right?