mirrorservice.org cannot be contacted
-
Hi,
I've done a fresh install of retropie (latest image) and been trying to perform update via:
"sudo apt-get dist-upgrade" via SSHDuring the process I get a number of failed fetches due to (1 example):
Failed to fetch http://www.mirrorservice.org/sites/archive.raspbian.org/raspbian/pool/main/p/publicsuffix/publicsuffix_20211109.1735-0+deb10u1_all.deb
Cannot initiate the connection to www.mirrorservice.org:80 (2001:630:341:12::184). - connect (101: Network is unreachable)Is there a way to use another connection to update?
Or is this something that will resolve itself over time? -
Try to update the system from RetroPie Menu. Check the RetroPie docs : https://retropie.org.uk/docs/Updating-RetroPie/
-
@windg
I've tried that also, it runs into the same error and is then bypassed by the update command and continues with core updates. All cores successfully update, but the underlying kernel/OS fails due to this connection error. -
This is the full response to the upgrade request:
https://pastebin.com/fDhtN0skOddly some other upgrade components have successfully downloaded, the request starts at 63% before these errors generate.
-
So on further investigation it looks like my ISP is blocking mirrorservice.org
I can connect to the site via VPN, but not directly.Is there any way to run the updates through VPN on retropie?
-
Or anyway to change the url that "sudo apt-get dist-upgrade" uses?
-
@Tomstar2000 said in mirrorservice.org cannot be contacted:
Or anyway to change the url that "sudo apt-get dist-upgrade" uses?
Is that what
/etc/apt/sources.list
is?deb http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi # Uncomment line below then 'apt-get update' to enable 'apt-get source' #deb-src http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi
-
@sleve_mcdichael
Thanks, yes this led me down the right path!I updated the url in there from one from the following site:
https://www.raspbian.org/RaspbianMirrorsIt now seems to be upgrading packages correctly :)
-
The issue seems to be the mirror chosen supports IPv6 and the PI tries to connect via IPv6 to it, then fails. Changing the mirror may work, but you can also configure
apt
to use IPv4 only - see here.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.