I’m experiencing a weird error on one of my sites. When building it suddenly throws this error. It’s from gatsby-source-datocms. Is this something you have seen before or have any idea why it’s coming? It started today and the site has been live and working (and getting updated without issues for 3-4 years).
hello @anders unfortunately this is due to a root certificate of Let’s Encrypt expiring. This means that if you are building your site on an old system with old root CAs then you’ll detect our certificate as expired, while it’s not the case.
Depending on where you are building I would recommend you to update your underlying OS as it might be the cause of your problems.
Ugh - I can’t really do that (without spending a lot of time upgrading packages). Why is this happening all of a sudden? Are there other ways to fix it?
Can you reach out to Netlify support and ask about their cert chain? I had a similar problem on my build machines but they resolved themselves in a few hours, but we use Vercel. Somebody somewhere has to keep updating all the certs periodically (usually handled by the OS or devops of your deployment company), and it really shouldn’t be you… unless you like doing that sort of thing.
In this case the reach was just quite wide because it was LetsEncrypt, which has the unfortunate combination of being free, popular, and implemented in different ways across different hosts and OSes.
(Edit: to be clear, what expired wasn’t the particular cert issued to Dato, but something higher up the chain of trust, at the CA level)
@anders if you want you can invite me (m.giaccone@datocms.com) to your Netlify project and I can have a look. Also if you invite me in your Github (maybe?) repo I can try to help, I’m matjack1 there.
Easier said than done unfortunately (for me). It’s an old and somewhat unmaintained solution and messing with Node version brings out a lot of other issues to the table. I’ll look into it. You have access to the netlify now. Let me know if you don’t need it anyway.