Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repeat of issue #820 #1228

Closed
scottpettyjohn opened this issue Nov 20, 2018 · 6 comments
Closed

Repeat of issue #820 #1228

scottpettyjohn opened this issue Nov 20, 2018 · 6 comments
Assignees
Labels
status: investigating The issue is under investigation, which is determined to be non-trivial.

Comments

@scottpettyjohn
Copy link

go get -v -u cloud.google.com/go
Fetching https://cloud.google.com/go?go-get=1
https fetch failed: Get https://cloud.google.com/go?go-get=1: x509: certificate signed by unknown authority
package cloud.google.com/go: unrecognized import path "cloud.google.com/go" (https fetch: Get https://cloud.google.com/go?go-get=1: x509: certificate signed by unknown authority)

If I use the -insecure flag, I get the missing meta-tag:

go get -v -u -insecure cloud.google.com/go/...
Fetching https://cloud.google.com/go?go-get=1
https fetch failed: Get https://cloud.google.com/go?go-get=1: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Fetching http://cloud.google.com/go?go-get=1
Parsing meta tags from http://cloud.google.com/go?go-get=1 (status code 401)
package cloud.google.com/go/...: unrecognized import path "cloud.google.com/go/..." (parse http://cloud.google.com/go?go-get=1: no go-import meta tags ())

@jeanbza
Copy link
Member

jeanbza commented Nov 20, 2018

@scottpettyjohn Is this resolved now? I just tried and was met with success.

cc @broady @dfawley @jba who were on #820

@scottpettyjohn
Copy link
Author

scottpettyjohn commented Nov 20, 2018 via email

@jeanbza jeanbza added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Nov 20, 2018
@jeanbza
Copy link
Member

jeanbza commented Nov 20, 2018

That definitely sounds like a proxy issue. I'll defer to the folks I pinged.

@jeanbza jeanbza added status: investigating The issue is under investigation, which is determined to be non-trivial. and removed priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Nov 20, 2018
@scottpettyjohn
Copy link
Author

scottpettyjohn commented Nov 20, 2018 via email

@jeanbza
Copy link
Member

jeanbza commented Nov 20, 2018

No problem. We've investigated - as far as we can tell everything seems to be working OK on our side. It is likely to be your side (the corporate VPN sounds like the likely culprit). Closing this for now - please report back if you find additional reason to believe it might be something on our side.

@jeanbza jeanbza closed this as completed Nov 20, 2018
@broady
Copy link
Contributor

broady commented Nov 27, 2018

Hopefully this kind of thing becomes less common once we* have Go module proxies in place :)

  • the Go community

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: investigating The issue is under investigation, which is determined to be non-trivial.
Projects
None yet
Development

No branches or pull requests

3 participants