Was the software title installed freshly or updated/migrated?
installed freshly
Can this issue be replicated on a fresh installation of DietPi?
← If you sent a “dietpi-bugreport”, please paste the ID here →
Bug report ID | echo $G_HW_UUID
f824e029-c7c2-42d6-a6d8-54890ab4626f
Steps to reproduce
I just write the current image for the raspberry and connect via terminal
Expected behaviour
Package updates completed successfully
Actual behaviour
The update fails and ends with a screen with error logs
Extra details
I also checked the same thing with my other computer NanoPi Neo3 and got exactly the same result, I also tried another router and again nothing changes. This screen with error logs appears even when I try to log in Dietpi-Software.
APT update │
│ - Command: apt-get -y -eany update │
│ - Exit code: 100 │
│ - DietPi version: v9.12.1 (MichaIng/master) | HW_MODEL: 4 | HW_ARCH: 3 | DISTRO: 7 │
│ - Error log: │
│ Ign:1 https://dietpi.com/apt bookworm InRelease │
│ Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease │
│ Hit:3 https://deb.debian.org/debian bookworm InRelease │
│ Ign:4 https://dietpi.com/apt all InRelease │
│ Hit:5 https://deb.debian.org/debian bookworm-updates InRelease │
│ Hit:6 https://deb.debian.org/debian-security bookworm-security InRelease │
│ Hit:7 https://deb.debian.org/debian bookworm-backports InRelease │
│ Ign:1 https://dietpi.com/apt bookworm InRelease │
│ Ign:4 https://dietpi.com/apt all InRelease │
│ Ign:1 https://dietpi.com/apt bookworm InRelease │
│ Ign:4 https://dietpi.com/apt all InRelease │
│ Err:1 https://dietpi.com/apt bookworm InRelease │
│ Could not handshake: Error in the pull function. [IP: 188.114.97.11 443] │
│ Err:4 https://dietpi.com/apt all InRelease │
│ Could not handshake: Error in the pull function. [IP: 188.114.97.11 443] │
│ Reading package lists... │
│ E: Failed to fetch https://dietpi.com/apt/dists/bookworm/InRelease Could not handshake: Error in the pull function. │
│ [IP: 188.114.97.11 443] │
│ E: Failed to fetch https://dietpi.com/apt/dists/all/InRelease Could not handshake: Error in the pull function. [IP: │
│ 188.114.97.11 443] │
│ E: Some index files failed to download. They have been ignored, or old ones used instead. │
│ │
│ Retry : Re-run the last command that failed │
│ DietPi-Config : Edit network, APT/NTP mirror settings etc │
│ Open subshell : Open a subshell to investigate or solve the issue │
│ Send report : Upload bug report including system info to DietPi │
│ Print report : Print bug report template for GitHub or forum │
│ ●─ Devs only ─────────────────────────────────────● │
│ Change command : Adjust and rerun the command │
│ │
│ │
│ <Select> <Exit>
Here is the content of the screen that ends the update. If this is a problem on my provider’s side, please tell me how to ask them a question to solve this problem.
The provider claims that it hasn’t changed any settings recently. However, everything worked fine on the previous build, then I noticed that I couldn’t do version updates, they all ended with this screen.
login as: root
root@192.168.0.109's password:
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
─────────────────────────────────────────────────────
DietPi v9.12.1 : 18:32 - Sun 05/18/25
─────────────────────────────────────────────────────
- LAN IP : 192.168.0.109 (eth0)
[ OK ] DietPi-Software | Initialised database
[ OK ] DietPi-Software | Reading database
DietPi-Software
─────────────────────────────────────────────────────
Step: Applying initial first run setup steps
[ OK ] DietPi-Software | Checking IPv4 network connectivity
[ OK ] DietPi-Software | Checking DNS resolver
[ OK ] DietPi-TimeSync | systemctl stop systemd-timesyncd
[ OK ] DietPi-TimeSync | mkdir -p /run/systemd/timesync
[ INFO ] DietPi-Software | APT update, please wait...
Ign:1 https://dietpi.com/apt bookworm InRelease
Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:3 https://deb.debian.org/debian bookworm InRelease
Ign:4 https://dietpi.com/apt all InRelease
Hit:5 https://deb.debian.org/debian bookworm-updates InRelease
Hit:6 https://deb.debian.org/debian-security bookworm-security InRelease
Hit:7 https://deb.debian.org/debian bookworm-backports InRelease
Ign:1 https://dietpi.com/apt bookworm InRelease
Ign:4 https://dietpi.com/apt all InRelease
Ign:1 https://dietpi.com/apt bookworm InRelease
Ign:4 https://dietpi.com/apt all InRelease
Err:1 https://dietpi.com/apt bookworm InRelease
Could not handshake: Error in the pull function. [IP: 188.114.97.11 443]
Err:4 https://dietpi.com/apt all InRelease
Could not handshake: Error in the pull function. [IP: 188.114.97.11 443]
Reading package lists...
E: Failed to fetch https://dietpi.com/apt/dists/bookworm/InRelease Could not handshake: Error in the pull function. [IP: 188.114.97.11 443]
E: Failed to fetch https://dietpi.com/apt/dists/all/InRelease Could not handshake: Error in the pull function. [IP: 188.114.97.11 443]
E: Some index files failed to download. They have been ignored, or old ones used instead.
[FAILED] DietPi-Software | APT update
- Command: apt-get -y -eany update
[FAILED] DietPi-Software | Unable to continue, DietPi-Software will now terminate.
─────────────────────────────────────────────────────
DietPi v9.12.1 : 18:37 - Sun 05/18/25
─────────────────────────────────────────────────────
- LAN IP : 192.168.0.109 (eth0)
[ OK ] DietPi-Login | Desired setting in /boot/dietpi.txt was already set: AUTO_SETUP_AUTOMATED=0
root@DietPi:~#
apt update
root@DietPi:~# apt update
Ign:1 https://dietpi.com/apt bookworm InRelease
Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease
Ign:3 https://dietpi.com/apt all InRelease
Hit:4 https://deb.debian.org/debian bookworm InRelease
Hit:5 https://deb.debian.org/debian bookworm-updates InRelease
Hit:6 https://deb.debian.org/debian-security bookworm-security InRelease
Hit:7 https://deb.debian.org/debian bookworm-backports InRelease
Ign:1 https://dietpi.com/apt bookworm InRelease
Ign:3 https://dietpi.com/apt all InRelease
Ign:1 https://dietpi.com/apt bookworm InRelease
Ign:3 https://dietpi.com/apt all InRelease
Err:1 https://dietpi.com/apt bookworm InRelease
Could not handshake: Error in the pull function. [IP: 188.114.97.11 443]
Err:3 https://dietpi.com/apt all InRelease
Could not handshake: Error in the pull function. [IP: 188.114.97.11 443]
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch https://dietpi.com/apt/dists/bookworm/InRelease Could not handshake: Error in the pull function. [IP: 188.114.97.11 443]
W: Failed to fetch https://dietpi.com/apt/dists/all/InRelease Could not handshake: Error in the pull function. [IP: 188.114.97.11 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.
root@DietPi:~#
My local time is 10:10:35
I am in the Russian Federation.
I changed it in the settings ru_RU.UTF-8
But the system time has not changed. The time has not changed.
I set up my time, now it is displayed correctly (Ekaterinburg, it turns out, belongs to the Asia region):
root@DietPi:~# date
Mon May 19 10:50:45 +05 2025
However, this did not solve the problem of updating the dietpi:
root@DietPi:~# sudo apt update
Ign:1 https://dietpi.com/apt bookworm InRelease
Ign:2 https://dietpi.com/apt all InRelease
Hit:3 https://deb.debian.org/debian bookworm InRelease
Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:5 https://deb.debian.org/debian bookworm-updates InRelease
Hit:6 https://deb.debian.org/debian-security bookworm-security InRelease
Hit:7 https://deb.debian.org/debian bookworm-backports InRelease
Ign:1 https://dietpi.com/apt bookworm InRelease
Ign:2 https://dietpi.com/apt all InRelease
Ign:1 https://dietpi.com/apt bookworm InRelease
Ign:2 https://dietpi.com/apt all InRelease
Err:1 https://dietpi.com/apt bookworm InRelease
Could not handshake: Error in the pull function. [IP: 172.67.193.183 443]
Err:2 https://dietpi.com/apt all InRelease
Could not handshake: Error in the pull function. [IP: 172.67.193.183 443]
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch https://dietpi.com/apt/dists/bookworm/InRelease Could not handshake: Error in the pull function. [IP: 172.67.193.183 443]
W: Failed to fetch https://dietpi.com/apt/dists/all/InRelease Could not handshake: Error in the pull function. [IP: 172.67.193.183 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.
I just connected my router to the hotspot configured on my phone. It’s a different ISP. And my dietpie updated without any problems. But this was done only for verification, later I will definitely check what you suggested.
I would also like to ask - is it possible to restore my previous installation of dietpi-bullseye to another microsd, which stopped loading after my attempts to solve this problem using Google? The contents of the microsd are accessible from the computer. Maybe I can send here the contents of some file for diagnostics?
No. At first it refused to reboot, I pulled out the power supply with my hand, then plugged it in and it didn’t show up on the network anymore.
Then I installed another microSD and wrote a new bookworm image, which is what I came here with.
Okay, I’ll set up the dietpi again, no big deal.
Tomorrow I will check the command that was recommended to me in message #7. I hope it will work, since updating packages and installing programs by connecting the router to the access point is very troublesome and inconvenient for me.
Thank you for helping and promoting such an important and useful product.
I installed and traced it to 188.114.97.11
Did I choose the right IP?
root@DietPi:~# traceroute 188.114.97.11
traceroute to 188.114.97.11 (188.114.97.11), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.816 ms 0.699 ms 507.399 ms
2 10.0.128.1 (10.0.128.1) 3.031 ms 3.039 ms 3.041 ms
3 172.31.0.148 (172.31.0.148) 3.587 ms 3.614 ms 3.682 ms
4 172.31.0.144 (172.31.0.144) 3.274 ms 3.286 ms 3.293 ms
5 172.31.129.44 (172.31.129.44) 4.686 ms 172.31.129.32 (172.31.129.32) 4.757 ms 172.31.129.40 (172.31.129.40) 4.888 ms
6 172.31.129.37 (172.31.129.37) 3.283 ms 1.602 ms 1.649 ms
7 172.31.127.222 (172.31.127.222) 5.565 ms 5.593 ms 5.683 ms
8 172.31.128.244 (172.31.128.244) 2.738 ms 2.875 ms 2.892 ms
9 * * *
10 87.226.169.209 (87.226.169.209) 3.760 ms 4.220 ms 4.229 ms
11 * * 185.140.148.153 (185.140.148.153) 25.994 ms
12 95.71.2.226 (95.71.2.226) 29.310 ms 27.998 ms 27.874 ms
13 172.68.8.49 (172.68.8.49) 30.605 ms * *
14 188.114.97.11 (188.114.97.11) 24.999 ms 25.075 ms 25.069 ms
traceroute works as well, but as noted by Joulinar, use the hostname dietpi.com, as this is what fails (the TLS handshake with whichever host the route ends).
I sent both traces to my ISP (traceroute and mtr -r). They sent me the following response. According to the trace, the resource is available:
According to both traces, there is a connection to the server and it ends with the server address 184.21.12.65.
We recommend contacting the server administrator to clarify whether your IP address is blocked when connecting.
