pip报“Cannot connect to proxy”与“Failed to establish a new connection: [Errno 113] No route to host"案例
2020-07-14 14:18 潇湘隐者 阅读(6799) 评论(0) 编辑 收藏 举报在一台新的Linux(CentOS 7.7)服务器上使用pip安装python包时遇到下面错误和告警,如下所示:
# pip install pymssql
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f8f866f3860>: Failed to establish a new connection: [Errno 113] No route to host',))': /simple/pymssql/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f8f8670d2b0>: Failed to establish a new connection: [Errno 113] No route to host',))': /simple/pymssql/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f8f8670d320>: Failed to establish a new connection: [Errno 113] No route to host',))': /simple/pymssql/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f8f866f3710>: Failed to establish a new connection: [Errno 113] No route to host',))': /simple/pymssql/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f8f866f3518>: Failed to establish a new connection: [Errno 113] No route to host',))': /simple/pymssql/
ERROR: Could not find a version that satisfies the requirement pymssql (from versions: none)
ERROR: No matching distribution found for pymssql
最后检查发现是因为代理弄错了。注意:下面敏感信息做了混淆,用xxx.xxx.xxx.xxx代替了具体IP。
export http_proxy='http://xxx.xxx.xxx.xxx:3128'
export https_proxy='http://xxx.xxx.xxx.xxx:3128'
修改/etc/profile,更改设置,如下所示
export http_proxy='http://xxx.xxx.xxx.xxx:3128'
export https_proxy='https://xxx.xxx.xxx.xxx:3128'
执行source /etc/profile使之生效,问题解决。

· 一个费力不讨好的项目,让我损失了近一半的绩效!
· .NET Core 托管堆内存泄露/CPU异常的常见思路
· PostgreSQL 和 SQL Server 在统计信息维护中的关键差异
· C++代码改造为UTF-8编码问题的总结
· DeepSeek 解答了困扰我五年的技术问题
· 一个费力不讨好的项目,让我损失了近一半的绩效!
· 清华大学推出第四讲使用 DeepSeek + DeepResearch 让科研像聊天一样简单!
· 实操Deepseek接入个人知识库
· CSnakes vs Python.NET:高效嵌入与灵活互通的跨语言方案对比
· Plotly.NET 一个为 .NET 打造的强大开源交互式图表库
2019-07-14 IndentationError: unindent does not match any outer indentation level笔记
2014-07-14 管理故事——和尚挑水的故事
2014-07-14 ORACLE优化器RBO与CBO介绍总结