Sorry if this is an irrelevant reply to an old post, but I also recently 
ran into pretty much the same problem.   Like you I filed a case to 
configure my corporate firewall, but I only have a moderate level of 
confidence that will be resolved to my satisfaction.  So I took it upon 
myself to hack the bundler source with more acceptable User-Agent.  I had 
asked about this problem last week on askubuntu.com, and so I've 
self-answered my question with the patch I generated:

http://askubuntu.com/questions/796526/failing-to-install-ruby-gems-required-by-vagrant-plugin-install-vagrant-proxycon/797569#797569

Hope it helps.

On Monday, December 21, 2015 at 1:30:32 PM UTC-8, Just Another Vagrant Noob 
wrote:
>
> Thanks for responding, Alvaro!
>
> I actually do a "bug" filed into IT support to configure the proxy. But 
> I'm coming up with contingency plans in case they don't come through for me.
>
> The plugin installer is actually trying to retrieve 
> http://gems.hashicorp.com/quick/Marshal.4.8/bigdecimal-1.2.6.gemspec.rz 
> when this error comes up. I can wget that URL with no problem. It seems my 
> proxy just doesn't want something that identifies itself as "bundler...." 
> to get it.
>
> On a related note, is there a way to tell the plugin installer, "Hey, 
> don't download bigdecimal-1.2.6.gemspec.rz, just use the one <here>", where 
> 'here' is a local file path?
>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/4fc51d80-6857-4968-8e96-cb33961cf96b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to