Re: [pypy-dev] [Infrastructure] https pypy.org has got an invalid certificate now

2018-06-08 Thread M.-A. Lemburg
Thanks, Ernest. On 08.06.2018 21:00, Ernest W. Durbin III wrote: > 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 > in

Re: [pypy-dev] [Infrastructure] https pypy.org has got an invalid certificate now

2018-06-08 Thread Ernest W. Durbin III
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

Re: [pypy-dev] [Infrastructure] https pypy.org has got an invalid certificate now

2018-06-08 Thread Ernest W. Durbin III
On June 8, 2018 at 1:45:58 PM, M.-A. Lemburg (m...@egenix.com) wrote: It looks like pypy.org is run on PSF infrastructure: virt-y8pzvf.psf.osuosl.org. That’s correct. We'd have to get a new certificate for it. I am a bit surprised that we have a wildcard certificate on one of the OSU VM. Shou

Re: [pypy-dev] [Infrastructure] https pypy.org has got an invalid certificate now

2018-06-08 Thread M.-A. Lemburg
It looks like pypy.org is run on PSF infrastructure: virt-y8pzvf.psf.osuosl.org. We'd have to get a new certificate for it. I am a bit surprised that we have a wildcard certificate on one of the OSU VM. Shouldn't this only be installed on front.python.org ? Thanks. On 08.06.2018 19:07, Alex G