Home > Software engineering >  app engine deploy failing with "fatal: unable to access 'https://gopkg.in/yaml.v3/':
app engine deploy failing with "fatal: unable to access 'https://gopkg.in/yaml.v3/':

Time:10-05

anyone else getting this issue when deploying Go/Other projects to app engine?

Deployment was working fine on Tuesday Sept 28th. Tried to deploy Friday Oct 1 (yesterday) and today but still getting the same error. Not code related since no code was changed since last deploy.

from the log: Step #2 - "build": go: gopkg.in/[email protected]: git fetch -f origin refs/heads/:refs/heads/ refs/tags/:refs/tags/ in /layers/google.go.gomod/gopath/pkg/mod/cache/vcs/5ea86ba1b933025fb7a7a539058d4acea777e0b3175c573a70130f7ea565323f: exit status 128: Step #2 - "build": fatal: unable to access 'https://gopkg.in/yaml.v3/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

If I'm reading this right there is a missing certificate in app engine? but, not sure what certificate it needs since I never had to provide one before. Maybe if I delete the cert file App Engine will recreate it?

Any ideas?

CodePudding user response:

I had the same issue is Travis CI build.

I changed the build image to ubuntu 20.04 (from 16.04) and update package ca-certificates

sudo apt-get update
sudo apt-get install --reinstall ca-certificates

CodePudding user response:

Solved ... mostly

This solution is for those running on App Engine Standard environment using Go 1.11

change your runtime in app.yaml to

runtime: go115

and change your go version in go.mod file:

module myapp

go 1.11

This will allow you to deploy your application. In my case, there were other changes I had to make to the app.yaml. For example, I had to add

app_engine_apis: true

I have my app deployed now but not completely running. I'll post relevant fixes here if I discover anything else. Hope this helps those that run into this issue.

  • Related