--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAN3hOS8s_1NO92RqpfxoXr85O04BotnErOR9Bh1eyKcZ67CfdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Correct. The new cert is missing mirror.bazel.build. I've rolled back to the old cert; it might take a few minutes for it to propagate through the load balancers. LMK if you still see issues after that. Thanks and sorry for the interruption.
On Wed, Nov 1, 2017 at 10:03 AM John Cater <jca...@google.com> wrote:
We just noticed this, and we're switching back to the previous cert while we iron it out.
On Wed, Nov 1, 2017 at 10:01 AM 'Damien Martin-Guillerez' via bazel-discuss <bazel-discuss@googlegroups.com> wrote:
+David--On Wed, Nov 1, 2017, 2:52 PM Ian O'Connell <ia...@stripe.com> wrote:Hi,it looks like some cert changes have happened for mirror.bazel.buildhttps://mirror.bazel.build/repo1.maven.org/maven2Certificate for <mirror.bazel.build> doesn't match any of the subject alternative names: [bazel.build, be.bazel.build, blog.bazel.build, ci.bazel.build, ci-staging.bazel.build, conf.bazel.build, cr.bazel.build, cs.bazel.build, docs.bazel.build, e4b.bazel.build, eclipse.bazel.build, ij.bazel.build, pantry.bazel.build, perf.bazel.build, skydoc.bazel.build, skylark.bazel.build, tulsi.bazel.build, www.bazel.build]Looks like i think the cert was updated today and doesn't contain an entry suggesting its valid for the mirror sub domain?
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discuss+unsubscribe@googlegroups.com.
The roll back did the job, thanks for the quick fix!Ian.
On Wed, Nov 1, 2017 at 10:08 AM, Dave Stanke <david...@google.com> wrote:
Correct. The new cert is missing mirror.bazel.build. I've rolled back to the old cert; it might take a few minutes for it to propagate through the load balancers. LMK if you still see issues after that. Thanks and sorry for the interruption.
On Wed, Nov 1, 2017 at 10:03 AM John Cater <jca...@google.com> wrote:
We just noticed this, and we're switching back to the previous cert while we iron it out.
On Wed, Nov 1, 2017 at 10:01 AM 'Damien Martin-Guillerez' via bazel-discuss <bazel-...@googlegroups.com> wrote:
+David--On Wed, Nov 1, 2017, 2:52 PM Ian O'Connell <ia...@stripe.com> wrote:Hi,it looks like some cert changes have happened for mirror.bazel.buildhttps://mirror.bazel.build/repo1.maven.org/maven2Certificate for <mirror.bazel.build> doesn't match any of the subject alternative names: [bazel.build, be.bazel.build, blog.bazel.build, ci.bazel.build, ci-staging.bazel.build, conf.bazel.build, cr.bazel.build, cs.bazel.build, docs.bazel.build, e4b.bazel.build, eclipse.bazel.build, ij.bazel.build, pantry.bazel.build, perf.bazel.build, skydoc.bazel.build, skylark.bazel.build, tulsi.bazel.build, www.bazel.build]Looks like i think the cert was updated today and doesn't contain an entry suggesting its valid for the mirror sub domain?
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.