authentication failed: javascript exception: error: certificate has expired

There is now a banner warning on Zapier about this, but no solution is offered. 

Hi @sbullet46 and @msandrew 

This is a known issue and outside the hands of Zapier to fix.

Who’s hand’s is it in?  It’s absolutely in Zapier’s hands. 

Zapier seems to be upgrading their root certificate library on their end, which should fix the problem. On the short term at least.

@msandrew

https://letsencrypt.status.io/

Check out this related Tweet:

when are we expecting a solution...

@Troy Tessalone Thanks for this.  As a non-IT person are you saying that Zapier failed to update their root certificate library for the planned expiry of the DST Root CA or are you saying it’s on Parsuer’s end?

Thanks.

@sbullet46

This is due to the nature of the problem with expired certificates issued from Let’s Enrcypt.

That’s up to each of the impacted apps to address, so there’s no timetable available.

You can open a ticket with Zapier Support if you’d like to inquire further: https://zapier.com/app/get-help

@msandrew 

As I understand the problem...

This is due to the nature of the problem with expired certificates issued from Let’s Enrcypt.

That’s up to each of the impacted apps to address, so there’s no timetable available.

You can open a ticket with Zapier Support if you’d like to inquire further: https://zapier.com/app/get-help

@Parseur (one of the impacted apps) is on this message string.  I think they may have a different opinion on this, but perhaps we can let them respond directly.  As they have noted, “Zapier seems to be upgrading their root certificate library on their end”

@msandrew

Zapier may be impacted as well in all of this.

It’s one thing when 1 app has an issue with a certificate expiring, but it’s another issue when thousands of apps/websites are impacted on the same day.

That usually points to some foundational issue with the internet such as when Amazon AWS has downtime, etc.

I’m having the same issuing connecting to MatterMost
We have LetsEncrypt disabled, and yet having the same issue

This is a wider Zapier problem that needs to be addressed? @Zapier give us some details on the issue and a timeline on the fix?

Also, where do I find the “app status page”? 
That is referred to in the blue bar message

@HS212 

For Mattermost, this is their status page: https://status.mattermost.com/

Zapier has a status page too: https://status.zapier.com/

@Zapier what changed this morning? Its obviously impacted more than one app, so there surely is a reason from the MatterMost side

Lets drop some details to paying customers

@HS212

Please see the above thread for added context on the issue, thanks.

Here’s the gist related to Let’s Encrypt:

Just got this message from Zapier

Thanks for reaching out to Zapier -- I hope you're doing well today! Sorry you're running into a snag here with your Mattermost app. Jamie from Support, happy to assist!
​ 
The SSL certs for Zapier are all up to date. The main problem stems from user and partner code that hasn't been updated in a while and uses an old Node.js version. It's old enough that it doesn't trust the new LE cert, which is why you're seeing the error in the Zap Editor. 
 
We've updated a few things on our end that bumped our partner integrations to a new node version, so hopefully, this issue is resolved now. 👍

Having the similar issue on my WordPress blog and I am trying to fix it. Look like SSL issue but not sure. :( Do I need to update SLetsEncrypt on my site?

Hi everyone thanks so much for your patience!

@HS212 very much appreciate you posting supports reply to your message!  As you mentioned, our team pushed an update that should fix this and those zaps should be coming back online. Of course, if you’re still experiencing any underlying issues please don’t hesitate to contact our support team and they’ll be happy to dig in further with you.

@HS212, @msandrew , @Parseur and @sbullet46 you’ve all also been added to the issue report and will be notified via email once all is confirmed good to go. We’ll also post here shortly with another update.

Thanks all for the assistance in clearing this up!

 @rayansufian , it’s certainly possible it’s related! I’ve also added you to the report so you’ll be kept in the loop as well. If you’re still seeing those errors post email confirmation and the update here in the thread it might be worth opening a ticket with our support team.