This is resolved. The certificate provided for pypy.org was “forgotten” by the chef configuration on the load balancers in our OSUOSL infrastructure. It appears that some tidy up work I performed in removing old hosts inadvertently disrupted the delicate balance.
I’ve rerun chef a couple times to ensure that the changes are stable and it seems TLS is back in action for pypy.org and www.pypy.org. -Ernest On June 8, 2018 at 1:08:11 PM, Alex Gaynor ([email protected]) wrote: Adding the PSF infra group. Alex On Fri, Jun 8, 2018, 1:03 PM Armin Rigo <[email protected]> wrote: > Hi, > > Who knows how to fix this? https://pypy.org/ complains that it has > got an invalid certificate. > > > Armin > _______________________________________________ > pypy-dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/pypy-dev > ________________________________________________ Infrastructure mailing list [email protected] https://mail.python.org/mailman/listinfo/infrastructure Unsubscribe: https://mail.python.org/mailman/options/infrastructure/ewdurbin%40gmail.com
_______________________________________________ pypy-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-dev
