The certificate for code.djangoproject.com expired on 7/4/2021.

112 views
Skip to first unread message

Asif Saif Uddin

unread,
Jul 4, 2021, 1:34:02 AM7/4/21
to Django developers (Contributions to Django itself)

Websites prove their identity via certificates, which are valid for a set time period. The certificate for code.djangoproject.com expired on 7/4/2021.
 
Error code: SEC_ERROR_EXPIRED_CERTIFICATE
 
View Certificate


Asif

Adam Johnson

unread,
Jul 4, 2021, 5:38:01 AM7/4/21
to django-d...@googlegroups.com
Hi Asif

I'm not seeing a problem - the certificate I get expires in October.

Screenshot 2021-07-04 at 10.36.15.png

Thanks,

Adam

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/539fc003-f4de-4dae-8ace-d5103c19f44en%40googlegroups.com.

Jason Johns

unread,
Jul 4, 2021, 9:07:55 AM7/4/21
to Django developers (Contributions to Django itself)
FWIW, a user at pyslackers said they got a 503 about the same time about 50 minutes after Asif's initial message.  Then about two hours later (about an hour before Adam's reply), someone else responded that they weren't able to replicate.  Maybe there was a delay in applying the cert rotation?  I'm not able to easily see when the cert was generated.

אורי

unread,
Jul 4, 2021, 9:10:36 AM7/4/21
to Django developers (Contributions to Django itself)
I think there was a downtime for about a few hours when the certificate was not valid.


Jason Johns

unread,
Jul 4, 2021, 9:14:20 AM7/4/21
to Django developers (Contributions to Django itself)
Ahh, I see the issue.

This screenshot is for Summer of Code 2021, at https://code.djangoproject.com/wiki/SummerOfCode2021.  You can see the cert is not valid before 0431 eastern

Screen Shot 2021-07-04 at 9.10.01 AM.png


Screen Shot 2021-07-04 at 9.09.14 AM.png

Looks like the SoC URL cert didn't get applied before this morning, and users who tried to access that URL would have gotten Certificate Expired errors.

chris.j...@gmail.com

unread,
Jul 4, 2021, 10:14:58 AM7/4/21
to Django developers (Contributions to Django itself)
Maybe someone can file an issue about it to address the same thing happening in the future. Perhaps here: https://github.com/django/code.djangoproject.com/issues

--Chris

Markus Holtermann

unread,
Jul 4, 2021, 10:49:03 AM7/4/21
to Django developers
We had some intermittent connection issues over the last couple of hours: https://status.djangoproject.com/. All should be fine again.

Cheers

On Sun, Jul 4, 2021, at 4:14 PM, chris.j...@gmail.com wrote:
> Maybe someone can file an issue about it to address the same thing
> happening in the future. Perhaps here:
> https://github.com/django/code.djangoproject.com/issues
>
> --Chris
>
> On Sunday, July 4, 2021 at 9:14:20 AM UTC-4 Jason Johns wrote:
> > Ahh, I see the issue.
> >
> > This screenshot is for Summer of Code 2021, at https://code.djangoproject.com/wiki/SummerOfCode2021. You can see the cert is not valid before 0431 eastern
> >
> > Screen Shot 2021-07-04 at 9.10.01 AM.png
> >
> > This screenshot is for https://docs.djangoproject.com/en/3.2/:
> >
> > Screen Shot 2021-07-04 at 9.09.14 AM.png
> >
> > Looks like the SoC URL cert didn't get applied before this morning, and users who tried to access that URL would have gotten Certificate Expired errors.
> > On Sunday, July 4, 2021 at 9:07:55 AM UTC-4 Jason Johns wrote:
> >> FWIW, a user at pyslackers said they got a 503 about the same time about 50 minutes after Asif's initial message. Then about two hours later (about an hour before Adam's reply), someone else responded that they weren't able to replicate. Maybe there was a delay in applying the cert rotation? I'm not able to easily see when the cert was generated.
> >>
> >> On Sunday, July 4, 2021 at 5:38:01 AM UTC-4 Adam Johnson wrote:
> >>> Hi Asif
> >>>
> >>> I'm not seeing a problem - the certificate I get expires in October.
> >>>
> >>> Screenshot 2021-07-04 at 10.36.15.png
> >>>
> >>> Thanks,
> >>>
> >>> Adam
> >>>
> >>> On Sun, 4 Jul 2021 at 06:34, Asif Saif Uddin <auv...@gmail.com> wrote:
> >>>>
> >>>> Websites prove their identity via certificates, which are valid for a set time period. The certificate for code.djangoproject.com expired on 7/4/2021.
> >>>>
> >>>> Error code: SEC_ERROR_EXPIRED_CERTIFICATE
> >>>>
> >>>> View Certificate
> >>>>
> >>>> https://code.djangoproject.com/wiki/SummerOfCode2021
> >>>>
> >>>> Asif
> >>>>
> >>>> --
> >>>> You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
> >>>> To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
> >>>> To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/539fc003-f4de-4dae-8ace-d5103c19f44en%40googlegroups.com <https://groups.google.com/d/msgid/django-developers/539fc003-f4de-4dae-8ace-d5103c19f44en%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to django-develop...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/4ab92cf4-04e0-4e30-a088-ec13ce3bc3d9n%40googlegroups.com <https://groups.google.com/d/msgid/django-developers/4ab92cf4-04e0-4e30-a088-ec13ce3bc3d9n%40googlegroups.com?utm_medium=email&utm_source=footer>.

chris.j...@gmail.com

unread,
Jul 4, 2021, 10:59:04 AM7/4/21
to Django developers (Contributions to Django itself)
Is the updating of the certificate done with an automated or documented process? If so, it seems like it could happen again in the future.

(By the way, the status page shows code.djangoproject.com not having downtime during that period, but that was the page that was down for folks.)

--Chris
Reply all
Reply to author
Forward
0 new messages