"cannot talk to GitHub" about gopkg HOT 80 CLOSED

Right, GitHub is not accepting connections from gopkg.in right now. I'm in touch with support trying to figure out why and get it sorted.

from gopkg.

This is happening to us as well and causing a lot of failures in our CI pipeline while downloading packages to build the binaries.
Could you please help us with a work around or a permanent fix for the same.

from gopkg.

I'm looking into it. Given the multiple reports, it's of course a real issue, but it's not easy to debug it on my end as this looks like GitHub failing to respond the request on time. If I can't find anything here, I'll reach out to GitHub and see if someone can help me.

from gopkg.

@niemeyer unfortunately the problem is back

from gopkg.

Guys, it's happening again. Just linking other issues so that people know what's happening.
go-yaml/yaml#887
srvaroa/labeler#43

from gopkg.

Created a discussion earlier, and based on help from @matthewgoodman13 was directed to a reddit post. Link to discussion:
https://github.com/orgs/community/discussions/29332

DasSkelett on the reddit post said that we could either use vendoring or GOPROXY. The GOPROXY route was a quick and easy fix for me. Just export the environment variable GOPROXY as proxy.golang.org and then run your go get command and you're good to go:
export GOPROXY=https://proxy.golang.org

from gopkg.

Reflected in https://status.github.com/

from gopkg.

It looks like the same issue is happening again. I'm currently experiencing the same behaviour while trying to install the gometalinter.v2:

$ curl https://gopkg.in/alecthomas/gometalinter.v2
Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/alecthomas/gometalinter.git/info/refs?service=git-upload-pack: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

from gopkg.

@niemeyer can you fail over to hot spare https://p3.gopkg.in/yaml.v2 please?

from gopkg.

Over the last few days we've also been doing some analysis with help from the IS team at Canonical, and we found that a relevant percentage of requests, which amounts to over one million requests a day, is being performed by one small for-profit organization. We'll probably introduce a quota to encourage cases like this to be more carefully designed.

from gopkg.

Getting this error again today while pulling dependencies from gopkg. Can you please help or suggest as this is blocking our builds

go: gopkg.in/[email protected]: unrecognized import path "gopkg.in/check.v1": reading https://gopkg.in/check.v1?go-get=1: 502 Bad Gateway Makefile:56: recipe for target 'test' failed</span></span></body></html>

from gopkg.

And it's sorted:

We've just deployed some changes to resolve this and I can see that https://gopkg.in/mgo.v2 is now loading again. We've updated our status back to green.

Sorry for the trouble this caused you and your users. Don't hesitate to follow up if you're still seeing any problems or if you have any questions.

from gopkg.

Could you please help us with a work around or a permanent fix for the same.

I cannot fix GitHub permanently. I cannot even fix it temporarily. The service provided by gopkg.in depends entirely on GitHub itself being able to serve requests. I have no visibility on how GitHub dispatches requests internally, but what I'm doing right now is adding a more strict quota on organizations that are clearly abusing the system so that we can try to make GitHub happier about the requests.

from gopkg.

@esetnik Since this is a more general issue on GitHub and the issue comes and goes, we have no guarantees that shifting won't present the same problem. Also, GitHub is using our service to debug their outage, so I'm keen on not masking the problem for them so it can be fixed faster and for good.

Per their support:

It looks like https://gopkg.in/mgo.v2 is accessible at the moment and our team are making use of this URL as they work to resolve the issue. I'll follow up again when I have another update for you.

We also had an update moments ago:

from gopkg.

Issue appears to be resolved from here at least! 🎉 My build just passed.

from gopkg.

same here... but hopefully it's not intermittent.

from gopkg.

Thanks for the data, folks. Still zero feedback from GitHub. My best guess at the moment is that there was some inconsistent hiccup there and it's been addressed. For future cases, please note that any such hiccup in GitHub ends up showing up as a failure from gopkg.in itself. In such cases the log is clear about what particular operation is failing and how.

Feel free to report here anyway, though, even more if you see https://www.githubstatus.com/ and there's nothing being reported there. It's useful to get some perspective on how it's failing and where.

Finally, just for some comfort: Canonical has 24x7 monitoring on this service, and a team that takes good care of it. So actual issues in gopkg.in itself are going to be looked after.

from gopkg.

Yup, just checking in here. Happened to us too.

from gopkg.

Hi all,
I'm getting this error:

go: gopkg.in/[email protected]: unrecognized import path "gopkg.in/yaml.v2" (parse https://gopkg.in/yaml.v2?go-get=1: no go-import meta tags ())

How can be solved?

Isaac.

from gopkg.

Also hitting this.

from gopkg.

Looks like it's happening again:

go install github.com/awslabs/amazon-ecr-credential-helper/ecr-login/cli/docker-credential-ecr-login@latest: github.com/awslabs/amazon-ecr-credential-helper/ecr-login@none updating to
        github.com/awslabs/amazon-ecr-credential-helper/[email protected] requires
        github.com/stretchr/[email protected] requires
        gopkg.in/[email protected]: unrecognized import path "gopkg.in/yaml.v3": reading https://gopkg.in/yaml.v3?go-get=1: 502 Bad Gateway
        server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

Using the proxy makes no difference.

from gopkg.

Problems have been reflected on GitHub System Status

from gopkg.

@andrewslotin Please see the last few messages above.

It also looks like it's almost sorted, from their status page:

from gopkg.

Github status seems all good for today, but I encountered this issue again.

package gopkg.in/inf.v0: unrecognized import path "gopkg.in/inf.v0" (https fetch: Get https://gopkg.in/inf.v0?go-get=1: dial tcp 35.196.143.184:443: i/o timeout)
package gopkg.in/mgo.v2: unrecognized import path "gopkg.in/mgo.v2" (https fetch: Get https://gopkg.in/mgo.v2?go-get=1: dial tcp 35.196.143.184:443: i/o timeout)
package gopkg.in/mgo.v2/bson: unrecognized import path "gopkg.in/mgo.v2/bson" (https fetch: Get https://gopkg.in/mgo.v2/bson?go-get=1: dial tcp 35.196.143.184:443: i/o timeout)

from gopkg.

We couldn't find any relevant information on our end that could explain timeouts with GitHub. I've filed a bug with GitHub, which remains silent. Their status page is also quiet about any issues yesterday, so I'm somewhat empty handed.

Would anyone here happen to have a precise timestamp for when the problem was observed, from your CIs?

from gopkg.

It seems to be resolved now 👍

from gopkg.

Happening for me too.

from gopkg.

Happening today again !

from gopkg.

As a side note, if you have a good contact at GitHub for that kind of issue, please raise attention so we can get it back up ASAP. If they take too long to respond I may end up switching IP addresses for a while so they can take their time to evaluate the issue, but I'd prefer to sort it the proper way instead.

from gopkg.

Unfortunately no :( Maybe switching IPs is a way to go now ...

from gopkg.

We have a hot spare at https://p3.gopkg.in/yaml.v2 ready to switch. Let's give them another moment to evaluate the issue with the domain pointing to the right location, and if it takes too long we switch.

from gopkg.

From GitHub:

I'm speaking with our infrastructure teams and we've just updated our status while we work on this. I'll follow up with you as soon as we have an update.

from gopkg.

Update from support:

We think we found the problem machine and are looking for a root cause.

Seems to be working now. Might be fixed, but given that feedback we might still see a few bumps.

from gopkg.

There we go again... just got in touch with them again.

from gopkg.

GitHub issue still persisting
golang/go#27622 was closed but my build is still failing.

Thanks!

from gopkg.

Is this a special case of this issue?

go get -u gopkg.in/src-d/go-git.v4/...                     
# cd [...]/src/gopkg.in/src-d/go-git.v4; git pull --ff-only                           
remote: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/src-d/go-git.git/info/refs?service=git-upload-pack: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
fatal: unable to access 'https://gopkg.in/src-d/go-git.v4/': The requested URL returned error: 502
package gopkg.in/src-d/go-git.v4: exit status 1
package gopkg.in/check.v1: unrecognized import path "gopkg.in/check.v1" (parse https://gopkg.in/check.v1?go-get=1: no go-import meta tags ())
package gopkg.in/src-d/go-git-fixtures.v3: unrecognized import path "gopkg.in/src-d/go-git-fixtures.v3" (parse https://gopkg.in/src-d/go-git-fixtures.v3?go-get=1: no go-import meta tags ())

from gopkg.

looks like it, it's a general Github http 502 error

from gopkg.

there's any known workaround for golang module system? Like adding/modifying something in the go.mod?

from gopkg.

@esetnik Since this is a more general issue on GitHub and the issue comes and goes, we have no guarantees that shifting won't present the same problem. Also, GitHub is using our service to debug their outage, so I'm keen on not masking the problem for them so it can be fixed faster and for good.

Per their support:

It looks like https://gopkg.in/mgo.v2 is accessible at the moment and our team are making use of this URL as they work to resolve the issue. I'll follow up again when I have another update for you.

We also had an update moments ago:

I'm not sure what's different about your connection, but I definitely cannot resolve https://gopkg.in/mgo.v2. I think it's a bit unreasonable for Github team to assume third-parties won't alter their own infrastructure to do everything they can to mitigate upstream affects of the outage for their users.

from gopkg.

We haven't been able to build our packages in CircleCI for 8+ hours because of this GitHub issue. We might be able to override some IPs in the build containers but this is a really crappy situation to be in. I'm experiencing all the issues pointed out above while this occurs on the Github side.

from gopkg.

The GitHub status says everything operates normally since 6 hours ago: ("한국 표준시" in the screenshot means KST, UTC+9)

When I visit http://gopkg.in/yaml.v2 in a Web browser, it works as well. But my build in Travis CI is still failing (gin-gonic depends on go-yaml in gopkg.in):

$ dep ensure -update github.com/hangulize/hangulize
Solving failure:
	(1) failed to list versions for https://gopkg.in/yaml.v2: remote: Not Found
fatal: repository 'https://github.com/go-yaml/yaml/' not found
: exit status 128
	(2) failed to list versions for http://gopkg.in/yaml.v2: remote: Not Found
fatal: repository 'http://github.com/go-yaml/yaml/' not found
: exit status 128

Is there anyone who has an idea about this experience?

from gopkg.

maybe they do have cache. I just opened travis an issue

from gopkg.

Apparently they've solved the issue for good, so I'm closing this one as well.

Sorry for the trouble everyone.

from gopkg.

My problem #63 (comment) was not due to this service issue. The reason was GIT_HTTP_USER_AGENT customized by Travis CI's deploy stage. Travis CI sets it as GIT_HTTP_USER_AGENT=travis/0.1.0 dpl/1.10.0 git/2.15.1 only in the deploy stage.

GitHub's git HTTPS URL without .git, like https://github.com/go-yaml/yaml rather than https://github.com/go-yaml/yaml.git, fails on an unexpected User-Agent header.

$ GIT_HTTP_USER_AGENT='' go get gopkg.in/yaml.v2
# cd .; git clone <https://gopkg.in/yaml.v2> .../go/src/gopkg.in/yaml.v2
Cloning into '.../go/src/gopkg.in/yaml.v2'...
error: RPC failed; HTTP 422 curl 22 The requested URL returned error: 422 Unprocessable Entity
fatal: The remote end hung up unexpectedly
package gopkg.in/yaml.v2: exit status 128

from gopkg.

@niemeyer it is happening again intermittently

from gopkg.

Facing the below error : 

remote: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

@niemeyer 

from gopkg.

+1
our ci/cd jobs are failing with something similar

go: github.com/rubenv/[email protected] requires
    gopkg.in/[email protected]: unrecognized import path "gopkg.in/gorp.v1": reading https://gopkg.in/gorp.v1?go-get=1: 502 Bad Gateway
    server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-gorp/gorp.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

from gopkg.

looks like it's working now.

update: spoke too soon, it's down again.

from gopkg.

Our ci/cd seems to pass currently.

Has there been any update/post somewhere about this?

from gopkg.

Success 15.11.2021 at 12:21 PM GMT +2
Success 15.11.2021 at 12:36 PM GMT +2 <- incidents happen from here on out
Failed 15.11.2021 at 12:40 PM GMT +2
Failed 15.11.2021 at 12:41 PM GMT +2
Failed 15.11.2021 at 12:47 PM GMT +2
Failed 15.11.2021 at 1:02 PM GMT +2
Failed 15.11.2021 at 1:49 PM GMT +2
Success 15.11.2021 at 2:26 PM GMT +2
Failed 15.11.2021 at 3:06 PM GMT +2
Success 15.11.2021 at 3:22 PM GMT +2
Success 15.11.2021 at 4:38 PM GMT +2
Failed 15.11.2021 at 5:00 PM GMT +2
Failed 15.11.2021 at 5:59 PM GMT +2 <- This is the last failed run that our logs show
Success 16.11.2021 at 8:48 AM GMT +2 <- Success from here on out

There was also some issues with the pipelines for our provider at that time but this is the closest thing that I could find https://status.dev.azure.com/_event/272370766

(also sorry from poor formatting)

from gopkg.

The earliest run that failed for me was around Nov 15, 2021 2:38 AM (UTC-8:00)

from gopkg.

Some feedback from GitHub:

from gopkg.

This is happening again... Any chance it will be resolved and gopkg.io becomes stable? IT's been happening for over 2 years randomly, as a result packages hosted on here are not reliable in production environment.

from gopkg.

Same here for about two hours

from gopkg.

Would replacing the problematic source with a github link instead using replace in go.mod help?

from gopkg.

Would replacing the problematic source with a github link instead using replace in go.mod help?

I mean it would help but the amount of work required for a not long term solution is not realistic.

from gopkg.

Just to confirm that this indeed the same issue, would anyone have the error message and timestamp at hand?

from gopkg.

Can provide them tomorrow.

from gopkg.

Some of the same error message and times are below. The timestamp is in IST.
`[Container] 2021/11/25 16:01:00
Step 14/27 : RUN go mod download

---> Running in c5d727371cc6

go: gopkg.in/[email protected] requires

gopkg.in/[email protected]: invalid version: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /go/pkg/mod/cache/vcs/9241c28341fcedca6a799ab7a465dd6924dc5d94044cbfabb75778817250adfc: exit status 128:

remote: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-check/check.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

fatal: unable to access 'https://gopkg.in/check.v1/': The requested URL returned error: 502

The command '/bin/sh -c go mod download' returned a non-zero code: 1
`

[Container] 2021/11/25 20:45:33 Running command make unit-test go test -count=1 -covermode=atomic -coverprofile=coverage-unit.out ./... go: bitbucket.org/swigy/[email protected] requires gopkg.in/[email protected]: reading gopkg.in/sourcemap.v1/go.mod at revision v1.0.5: unknown revision v1.0.5 Makefile:21: recipe for target 'unit-test' failed make: *** [unit-test] Error 1

from gopkg.

Getting this error again today while resolving dependencies from gopkg. This is blocking production critical builds for us. Can someone please look into this on priority?

https://gopkg.in/alexcesaro/statsd.v2?go-get=1: 502 Bad Gateway

from gopkg.

Same as @kaushiknag90 stated, receiving this on github ci and blocks our builds.

remote: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-check/check.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers) fatal: unable to access 'https://gopkg.in/check.v1/': The requested URL returned error: 502

from gopkg.

Same issue as @kaushiknag90
the issue persists when running go mod download:

gopkg.in/go-playground/[email protected]: unrecognized import path "gopkg.in/go-playground/assert.v1" (parse https://gopkg.in/go-playground/assert.v1?go-get=1: no go-import meta tags ())
gopkg.in/[email protected]: unrecognized import path "gopkg.in/yaml.v2" (parse https://gopkg.in/yaml.v2?go-get=1: no go-import meta tags ())

from gopkg.

Having the same issue.

server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

from gopkg.

@DavidYos27 @ucanfil @deydebaditya @kaushiknag90 is it still happening for you guys?

from gopkg.

@hamdi-ben-yaflah not sure what's the root cause of the problem, but mine is resolved

from gopkg.

@hamdi-ben-yaflah No, still facing the same issue.
go: github.com/spf13/[email protected] requires github.com/sagikazarmark/[email protected] requires go.etcd.io/etcd/client/[email protected]: unrecognized import path "go.etcd.io/etcd/client/v2": reading https://go.etcd.io/etcd/client/v2?go-get=1: 503 Service Unavailable

from gopkg.

@hamdi-ben-yaflah mine was resolved as well.

from gopkg.

Hi guys, also having this issue, anyone found any solution beside trying to use GOPROXY https://proxy.golang.org ?

from gopkg.

And now…

That's a “urgent” problem while a lot of packages are referenced through gopkg.in, and we can't work on our software (build fails while getting the dependencies)

Any change to find what's the issue? (we can help on resolution)

from gopkg.

go: fyne.io/fyne/[email protected] requires
	gopkg.in/[email protected]: unrecognized import path "gopkg.in/check.v1": reading https://gopkg.in/check.v1?go-get=1: 502 Bad Gateway
	server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-check/check.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

from gopkg.

Yup happening for me too... with gopkg.in/square/go-jose.v2
Thanks to this issue, now i know i'm not the only facing this non-sense

from gopkg.

Is there any workaround at all for this (other than using the proxy, which doesn't seem to work)?

from gopkg.

from gopkg.

@saadzaman which one ?

from gopkg.

experiencing this as well

from gopkg.

Adding proxy path solved the issue for meOn 4 Nov 2022 11:07 pm, Florian PENDARIES @.> wrote: Yup happening for me too... with gopkg.in/square/go-jose.v2 Thanks to this issue, now i know i'm not the only facing this non-sense —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.>

[ec2-user@ip-10-180-29-71 ~]$ GOPROXY=https://proxy.golang.org sudo /usr/bin/go install github.com/awslabs/amazon-ecr-credential-helper/ecr-login/cli/docker-credential-ecr-login@latest
go install github.com/awslabs/amazon-ecr-credential-helper/ecr-login/cli/docker-credential-ecr-login@latest: github.com/awslabs/amazon-ecr-credential-helper/ecr-login@none updating to
        github.com/awslabs/amazon-ecr-credential-helper/[email protected] requires
        github.com/stretchr/[email protected] requires
        gopkg.in/[email protected]: unrecognized import path "gopkg.in/yaml.v3": reading https://gopkg.in/yaml.v3?go-get=1: 502 Bad Gateway
        server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

@saadzaman Is there another proxy I should use?

from gopkg.

Please see #78 for details on this week's issue.

from gopkg.

@niemeyer Is the cannot talk to GitHub issue occurring again today? I'm getting a 502 when our pipelines run and "package gopkg.in/yaml.v2: exit status 128"

from gopkg.

@niemeyer says there was a major outage this morning that is now resolved. But I am still having issues on our pipelines: https://status.canonical.com/#/incident/KNms6QK9ewuzz-7xUsPsNylV20jEt5kyKsd8A-3ptQHaFVW3sYpVjaoC6hSLL7x3PgfLD6yowK_1bYTd8bAkgg==

from gopkg.

happen to me again...

from gopkg.