DatoCMS <> Vercel Build Triggers Failing

Describe the issue:

  • The error in the log is SSL_connect returned=1 errno=0 peeraddr=76.76.21.112:443 state=error: unexpected eof while reading
  • All the build triggers we have available within DatoCMS that are connected to Vercel instantly fail with the above error. This is true within my company’s Pro account, as well as my personal hobby-tester account. And across several connected Vercel projects.
  • We’ve made no changes this is just newly happening this morning for us.
  • When I try and create a new build trigger it hangs when it should be displaying the “Select Project Repo” screen.
  • Triggering a build from within Vercel (manually or via pushing code into a connected repo) still does the job of getting data out of DatoCMS.

Maybe unrelated but it appears that the DatoCMS Status Dashboard isn’t connecting to the services it should be reporting on.

(Recommended) What’s the URL of the record or model in question?

  • Being able to see the issue in your real project is you for very helpful for troubleshooting. If you don’t provide the URL upfront, we’ll often have to ask you for it anyway, which just slows down our response time for you.
  • If you’re concerned about privacy, you can email us at support@datocms.com instead of posting here.

(Optional) Do you have any sample code you can provide?

Hello @derek.kinsman and welcome to Community! :slight_smile:

Thank you for the report, we are aware of it and seems like it’s related to a problem within Vercel’s infrastructure, in particular with a Digital Ocean problem.

We are tracking the situation and we are not seeing errors on our side any more. Can you confirm if the problem is still there or if it’s gone? Thank you!

Thanks @mat_jack1 ! (I’ve been in lurker mode for a bit, but been a user of the service for a few years now). It looks like this has resolved. Build triggers are firing as usual.

2 Likes

thanks for confirming :slight_smile: