Personal dietpi-banner problem

Troubleshooting
1

I have a problem with curl and dietpi-banner.

Under dietpi-banner I have created an info with the following content under custum banner with the help of the forum here.

echo -e "Kernel | OS Release | Weather\n   Kernel : $(uname -r)\n   OS Release : $(cat /etc/debian_version)\n   Weather : $(curl -sSfLm 3 https://wttr.in/Falkensee?format=4)"

There now seem to be problems with curl on all my DietPi installations.

The output of dietpi-banner looks like this:

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

I have to admit that I don’t understand any of this and would like to ask politely what a solution to the problem might look like.
The site https://curl.se/docs/sslcerts.html
doesn’t really help me personally…

Many thanks in advance!

2

Website certificate expired two days ago. You could try to add k switch to curl command to ignore certificate check.

1 Like
3

Thank you for your feedback.
However, if you look at the website described, this is not recommended under any circumstances.
So this would seem to be “only” a temporary solution.
Is there possibly also a safe adjustment?

4

Problem is on the website, they need to renew certificate. Only solition for you now is to ignore the certificate.

5

Yes this has nothing to do with DietPi. It’s the website you are trying to reach. Simply open https://wttr.in on your Desktop and you will receive the SSL warning. Nothing we can do on this.

1 Like
6

I already thought it wasn’t DietPi. :wink:
Of course it works with the -k option.
Are the certificates renewed automatically or do I have to take action? So far it has worked and the expired certificates must have come from somewhere. :thinking:

7

Is https://wttr.in owned by you? If not, nothing you can do except contacting web site owner

8

Of course I am not the owner!
Then let’s leave it at that. Thank you!

9

We use the same website for the native whether output of the DietPi banner :sweat_smile:. Interestingly it can be accessed well via browser. We faced it in some other cases, when websites updated their Let’s Encrypt certificates a weird way, after they moved to their own R3 intermediate CA. Somehow the old invalid one is still shipped by default, but browsers seem to have implemented some workaround to pull the correct one or so.

Which Debian version do you use? Bookworm or still Bullseye?

10

certificate has been issues on December 13th. I guess it was invalid for 2 days only

1 Like
11

Ah okay, makes sense then.

12

Almost all installations are based on Bookworm. But in the meantime, the whole spook seems to be over!

1 Like