It started with first “apt-get update” where the https sources (i.e. http://archive.raspberrypi.org/) did not respond. I tried to send bug report, did not work as the request was on 443.
I passed the ‘update’ part by changing the https://’ in ‘source.list’ to http://
Now I am stuck at “Downloading current dietpi.txt” step, which is hosted in github (https://). No errors, whatsoever.
I have updated system time, tried to update certificates i.e but no luck.
Can anyone provide permanent solution, rather than a work around?
DietPi version | v6.32.2 (MichaIng/master)
Image creator | DietPi Core Team
Pre-image | Raspbian Lite
Hardware | RPi 4 Model B (armv7l) (ID=4)
Kernel version | Linux DietPi 5.4.51-v7l+ #1333 SMP Mon Aug 10 16:51:40 BST 2020 armv7l GNU/Linux
many thanks for your message. Do you have anything on your network that could block https access to the internet? Like a firewall, a proxy or a router?
root@DietPi:~# curl https://raw.githubusercontent.com/MichaIng/DietPi/master/dietpi.txt
# IMPORTANT:
# - This is intended for advanced users, unless you know what you are doing, do not edit this file. Please use the DietPi programs instead.
# - Do not remove uncommented lines, as the items are scraped by DietPi programs, on demand.
Thanks for the tip and prompt responses. Really appreciated.
Just to avoid any confusion. DietPi is not an onw OS. It’s a set of scripts installed on a base image. If you are running a Raspberry Pi device, base image used is Raspberry OS. Means, DietPi is a Raspberry OS with reduced amount of packaged installed and some configuration script on top. Therefore it should not make a difference if you are using DietPi or Raspberry OS.
Most probably it’s your geo location, because the SBC did not decide on the routing within the internet. That’s done by the network devices inside the internet. AS well a VPN (which locate you somewhere else on the globe) is overcoming the situation.
E.g. our images ship with IPv6 enabled, but IPv4 preferred via wgetrc config. For curl, such is not possible, so curl would connect via IPv6 while wget would do via IPv4 (which can be seen). So would be interesting if the following succeeds: