is this expected atm? ```for path in \ /v1-relea...
# rke2
b
is this expected atm?
Copy code
for path in \
  /v1-release/channels \
  /v1-release/channels/stable \
  /v1-release/channels/latest
do
  echo "$path"
  curl -sSL -o /dev/null \
    -w 'HTTP %{http_code} redirect=%{url_effective}\n' \
    "<https://update.rke2.io>$path"
done
/v1-release/channels
HTTP 404 redirect=<https://update.rke2.io/v1-release/channels>
/v1-release/channels/stable
HTTP 404 redirect=<https://update.rke2.io/v1-release/channels/stable>
/v1-release/channels/latest
HTTP 404 redirect=<https://update.rke2.io/v1-release/channels/latest>
Copy code
curl -sfL <https://get.rke2.io> | INSTALL_RKE2_METHOD="tar" INSTALL_RKE2_CHANNEL="v1.34" sh - && {
  systemctl is-enabled rke2-server && systemctl restart rke2-server
  systemctl is-enabled rke2-agent && systemctl restart rke2-agent
}
[INFO]  finding release for channel v1.34
[INFO]  using v1.34 as release
[INFO]  downloading checksums at <https://github.com/rancher/rke2/releases/download/v1.34/sha256sum-amd64.txt>
curl: (22) The requested URL returned error: 404
b
I don't think so...
<https://update.rke2.io/v1-release/channels/stable>
shouldn't be 404, but go to 1.36.5
I think you might need to set
INSTALL_RKE@_CHANNEL="v1.36.5+rke2r1"
and not just v1.34 but idk.
b
For years now I have used the same syntax so something else must be off on the servers or something
b
¯\_(ツ)_/¯
the
/channels/stable
gets redirected to to that 1.36.5 release for me, but your logs show 404
b
Maybe it was fixed. I will try again shortly
🤞 1
yeah, seems like it was fixed and something was indeed broken for a time