-
Notifications
You must be signed in to change notification settings - Fork 368
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
[Feature]: For China Users Internet Problems! 安装时出现网络错误的方案 #135
Comments
但是还是不能下载下来这个macos. |
It seems like that your cannot access dockerhub, which is also block by GFW. I guess you need to use web proxy... Try Set enviroment variables HTTP_PROXY and HTTPS_PROXY to your proxy address, like docker 的仓库也被墙了, 你没有代理的话没办法访问docker仓库. 你看看你电脑能不能上 |
thanks,非常感谢,但是大哥,我运行后,日志显示 然后我手动访问了:http://oscdn.apple.com/content/downloads/28/14/042-23155/4rscm4lvp3084gutfgpkwj5eex0yyxmzkt/RecoveryImage/BaseSystem.chunklist 我的配置如下: |
你手动访问 我在使用这个项目的时候, 也同样遇到了报错, 但是事件有带你就, 不太确定和你的错误是否是同一个. 但是这个报错并不影响执行. 你可以通过http访问你设备上的8006端口(如果你在本机运行 就在浏览器粘贴 http://127.0.0.1:8006/), 检查 novnc 是否启动成功. |
Is your proposal related to a problem?
This is an excellent project; however, due to China's internet restrictions, we cannot easily use this project to complete macOS installations. Through my testing, I found that during installation, it is not possible to use Alibaba's DNS service (223.5.5.5). This is because Alibaba DNS redirects
swcdn.apple.com
toswcdn.apple.com.w.alikunlun.com
, which prevents the installation from completing. Whether downloading directly or via a VPN (many VPN providers default to using this DNS), this DNS cannot be used!A solution is as follows(Using Google DNS by):
这是一个非常好的项目, 但是由于中国网络的原因, 我们无法简单的使用此项目完成苹果系统的安装. 经过我的测试, 发现安装此项目时, 不能够使用alibaba提供的dns服务, (223.5.5.5). 因为alibaba dns 会将
swcdn.apple.com
重定向到swcdn.apple.com.w.alikunlun.com
, 这会导致无法完成系统的安装. 不论是直接下载还是通过VPN下载(很多VPN服务提供商都会默认使用该dns), 都不能够使用此dns!一个比较好的解决方法如下(即在 docker-compose 中指定 DNS 为 Google DNS):
Describe the solution you'd like.
Specified DNS:
Describe alternatives you've considered.
None
Additional context
No response
The text was updated successfully, but these errors were encountered: