Updates and package installs not working on fresh install

bassybeats

So I have flashed a fresh image of RetroPie 4.8 and tried to run the update script and install a few extra emulators and everytime I run into this same error.

curl: (28) Resolving timed out after 10000 milliseconds

I have disabled IPv6 as some others users have done but still have the same issues. Whats causing this? Internet seems ping.

Screen Shot 2022-05-23 at 1.12.49 PM.png

Screen Shot 2022-05-23 at 1.13.28 PM.png

The logs don't have much in them either

Log started at: Mon 23 May 2022 01:11:46 PM NZST

RetroPie-Setup version: 4.8.1 (5cd6dd28)
System: rpi4 (armv7l) - Raspbian GNU/Linux 10 (buster) - Linux retropie 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux

= = = = = = = = = = = = = = = = = = = = =
Running post update hooks
= = = = = = = = = = = = = = = = = = = = =

= = = = = = = = = = = = = = = = = = = = =
Installing dependencies for 'joy2key' : Provides joystick to keyboard conversion for navigation of RetroPie dialog menus
= = = = = = = = = = = = = = = = = = = = =

= = = = = = = = = = = = = = = = = = = = =
Installing (binary) 'joy2key' : Provides joystick to keyboard conversion for navigation of RetroPie dialog menus
= = = = = = = = = = = = = = = = = = = = =

Compiling '/opt/retropie/admin/joy2key/joy2key.py'...
Compiling '/opt/retropie/admin/joy2key/joy2key_sdl.py'...
Compiling '/opt/retropie/admin/joy2key/osk.py'...
Already on 'master'
Your branch is up to date with 'origin/master'.
Already up to date.
HEAD is now in branch 'master' at commit 'b8645a8197d977a0492fc56341dc7248f7d7bb10'

Log ended at: Mon 23 May 2022 01:12:34 PM NZST
Total running time: 0 hours, 0 mins, 48 secs

mitu

@bassybeats said in Updates and package installs not working on fresh install:

Whats causing this?

Your configured DNS server doesn't work reliably. Do you use something like PiHole in your network ?

Internet seems ping.

Dope.

bassybeats

@mitu well that was a good hint. Even though tracert and ping tests checked out, a faulty network cable was still the culprit. Must have just been enough to connect somehow.