You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the issue! Anyway this is duplicate for #53. Please read more information there, but the problem with this is that depending on the vagrant command, it's possible that the (project's) Vagrantfile or even the plugin is not loaded. And another issue is that if people use Vagrant and the proxyconf plugin mainly with cloud providers like vagrant-aws, the proxy configuration might be totally different than on the workstation.
But before we get to implement #53 in some form, you can yourself set HTTPS_PROXY (and HTTP_PROXY) environment variables. Vagrant will use them when downloading boxes, plugins, etc.
Having vagrantcloud boxes, vagrant does not use the configured proxy, and instead attempts direct connection to vagrant cloud.
Netstat:
ec2-107-23-113-67.com:https SYN_SENT
Vagrant:
Error: Failed connect to vagrantcloud.com:443; Connection timed out
Expected:
Requests should use the configured proxy by proxyconf plugin.
The text was updated successfully, but these errors were encountered: