Same issue here. Glad to hear it's not a localised issue, frustrated that it hasn't been resolved promptly. Was expecting this to be solved by today. It's an out of date security certificate on the server. There's little reason it should have been allowed to lapse, and even less reason it should be still out of date.