Error while updating to 9.02 to current version 9.1.1

[sfbuch]

Error while updating to 9.02 to current version 9.1.1

[Joulinar]

@ISquishWorms your issue is completely different as you have some DNS challenges. Check your DNS server used as you are not able to resolve github.com

@sfbuch did you already tried apt --fix-broken install?

[ISquishWorms]

Just to say I am also getting this error and was about to make a post on the same topic. I did try running the command 'apt --fix-broken install' and then tried to update again but I am still getting an error.

Details:

• Date | Thu Feb 22 23:54:16 GMT 2024
• Bug report | 59276acf-c7a9-409c-b97f-e72ce1f121ea
• DietPi version | v9.0.2 (MichaIng/master)
• Image creator |
• Pre-image |
• Hardware | RPi 4 Model B (aarch64) (ID=4)
• Kernel version | Linux RaspberryPi-4 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
• Distro | bookworm (ID=7,RASPBIAN=0)
• Command | curl -sSfLO https://github.com/MichaIng/DietPi/archive/master.tar.gz
• Exit code | 6
• Software title | DietPi-Update

Steps to reproduce:

1. ... dietpi-update
2. ...

Expected behaviour:

• ... The update should be downloaded and applied.

Actual behaviour:

• ... See above error.

Extra details:

• ...

Additional logs:

curl: (6) Could not resolve host: github.com

[ISquishWorms]

@ISquishWorms your issue is completely different as you have some DNS challenges. Check your DNS server used as you are not able to resolve github.com

Will do, I have my DNS set to PiHole using Unbound at the moment I will change that just for the update and try again. Although I did have the same error sfbuch had initially before running the "apt --fix-broken install". Also not sure why I can access github on the PC to post about the error I am having as the PC is on the same network as the PI using the same DNS?

[ISquishWorms]

Ok running the "apt --fix-broken install" fixed the issue but as Joulinar pointed out I then ran into a DNS problem which was resolved by using Cloudflare instead of my local DNS supplied by another PI using PiHole and Unbound. Never had an issue while updating using the local DNS before so not sure why this caused a problem last night. Oh well it is now solved thank you Joulinar for the assistance.

[holocronology]

UPDATE: Eventually got into dietpi-config and turned off IPv6. I think that fixed it.

Also getting this on first run:
Reference code: 51bd4ec2-d122-43e9-8502-a129b74dbbf0

Getting stuck here:

[MichaIng]

Are you having multiple GitHub accounts or are you a different person? 😄

If Pi-hole or Unbound have issues resolving a hostname, both have query logs to check what went wrong. Also check whether both services are running and whether they report errors:

systemctl status unbound pihole-FTL
journalctl -u unbound -u pihole-FTL

Resolving hostnames to IPv6 addresses and actually connecting via IPv6 are two different things. The first should always work, even if the system does not actually support/have an IPv6 address. But connecting to/downloading from that resolved IPv6 would then fail. When doing a dietpi-update or dietpi-software installation, we actually check whether connecting to an IPv6 IP works, in case it is even enabled, and do a prompt in case if fails, before doing any APT upgrade, download or whatever. If this check fails, the error dialog allows you to disable IPv6 quickly. But also quite possible that IPv6 in general works, but has issues from a particular location/network to a particular remote host. Still not 100% reliable in 2024 😞.

Since OP is quite a while ago and the other found solutions, I'll mark this as closed.