2022-04-12 服务器开发-github访问失败的解决办法-优快云博客

本文档提供了解决GitHub访问问题的解决方案，通过编辑hosts文件，将GitHub的相关域名映射到特定IP地址，以确保正常访问。内容包括hosts文件的更新内容以及使用nping工具进行的验证步骤，显示了配置成功后的网络通讯情况。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

摘要:

记录github访问失败的解决办法

hosts内容:

# update: 20220222
# Github Hosts
# domain: github.com
140.82.113.4 github.com
140.82.114.9 nodeload.github.com
140.82.112.5 api.github.com
140.82.112.10 codeload.github.com
185.199.108.133 raw.github.com
185.199.108.153 training.github.com
185.199.108.153 assets-cdn.github.com
185.199.108.153 documentcloud.github.com
140.82.114.17 help.github.com

# domain: githubstatus.com
185.199.108.153 githubstatus.com

# domain: fastly.net
199.232.69.194 github.global.ssl.fastly.net

# domain: githubusercontent.com
185.199.108.133 raw.githubusercontent.com
185.199.108.154 pkg-containers.githubusercontent.com
185.199.108.133 cloud.githubusercontent.com
185.199.108.133 gist.githubusercontent.com
185.199.108.133 marketplace-screenshots.githubusercontent.com
185.199.108.133 repository-images.githubusercontent.com
185.199.108.133 user-images.githubusercontent.com
185.199.108.133 desktop.githubusercontent.com
185.199.108.133 avatars.githubusercontent.com
185.199.108.133 avatars0.githubusercontent.com
185.199.108.133 avatars1.githubusercontent.com
185.199.108.133 avatars2.githubusercontent.com
185.199.108.133 avatars3.githubusercontent.com
185.199.108.133 avatars4.githubusercontent.com
185.199.108.133 avatars5.githubusercontent.com
185.199.108.133 avatars6.githubusercontent.com
185.199.108.133 avatars7.githubusercontent.com
185.199.108.133 avatars8.githubusercontent.com
# End of the section

验证:

[root@bj-wlc-test-10-255-190-73 ~]# nping github.com

Starting Nping 0.7.70 ( https://nmap.org/nping ) at 2022-04-13 10:25 CST
SENT (0.2763s) ICMP [10.255.190.73 > 140.82.113.4 Echo request (type=8/code=0) id=62051 seq=1] IP [ttl=64 id=8452 iplen=28 ]
RCVD (0.5336s) ICMP [140.82.113.4 > 10.255.190.73 Echo reply (type=0/code=0) id=62051 seq=1] IP [ttl=33 id=55237 iplen=28 ]
SENT (1.2765s) ICMP [10.255.190.73 > 140.82.113.4 Echo request (type=8/code=0) id=62051 seq=3] IP [ttl=64 id=8452 iplen=28 ]
RCVD (1.6236s) ICMP [140.82.113.4 > 10.255.190.73 Echo reply (type=0/code=0) id=62051 seq=3] IP [ttl=33 id=55478 iplen=28 ]
SENT (2.2765s) ICMP [10.255.190.73 > 140.82.113.4 Echo request (type=8/code=0) id=62051 seq=4] IP [ttl=64 id=8452 iplen=28 ]
RCVD (2.7036s) ICMP [140.82.113.4 > 10.255.190.73 Echo reply (type=0/code=0) id=62051 seq=4] IP [ttl=33 id=55483 iplen=28 ]
SENT (3.2766s) ICMP [10.255.190.73 > 140.82.113.4 Echo request (type=8/code=0) id=62051 seq=5] IP [ttl=64 id=8452 iplen=28 ]
RCVD (3.5536s) ICMP [140.82.113.4 > 10.255.190.73 Echo reply (type=0/code=0) id=62051 seq=5] IP [ttl=33 id=55618 iplen=28 ]
SENT (4.2766s) ICMP [10.255.190.73 > 140.82.113.4 Echo request (type=8/code=0) id=62051 seq=5] IP [ttl=64 id=8452 iplen=28 ]
RCVD (4.6237s) ICMP [140.82.113.4 > 10.255.190.73 Echo reply (type=0/code=0) id=62051 seq=5] IP [ttl=33 id=55706 iplen=28 ]
 
Max rtt: 426.999ms | Min rtt: 257.197ms | Avg rtt: 331.072ms
Raw packets sent: 5 (140B) | Rcvd: 5 (230B) | Lost: 0 (0.00%)
Nping done: 1 IP address pinged in 4.62 seconds