One clic deploy fails
6:05:50 PM: Failed during stage ‘preparing repo’: error checking for ref: fatal: unable to access ‘https://undefined.com/start/netlify/victor-hugo/’: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
the URL is ‘undefined’
Undefined.com does not have an SSL certificate so I believe it is refusing to connect as it could be a security risk. Is it your website and you’re appemting to setup a one-click deploy or are you attempting to just use somebodies template? Where are you attempting to one click deploy from since undefined.com shows no content to me?
hi Aaron.
Thanks for the reply.
I think it’s a bug in some script, and it expands to ‘undefined’ .com !
Who would have a domain named undefined ?
I click on any of the cards from StaticGen.com “Deploy to Netlifiy”
I then get to
https://app.netlify.com/start/deploy
I connect to my github
Save and Deploy
I am now in my dashboard, with a site deploy failed
Production master @head failed
3:42:44 PM: Failed during stage ‘preparing repo’: error checking for ref: fatal: unable to access ‘https://undefined.com/start/netlify-templates/jekyll-base/’: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
So it looks like the script in Save and Deploy is giving me the ‘undefined’
Maybe the repo was deleted 
Hey @TMorgan00,
Very strange! I just successfully deployed two sites from staticgen.com- one using the Jekyll template, the other using Gatsby template. It seems like there’s a connection issue between Github and Netlify. Could you share the deploy log here? And just to check all the things, can you confirm that you were logged into Netlify when you clicked the “deploy to Netlify” button?
Circling back here- apparently this was in fact a bug that was fixed on Friday with Fix Deploy to Netlify button by huguestennier · Pull Request #435 · jamstack/jamstack.org · GitHub 
Please let us know if you’re still running into this!
Good to know,
Anyway, I blame myself, so I started again from a new virtual instance, and it seems to be working just fine now.
Thanks!