go
module_error
ai_generated
true
go: module github.com/foo/[email protected]: reading https://proxy.golang.org/github.com/foo/bar/@v/v1.2.3.mod: 404 Not Found
ID: go/module-not-found-reading-https-proxy
80%Fix Rate
88%Confidence
0Evidence
2024-02-11First Seen
Version Compatibility
| Version | Status | Introduced | Deprecated | Notes |
|---|---|---|---|---|
| 1.16+ | active | — | — | — |
| 1.21+ | active | — | — | — |
Root Cause
The module version does not exist on the configured proxy or the module path is wrong/mis-cased. Go module paths are case-sensitive and require the exact tag (e.g. v1.2.3, not v1.2).
generic中文
所请求的模块版本在代理上不存在,或模块路径拼写/大小写错误。Go 模块路径区分大小写,且需要精确的 tag(如 v1.2.3,而非 v1.2)。
Workarounds
-
95% success
git ls-remote --tags https://github.com/foo/bar | grep v1.2.3 go get github.com/foo/[email protected]
-
90% success
GOPRIVATE=github.com/foo/* GONOSUMDB=github.com/foo/* GOPROXY=direct go get github.com/foo/[email protected]
-
80% success
go get github.com/foo/bar@<commit-sha>
Dead Ends
Common approaches that don't work:
-
70% fail
go still needs to resolve the original module graph and reports 'replacement directory does not exist'
-
85% fail
clearing cache does not create a missing version on the proxy
-
90% fail
does not change remote availability of the module version