Fail to deploy site generator

I am a newbie to netlify and jamstack, ANy help appreciated to resolve the below issue.

  1. Vistied Static Site Generators - Top Open Source SSGs | Jamstack
  2. Clicked “Deploy to Netlify” under the first generateor (Next.js)
  3. I choose to connect to github
  4. Deployment fails with this sequence:
    12:40:35 PM: Build ready to start
    12:40:37 PM: build-image version: b0258b965567defc4a2d7e2f2dec2e00c8f73ad6
    12:40:37 PM: build-image tag: v3.4.1
    12:40:37 PM: buildbot version: db1c11c310036491f94882c0e310ea68c81c7e60
    12:40:37 PM: Fetching cached dependencies
    12:40:37 PM: Failed to fetch cache, continuing with build
    12:40:37 PM: Starting to prepare the repo for build
    12:40:38 PM: Failing build: Failed to prepare repo
    12:40:38 PM: Failed during stage ‘preparing repo’: error checking for ref: fatal: unable to access ‘’: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none: exit status 128
    12:40:38 PM: Finished processing build request in 1.381713385s
1 Like

If you try to visit (the website which is probably the source repo which Netlify is trying to clone), you can see that Chrome (and probably other browsers) will show an error that connection is not private. It’s basically some error with the SSL of that URL. This isn’t a solution, but a description of what the error is. The problem is probably the link here:

This is just my guess.

same question. Do I have to have my own SSL certs? Why can’t I use netlify subdomain SSL certs?

I can’t establish a relation between the opening question and your question. What does this have to with your SSL?

hey @fangjijob - I am having trouble understanding as well. Can you try and explain what you are trying to do in a different way? thanks!

Could it be that ‘’ is a bug in the javascript within ?

1 Like

Hey @TMorgan00,
Was just digging up your post to share here: Deploy from templates Yeah, it looks like we may have a bug somewhere. I’ll leave a note for us to look into it and possibly escalate to an engineering team next week :memo:

Circling back here- apparently this was in fact a bug that was fixed on Friday with :partying_face: Please let us know if you’re still running into this!

yes much better, and thanks