Hi Alvaro, The precise64 Vagrant file doesn't appear to require any plugins. This connectivity issue happens when they system needs to download and install a new plugin.
For me, it can also be reproduced with: vagrant plugin install vagrant-vbguest Its a corporate proxy. I don't have details on how our network traffic is routed in our network. Our IT department decrypts all SSL traffic, inspects it for viruses and policy compliance and then re-encrypts it using the corporate certificate authority. Our firewalls blocks the SSL version 3 protocol as well. I just need to know how to tell Vagrant to disable SSL and use TLS instead. Thanks! On Thursday, March 28, 2019 at 10:36:42 AM UTC-4, Alvaro Miranda Aguilera wrote: > > Hello > > Using this proxy and a different project does work? > > > mkdir p64 > cd p64 > vagrant init -m hashicorp/precise64 > vagrant up > > Does this work? > How do you specify the proxy? > > Thanks > Alvaro. > -- 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/17a08454-3e00-4cd9-b096-e1fe82d58e07%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
