Alvaro, thank you so much. that was it. I added my company's root certs to the cacert.pem and everything works now!
On Sunday, July 20, 2014 5:32:44 PM UTC-4, Alvaro Miranda Aguilera wrote: > > hello, > > The certificate is valid on the internet, if you are at a company, or you > are using a proxy, this could mean that proxy/company network is sending > you a self signed certificate > > can you open a web browser to > https://vagrantcloud.com/hashicorp/precise64 and check if you wet a green > status/closed padlock etc and check the certificate? > > real one is geotrust. > > Alvaro. > > > > On Sun, Jul 20, 2014 at 9:03 AM, Jeff Saremi <[email protected] > <javascript:>> wrote: > >> Windows 7 >> C:\temp>Vagrant -v >> Vagrant 1.6.3 >> >> C:\temp>ruby -v >> ruby 2.0.0p481 (2014-05-08) [x64-mingw32] >> >> The complete text for the error is listed below. >> The following settings did not make a difference either: >> set CURL_CA_BUNDLE=c:\temp\cacert.pem >> >> error: >> >> C:\temp>vagrant up >> Bringing machine 'default' up with 'virtualbox' provider... >> ==> default: Box 'hashicorp/precise64' could not be found. Attempting to >> find an >> d install... >> default: Box Provider: virtualbox >> default: Box Version: >= 0 >> The box 'hashicorp/precise64' 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/hashicorp/precise64";] >> Error: SSL certificate problem: self signed certificate in certificate >> chain >> More details here: http://curl.haxx.se/docs/sslcerts.html >> >> curl performs SSL certificate verification by default, using a "bundle" >> of Certificate Authority (CA) public keys (CA certs). If the default >> bundle file isn't adequate, you can specify an alternate file >> using the --cacert option. >> If this HTTPS server uses a certificate signed by a CA represented in >> the bundle, the certificate verification probably failed due to a >> problem with the certificate (it might be expired, or the name might >> not match the domain name in the URL). >> If you'd like to turn off curl's verification of the certificate, use >> the -k (or --insecure) option. >> >> -- >> 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] <javascript:>. >> 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.
