thanks for pointing me in the right direction. it’s a bug with vagrants
the workaround is on the bottom and i just confirmed it works.
On Thu Dec 18 2014 at 12:34:08 PM Daniel DeLeo firstname.lastname@example.org wrote:
On Thursday, December 18, 2014 at 10:54 AM, Ryan Kelley wrote:
using straight curl alone seems to work fine. i had a co-worker confirm
rykelley@EOS01:~$ curl -I https://opscode-omnibus-
HTTP/1.1 200 OK
Date: Thu, 18 Dec 2014 18:52:41 GMT
Last-Modified: Fri, 14 Nov 2014 02:57:44 GMT
how do i find how vagrant is calling curl ?
I poked around in the /Applications/Vagrant directory on my mac and it
looks like vagrant is bundling its own version of curl and its own
cacert.pem (though I haven’t upgraded vagrant in forever, I have 1.4.2).
Are you always seeing the errors from vagrant downloading boxes from S3
like in your original post, or do you get them during other operations as
well? If you’re only seeing errors from vagrant, it’s possible they got bit
by the Curl CA cert thing I linked. You might want to peruse their issue
tracker to see if it’s been reported and fixed.