Re: Can't push app due to expired certificate

Mike Dalessio

Hi all,

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)>

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)>

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


On Mon, Aug 31, 2015 at 9:42 AM, Aleksey Zalesov <
aleksey.zalesov(a)> wrote:

Can you clarify how can I do this?

It is not problem of our installation SSL cert that can be skipped with

Aleksey Zalesov | CloudFoundry Engineer | Altoros
Tel: (617) 841-2121 ext. 5707 | Toll free: 855-ALTOROS
Fax: (866) 201-3646 | Skype: aleksey_zalesov | |

On 31 Aug 2015, at 16:18, Quintessence Anx <qanx(a)>

Are you able to work around the issue by skipping SSL validation?
On Aug 31, 2015 9:10 AM, "Kei YAMAZAKI" <daydream.yamazaki(a)>

Hi all,

I encountered the same problem.
The same problem has occurred even PWS.
Please fix as soon as possible.

Join to automatically receive all group messages.