The timing suggests this is almost certainly caused by the letsencrypt certificate changes. You can find instructions for fixing the problem here:
Unfortunately there was no way for us to push out an automatic update for this problem, so an “Announcement” was the best we could do - sorry for the disruption!