"cannot talk to GitHub"

[shivamMg]

For some reason it cannot talk to GitHub. The requests time out. GH is up. Must be something between your server and GH.

[niemeyer]

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.

[niemeyer]

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.

[niemeyer]

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.

[niemeyer]

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.

[sysradium]

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

[sysradium]

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

[niemeyer]

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.

[niemeyer]

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.

[niemeyer]

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.

[niemeyer]

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.

[niemeyer]

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

[niemeyer]

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

[niemeyer]

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.

[niemeyer]

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.

[niemeyer]

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.

[niemeyer]

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.

[sysradium]

@niemeyer unfortunately the problem is back

[sysradium]

@niemeyer unfortunately the problem is back

[niemeyer]

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

[niemeyer]

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

[Ads20000]

Problems have been reflected on GitHub System Status

[Ads20000]

Problems have been reflected on GitHub System Status

[andrewslotin]

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)

[andrewslotin]

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)

[niemeyer]

@andrewslotin Please see the last few messages above.

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

[niemeyer]

@andrewslotin Please see the last few messages above.

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

[Baha-sk]

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

Thanks!

[Baha-sk]

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

Thanks!

[mdittmer]

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 ())

[mdittmer]

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 ())

[Baha-sk]

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

[Baha-sk]

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

[esetnik]

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

[esetnik]

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

[niemeyer]

@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:

[niemeyer]

@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:

[adriamb]

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

[adriamb]

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

[esetnik]

@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.

[esetnik]

@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.

[brandoncole]

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.

[brandoncole]

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.

[glb]

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

[glb]

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

[Baha-sk]

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

[Baha-sk]

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

[sublee]

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?

[sublee]

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?

[jney]

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

[jney]

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

[niemeyer]

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

Sorry for the trouble everyone.

[niemeyer]

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

Sorry for the trouble everyone.

[sublee]

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

[sublee]

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

[acloudiator]

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)

[acloudiator]

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)