Upgrade from 0.3.21 to 0.3.22 not possible
ABAPRules opened this issue · 3 comments
Describe the bug
Cannot upgrade from 0.3.21 to 0.3.22
Expected behavior
Simple upgrade as usual ;-)
MyNode hardware (please complete the following information):
- Device: Raspi4
- Version 0.3.21
Additional context
HTTP 403 on http://deb.nodesource.com/node_18.x buster InRelease
-
torify curl -fsSL https://download.docker.com/linux/debian/gpg
-
gpg --batch --yes --dearmor -o /etc/apt/keyrings/docker.gpg
-
tee /etc/apt/sources.list.d/docker.list
++ dpkg --print-architecture
++ lsb_release -cs -
echo 'deb [arch=arm64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian buster stable'
-
torify apt-get update --allow-releaseinfo-change
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Err:3 https://deb.nodesource.com/node_18.x buster InRelease
403 Forbidden [IP: 104.22.5.26 443]
Hit:4 https://download.docker.com/linux/debian buster InRelease
Hit:5 https://repo.i2pd.xyz/debian buster InRelease
Hit:6 http://deb.debian.org/debian-security buster/updates InRelease
Hit:7 https://deb.torproject.org/torproject.org buster InRelease
Hit:8 http://deb.debian.org/debian buster-updates InRelease
Hit:9 http://deb.debian.org/debian buster-backports InRelease
Reading package lists...
E: Failed to fetch https://deb.nodesource.com/node_18.x/dists/buster/InRelease 403 Forbidden [IP: 104.22.5.26 443]
E: The repository 'https://deb.nodesource.com/node_18.x buster InRelease' is no longer signed. -
RC=100
-
'[' 100 -eq 0 ']'
-
printf '\n\n\n'
-
printf '##################################################\n'
################################################## -
printf 'Post upgrade script failed attempt 5. Retrying. \n'
Post upgrade script failed attempt 5. Retrying. -
printf '##################################################\n'
################################################## -
printf '\n\n\n'
I did some more research and saw that the IP 104.22.5.26 belongs to Cloudflare. And Cloudflare seems to be having problems at the moment. I'll close the bug until the problems at Cloudflare are fixed.
These issues at cloudflare do not affect the serving of cached files via the Cloudflare CDN.
So it seems to be a problem in combination with torify.
Without torify the command apt-get update --allow-releaseinfo-change works fine
Problem solved by not using Tor for System Upgrade.