Prescreen incident

Global certificate validation issue for old platforms

Notice Resolved View vendor source →

Prescreen experienced a notice incident on October 4, 2021 affecting onlyfy.io, lasting 36d 3h. The incident has been resolved; the full update timeline is below.

Started
Oct 04, 2021, 11:04 AM UTC
Resolved
Nov 09, 2021, 02:19 PM UTC
Duration
36d 3h
Detected by Pingoru
Oct 04, 2021, 11:04 AM UTC

Affected components

onlyfy.io

Update timeline

  1. investigating Oct 04, 2021, 11:04 AM UTC

    Liebe Prescreen User, je nach Ihrer Plattform kann es dazu kommen, dass Sie, aufgrund einer Änderung bei der Validierung von Zertfikaten durch die Zertifizierungsstelle Let's Encrypt, nun Schwierigkeiten dabei haben, Prescreen zu erreichen. Let's Encrypt unterstützt nicht mehr die Validierung des ISRG Root X1 Zertifikats über veraltete Methoden, was zur unbeabsichtigten Blockierung von Prescreen führen kann. Sollten Sie Prescreen durch eine Zertifikatswarnung, wie von Ihrem Web-Browser angezeigt, nicht erreichen können, so wenden Sie sich bitte an Ihre IT-Administratoren. Mehr Informationen zu diesem globalen Problem finden Sie hier: https://letsencrypt.org/docs/certificate-compatibility/ Beste Grüße Ihr Prescreen Team ------------------------------------ Dear Prescreen users, depending on your platform, you may experience trouble accessing Prescreen due to a change in certificate validation by Let's Encrypt, a certificate authority. Let's Encrypt is no longer allowing validation of their ISRG Root X1 certificate via outdated means, which may result in accidental blocking of Prescreen. If you find yourself unable to access Prescreen due to a certificate warning displayed by your web browser, please turn to your IT administrators. More information about this global issue can be found here: https://letsencrypt.org/docs/certificate-compatibility/ Best regards, Your Prescreen Team

  2. monitoring Oct 12, 2021, 03:06 PM UTC

    We are already receiving significantly fewer questions regarding this global occurrence.

  3. resolved Nov 09, 2021, 02:19 PM UTC

    This incident has been resolved.