求助冬瓜大佬，望请忙里偷闲进来救急为谢

ucanf

Waiting for the Home Assistant CLI to be ready...
[WARN] Home Assistant CLI not starting! Jump into emergency console...
root@homeassistant:/ # WGTTYD CONFIG --SHELL-BIN/USR/ASH
/bin/ash: WGTTYD: not found
root@homeassistant:/ # wgttyd config --shell-bin/usr/ash
ttyd 已配置的端口                  : 7681
ttyd 已配置的web认证账户口令       :
ttyd 已配置的shell(命令行脚本环境) : /usr/sbin/hassos-cli
root@homeassistant:/ # wgturbo docker.io fastgh
设置 dockerhub(docker.io) 的加速镜像代理为: fastgh
当前配置的系统镜像加速站:
  docker.io  的镜像加速站: docker.fastgh.com
  github.com 的镜像加速站: gh.fastgh.com
  ghcr.io    的镜像加速站: ghcr.fastgh.com
root@homeassistant:/ # wgturbo ghcr.io fastgh
设置 ghcr.io 的加速镜像代理为: fastgh
当前配置的系统镜像加速站:
  docker.io  的镜像加速站: docker.fastgh.com
  github.com 的镜像加速站: gh.fastgh.com
  ghcr.io    的镜像加速站: ghcr.fastgh.com
root@homeassistant:/ # wgturbo apply -d
应用配置到当前haos系统
当前配置的系统镜像加速站:
  docker.io  的镜像加速站: docker.fastgh.com
  github.com 的镜像加速站: gh.fastgh.com
  ghcr.io    的镜像加速站: ghcr.fastgh.com
==[在线版本]============================================
设备ID: x86-64-pc       指令集兼容: amd64       设备兼容: generic-x86-64
==[安装镜像]============================================
hassio_audio    => ghcr.fastgh.com/home-assistant/amd64-hassio-audio:2023.12.0
Error response from daemon: Get "https://ghcr.fastgh.com/v2/": read tcp 192.168.3.44:48004->146.56.148.221:443: read: connection reset by peer

hassio_cli      => ghcr.fastgh.com/home-assistant/amd64-hassio-cli:2024.05.0
Error response from daemon: Get "https://ghcr.fastgh.com/v2/": read tcp 192.168.3.44:48010->146.56.148.221:443: read: connection reset by peer

hassio_dns      => ghcr.fastgh.com/home-assistant/amd64-hassio-dns:2024.04.0
Error response from daemon: Get "https://ghcr.fastgh.com/v2/": read tcp 192.168.3.44:48020->146.56.148.221:443: read: connection reset by peer

hassio_multicast        => ghcr.fastgh.com/home-assistant/amd64-hassio-multicast:2024.03.0
Error response from daemon: Get "https://ghcr.fastgh.com/v2/": read tcp 192.168.3.44:48028->146.56.148.221:443: read: connection reset by peer

hassio_observer         => ghcr.fastgh.com/home-assistant/amd64-hassio-observer:2023.06.0
Error response from daemon: Get "https://ghcr.fastgh.com/v2/": read tcp 192.168.3.44:48030->146.56.148.221:443: read: connection reset by peer

hassio_supervisor       => ghcr.fastgh.com/home-assistant/amd64-hassio-supervisor:2024.06.0
Error response from daemon: Get "https://ghcr.fastgh.com/v2/": read tcp 192.168.3.44:48042->146.56.148.221:443: read: connection reset by peer

hassio_supervisor       => ghcr.fastgh.com/home-assistant/amd64-hassio-supervisor:latest
Error response from daemon: Get "https://ghcr.fastgh.com/v2/": read tcp 192.168.3.44:48052->146.56.148.221:443: read: connection reset by peer

homeassistant   => ghcr.fastgh.com/home-assistant/generic-x86-64-homeassistant:2024.6.3
Error response from daemon: Get "https://ghcr.fastgh.com/v2/": read tcp 192.168.3.44:48056->146.56.148.221:443: read: connection reset by peer

==[启动服务]============================================
root@homeassistant:/ # Error: No such object: hassio_supervisor
[WARNING] Supervisor container did not remove the startup marker file. Assuming container image or container corruption.
Error response from daemon: No such container: hassio_supervisor
"docker image rm" requires at least 1 argument.
See 'docker image rm --help'.

Usage:  docker image rm [OPTIONS] IMAGE [IMAGE...]

Remove one or more images
jq: error: Could not open file /mnt/data/supervisor/updater.json: No such file or directory
[WARNING] Supervisor image missing, downloading a fresh one: 2024.06.0
Error response from daemon: Get "https://ghcr.fastgh.com/v2/": read tcp 192.168.3.44:48064->146.56.148.221:443: read: connection reset by peer
[ERROR] Supervisor downloading failed.

ucanf

四条指令发完还是failed。为什么？大神教我

ucanf

搞不定啊，摸鱼上班弄两天林，等瓜哥完善再安装了，或者坐等瓜哥把我的x96max整出来寄给我

达文西

ucanf 发表于 2024-6-18 21:28
搞不定啊，摸鱼上班弄两天林，等瓜哥完善再安装了，或者坐等瓜哥把我的x96max整出来寄给我 ...

read: connection reset by peer
链路被中途截断了。原因另外的帖子给你回了。

这是你的宽带运营商弄的（不是国家弄的）。
你得绕过他
1. 物理绕过（换接入商。比如尝试手机5G上网-。路由热点走手机热点ap，盒子网线连路由）
2. 科学绕过，如果接入商配的比较狠，98%以上的你能找到的方法都可能无效。
3. 等冬瓜haos未来解决
4. 等老大上线私信远程帮你单配