Tellyworth 3:58 am on April 21, 2020

WordCamp.org Let’s Encrypt script isn’t…

WordCamp.org Let’s Encrypt script isn’t running, and hasn’t for several weeks. As mentioned here: https://wordpress.slack.com/archives/G02QCEMRY/p1586994663032600

Can we please see of a copy of the /tmp/letsencrypt-update.log file from production to diagnose.

cc @iandunn

Barry 4:12 am on April 21, 2020

Fixed. Please note that this currently uses the LE ACME v1 APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. which will stop working in June – https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430

In the process of switching to v2, I would probably recommend switching to a standard client and away from this custom one. Is this something that is on your radar/TODO list? I’m only asking because I think your team implemented this client – it wasn’t systems AFAIK.
- Tellyworth 4:58 am on April 21, 2020
  
  Yep we have v2 on our near-term TODO list.
Ian Dunn 2:54 pm on April 21, 2020

Thanks Barry.

xref 9484

Unbreak the LE script. Default python requests user agent is blocked, lets use a more descriptive UA.