hello
what is your problem and why you think that cert will be the fix?
seems the cert you sent is a public one .. the previous one in the thread
email was the cert required to auth to a internal proxy
please provide context, error and messages
thanks
Alvaro.
On Thu, Oct 16, 2014 at 8:10 PM, R
Hi Jeff, can I ask you if you can share your notes on the technical steps?
(leaving out sensitive names from your company ofcourse)
I would like to have this for reference in case someone else come this
email thread from google in the future.
Thanks!
Alvaro.
On Tue, Jul 22, 2014 at 1:34 PM, Je
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
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/c
Hi Jeff,
try `set SSL_CERT_FILE=c:\temp\cacert.pem`. That works for me on Win7.
Credits to Fletcher Nichol:
https://gist.github.com/fnichol/867550
HTH, Torben
On Sat, Jul 19, 2014 at 11:03 PM, Jeff Saremi wrote:
> Windows 7
> C:\temp>Vagrant -v
> Vagrant 1.6.3
>
> C:\temp>ruby -v
> ruby 2.
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 'defaul
