A new cert has been pushed, and it looks like this issue is resolved. Please let me know if you're still experiencing SSL issues when downloading java-buildpack artifacts.
On Mon, Aug 31, 2015 at 11:29 AM, Mike Dalessio <mdalessio(a)pivotal.io> wrote:
Hi all,
Just an update: This affects:
* users of the "online" a.k.a. "uncached" java-buildpack, * users of the "online/uncached" ruby-buildpack 1.5.0 and later who haved opted-in to JRuby.
We're currently waiting for a new cert to be installed.
I'll obviously follow up with the java-buildpack team to make sure all the buildpacks are using the same domain for downloading artifacts.
On Mon, Aug 31, 2015 at 10:33 AM, Daniel Mikusa <dmikusa(a)pivotal.io> wrote:
I've reported this and we're working on it.
For what it's worth, this should only affect the Java build pack. I don't believe the other ones are using that URL. If you're seeing the message with other build packs, it might be because you aren't setting a specific build pack for your app (i.e. you are relying on the detect behavior of the build packs). For non-Java apps if you set a build pack with `-b` or the `buildpacks` attribute, I believe it should clear up the message.
Dan
On Mon, Aug 31, 2015 at 9:42 AM, Aleksey Zalesov < aleksey.zalesov(a)altoros.com> wrote:
Can you clarify how can I do this?
It is not problem of our installation SSL cert that can be skipped with —skip-ssl-validation.
