golang中引用自己github公开的包失败：connected host has failed to respond

原创 已于 2022-03-30 09:56:39 修改 · 981 阅读 · 1 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#golang

于 2022-03-25 14:54:51 首次发布
本文介绍在Golang编程中如何成功引用并使用自己上传到GitHub上的包。当使用gomod方式下载这些包遇到连接超时问题时，可以通过设置国内代理解决。具体操作包括修改环境变量 GOPROXY 和 GOPRIVATE。

golang编程中，想使用自己上传到github的包

使用go mod方式，下载引用自己上传的包失败：

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

更改国内代理即可

go env -w GOPROXY=https://goproxy.cn,direct
go env -w GOPRIVATE=*.corp.example.com

golang导入私有仓库
weixin_42547619的博客
10-13 2710
一、背景 在日常开发中经常需要导入自己私有库的包文件，但是使用 GOPROXY=https://goproxy.cn,direct 以后 默认下载包会从代理路径进行下载。私有仓库例如 e.coding.net 不是https www.test:6000 不是 80端口 173.9.78.90 直接ip 这类的符合规范的宝路径可能会下载不出来那么要怎么处...
关于golang1.13版本国内代理无法使用问题
小飞哥的博客
09-11 6740
golang1.13发布后 我们go get 一些资源的时候就不用通过特殊方式来下载了，官方提供了代理资源， 但是按照操作一波下来后发现出现以下问题: go get -u github.com/mdempsky/gocode package golang.org/x/tools/go/gcexportdata: unrecognized import path "gol...
解决VScode不能成功安装go插件
qq_41725131的博客
04-05 1237
解决vscode不能成功安装go插件
go get 下载包时提示 nnection failed because connected host has failed to respond 解决方法.
qq_44765926的博客
05-06 1286
go get 下载包时提示 nnection failed because connected host has failed to respond 解决方法. 第一步： 打开 cmd 输入命令配置国内镜像 第二步： go env -w GO111MODULE=on， 回车。 第三步： go env -w GOPROXY=https://goproxy.io,direct， 回车。 第一步命令 go env -w GO111MODULE=on 第二步命令 go env -w GOPROXY=https
【Electron】electron-builder打包过程中报错： A connection attempt failed—connected host has failed to respond
余浩的博客
01-24 2071
npm run build 打包报错信息如下： Get “https://github.com/electronXXXX”: dial tcp XXXX: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connecte
After restarting ComfyUI, please refresh the browser. translate\translate.go:25:2: github.com/abadojack/whatlanggo@v1.0.1: Get "https://proxy.golang.org/github.com/abadojack/whatlanggo/@v/v1.0.1.zip": dial tcp 142.251.33.81:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. translate\translate.go:28:2: github.com/andybalholm/brotli@v1.1.0: Get "https://proxy.golang.org/github.com/andybalholm/brotli/@v/v1.1.0.zip": dial tcp 142.251.33.81:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. translate\translate.go:26:2: github.com/imroc/req/v3@v3.48.0: Get "https://proxy.golang.org/github.com/imroc/req/v3/@v/v3.48.0.zip": dial tcp 142.251.33.81:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. translate\translate.go:29:2: github.com/tidwall/gjson@v1.14.3: Get "https://proxy.golang.org/github.com/tidwall/gjson/@v/v1.14.3.zip": dial tcp 142.251.33.81:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. service\service.go:23:2: github.com/gin-contrib/cors@v1.6.0: Get "https://proxy.golang.org/github.com/gin-contrib/cors/@v/v1.6.0.zip": dial tcp 142.251.33.81:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. service\service.go:24:2: github.com/gin-gonic/gin@v1.9.1: Get "https://proxy.golang.org/github.com/gin-gonic/gin/@v/v1.9.1.zip": dial tcp 142.251.33.81:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [ComfyUI-Manager] Failed to perform initial fetching 'custom-node-list.json': Traceback (most recent call last): File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\streams.py", line 347, in _wait await waiter asyncio.exceptions.CancelledError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\ComfyUI\custom_nodes\comfyui-manager\glob\manager_server.py", line 1729, in get_cache json_obj = await manager_util.get_data(uri, True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\ComfyUI\custom_nodes\comfyui-manager\glob\manager_util.py", line 146, in get_data json_text = await resp.text() ^^^^^^^^^^^^^^^^^ File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\client_reqrep.py", line 1260, in text await self.read() File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\client_reqrep.py", line 1218, in read self._body = await self.content.read() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\streams.py", line 418, in read block = await self.readany() ^^^^^^^^^^^^^^^^^^^^ File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\streams.py", line 440, in readany await self._wait("readany") File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\streams.py", line 346, in _wait with self._timer: File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\helpers.py", line 685, in __exit__ raise asyncio.TimeoutError from exc_val TimeoutError [ComfyUI-Manager] Failed to perform initial fetching 'extension-node-map.json': Traceback (most recent call last): File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\streams.py", line 347, in _wait await waiter asyncio.exceptions.CancelledError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\ComfyUI\custom_nodes\comfyui-manager\glob\manager_server.py", line 1729, in get_cache json_obj = await manager_util.get_data(uri, True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\ComfyUI\custom_nodes\comfyui-manager\glob\manager_util.py", line 146, in get_data json_text = await resp.text() ^^^^^^^^^^^^^^^^^ File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\client_reqrep.py", line 1260, in text await self.read() File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\client_reqrep.py", line 1218, in read self._body = await self.content.read() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\streams.py", line 418, in read block = await self.readany() ^^^^^^^^^^^^^^^^^^^^ File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\streams.py", line 440, in readany await self._wait("readany") File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\streams.py", line 346, in _wait with self._timer: File "C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\python\Lib\site-packages\aiohttp\helpers.py", line 685, in __exit__ raise asyncio.TimeoutError from exc_val TimeoutError FETCH ComfyRegistry Data: 5/85 FETCH ComfyRegistry Data: 10/85 FETCH ComfyRegistry Data: 15/85 FETCH ComfyRegistry Data: 20/85 FETCH ComfyRegistry Data: 25/85 FETCH ComfyRegistry Data: 30/85 FETCH ComfyRegistry Data: 35/85 FETCH ComfyRegistry Data: 40/85 FETCH ComfyRegistry Data: 45/85 FETCH ComfyRegistry Data: 50/85 FETCH ComfyRegistry Data: 55/85 FETCH ComfyRegistry Data: 60/85 FETCH ComfyRegistry Data: 65/85 FETCH ComfyRegistry Data: 70/85 FETCH ComfyRegistry Data: 75/85 FETCH ComfyRegistry Data: 80/85 FETCH ComfyRegistry Data: 85/85 FETCH ComfyRegistry Data [DONE] [ComfyUI-Manager] default cache updated: https://api.comfy.org/nodes FETCH DATA from: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/custom-node-list.json[ComfyUI-Manager] Due to a network error, switching to local mode. => custom-node-list.json => FETCH DATA from: C:\Documents\Ai\ComfyUI-aki\ComfyUI-aki-v1.6\ComfyUI\custom_nodes\comfyui-manager\custom-node-list.json [DONE] [ComfyUI-Manager] All startup tasks have been completed. [Crystools ERROR] For some reason, pynvml is not working in a laptop with only battery, try to connect and turn on the monitor [Crystools ERROR] Monitor of GPU is turning off (not on UI!) [BizyAir] Fail to get notification unread counts: Cannot connect to host api.bizyair.cn:443 ssl:default [getaddrinfo failed] 我在comfyUI中安装nunchaku有些问题 这个应该怎么修复呢
05-14
好的，用户遇到了在ComfyUI中安装nunchaku时的网络连接和依赖下载问题，需要解决方案。首先，我需要回忆常见的依赖安装问题可能的原因和解决办法。常见的包括网络超时、代理设置、镜像源更换、依赖冲突等。 用户...
GO A connection attempt failed because the connected party did not properly respond after a period..
这把躺赢
11-17 2857
1.问题 启动Go项目时，报如下错误，连接失败。问题在于代理，问题已解决。 Get "https://proxy.golang.org/github.com/xx.mod": dial tcp 216.58.200.49:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connecti
go install dial tcp 172.217.14.241:443: connectex: A connection attempt failed报错
天涯的浪子
11-06 1052
新安装的go install工具gopls，运行安装命令报错连接超时。dial tcp 172.217.14.241:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time
go get使用goproxy.cn仍然报错connectex: A connection attempt failed的解决方法
Ayka的博客
02-13 5563
执行 go get -v golang.org/x/tools/gopls 报错： package golang.org/x/tools/gopls: unrecognized import path "golang.org/x/tools/gopls": https fetch: Get "https://golang.org/x/tools/gopls?go-get=1": dial tcp 216.239.37.1:443: connectex: A connection attempt f
docker安装报error during connect: ......connected host has failed to respond
qq_41604862的博客
11-11 3931
安装 docker for windows ，下载地址：docker-for windows 安装教程参考：Win10中docker的安装与使用 根据教程安装后，docker --version 报错 在网上找了很久也没有找到解决方法，后面就试着来卸载-重启-安装，第一次重装后还是报这个错，后面又试了几次重装，报了另一个错： unable to resolve docker endpo...
go语言导入git包_导入git项目下载依赖包失败-Go语言中文社区
weixin_39778393的博客
12-20 459
1.不能选择offline work2.选中3.这里的gradle版本要与项目根目录下的gradle插件对应(自己查)，gradle可以自己下载到本地放在C:Users计算机名.gradlewrapperdistsgradle-4.9-all491wbe0x5d54n9cojs2p0zv90下，不用解压(这个文件在第一次编译时自动生成)gradle插件位置：此事，删除所有依赖包应该是可以编译的，如...
because the connected party did not properly respond after a period of time, or established connect
qq_57070423的博客
04-02 6757
出现上面报错的原因是因为当你执行命令的时候回去国外的仓库下载你需要的包,但是被防火墙拦截了,你只需要更换一下代理就可以.
【Golang记录】go项目中如何导入github包，导入包红色问题解决
每一步，都在缩短你与梦想的距离。
02-01 9565
问题描述： Golang项目中，导入包异常。 解决方案： 1.先打开导包的地址链接，确保地址正常，如果出现404了，那地址肯定错了，重新排查吧。 2.在命令行输入 go get 包的地址，如下图 如果加载缓慢，或者报错 go get github.com/kubeedge/kubeedge/tree/mappers/common: module github.com/kubeedge/kubeedge/tree/mappers/common: Get "https://proxy.
go拉取github依赖连接失败问题
m0_64656053的博客
07-19 1117
经验证，···go env -w GOPROXY=https://goproxy.cn```更改后可以正常拉取。,很明显是个代理地址，而且这个地址是访问不了的，导致连接失败，拉取不成功，这个参数是在。在go拉取github依赖时，发现显示的地址带有前缀。
Go 在编译时报 A connection attempt failed because the connected party did not properly respond after...
weixin_42852778的博客
07-11 2万+
dial tcp 172.217.163.49:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
解决golang编译提示dial tcp 172.217.160.113:443: connectex: A connection attempt failed
热门推荐
weixin_37254196的博客
12-07 11万+
废话不多说，直接开讲 还多新手朋友在编译go的过程中是不是经常会遇到这样的报错 module ***: Get “https://proxy.golang.org/***”: dial tcp 172.217.160.113:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connect
windows10专业版64位安装docker和podman遇到的坑
qq_34905631的博客
01-29 6171
很多软件的安装出现奇怪的问题最有效的办法是重装系统就可以非常好的解决了。
拉取gin框架报错
weixin_44961320的博客
05-09 1143
今天学习gin框架时，拉取github的包失败，提示： PS E:\GoSource\src\gin_demo> go get -u github.com/gin-gonic/gin go: downloading github.com/gin-gonic/gin v1.7.7 go get: github.com/gin-gonic/gin@v1.7.7: verifying module: github.com/gin-gonic/gin@v1.7.7: Get "https://sum.go
golang解决go get命令无响应问题
Mars
10-01 5万+
操作 go get -v github.com/golang/net 现象 go get github.com/golang/net: module github.com/golang/net: Get https://proxy.golang.org/github.com/golang/net/@v/list: dial tcp 216.58.220.209:443: connec...
go: golang.org/x/tools/gopls@latest: module golang.org/x/tools/gopls: Get "https://proxy.golang.org/golang.org/x/tools/gopls/@v/list": dial tcp 142.251.33.81:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
最新发布
06-15
### 解决 gopls 模块更新时的网络连接问题 在使用 Go 语言开发时，`gopls` 是官方推荐的语言服务器协议（LSP）实现，用于提供代码补全、跳转等功能。当 `gopls` 模块更新时遇到网络连接问题，通常是因为模块下载依赖于 `proxy.golang.org` 或其他镜像站点，而这些站点可能因网络限制无法正常访问[^1]。 以下是解决该问题的具体方法： #### 方法一：配置 GOPROXY 使用国内镜像 Go 官方提供了模块代理机制，可以通过设置环境变量 `GOPROXY` 来指定模块下载的代理地址。国内有许多可用的 Go 模块镜像站点，例如阿里云和清华大学开源软件镜像站。 ```bash export GOPROXY=https://goproxy.cn,direct ``` 上述命令将 `GOPROXY` 设置为 `https://goproxy.cn`，并在代理不可用时直接连接上游源码库[^2]。如果需要永久生效，可以将该命令添加到 `.bashrc` 或 `.zshrc` 文件中。 #### 方法二：离线模式 如果网络问题持续存在，可以尝试使用离线模式进行模块管理。离线模式下，Go 工具链仅从本地缓存中获取模块，而不尝试连接外部网络。 ```bash export GOOFFLINE=1 ``` 此方法适用于已经下载过所需模块的情况。若某些模块尚未缓存，则仍需通过网络下载[^3]。 #### 方法三：手动下载缺失模块 对于特定模块无法通过代理或直接连接下载的情况，可以手动下载并放置到本地模块缓存目录中。例如，针对 `gopls` 的相关依赖： 1. 找到具体的模块路径（如 `golang.org/x/tools/gopls`）。 2. 在本地克隆仓库或下载压缩包。 3. 将文件解压至 `$GOPATH/pkg/mod` 或 `$GOCACHE` 目录下的对应位置。 #### 方法四：调整模块版本 有时，特定版本的模块可能由于网络原因无法下载。可以通过修改 `go.mod` 文件中的版本号来切换到其他可用版本。例如： ```go require golang.org/x/tools v0.1.4 ``` 运行以下命令以同步更改： ```bash go mod tidy ``` 这将重新计算依赖关系并尝试下载新的模块版本[^4]。 ```python # 示例 Python 脚本用于检查模块状态 import subprocess def check_module_status(module_name): result = subprocess.run(["go", "list", "-m", module_name], capture_output=True, text=True) return result.stdout.strip() print(check_module_status("golang.org/x/tools")) ``` ###
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值