Wget SSL errors : Unable to update DietPi

Troubleshooting
1

Hi Everyone!

I’d just like to say I’m quite a novice at this, so there might be something obvious I’m doing wrong (which I have overlooked).

Essentially, I’m unable to update DietPi when I enter “dietpi-update”. Instead I get the following:

–2015-11-18 17:56:49-- https://raw.githubusercontent.com/Fourdee/DietPi/master /dietpi/server_version
Resolving raw.githubusercontent.com (raw.githubusercontent.com)… 62.252.172.24 1
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|62.252.172.2 41|:443… connected.
GnuTLS: A TLS fatal alert has been received.
GnuTLS: received alert [0]: Close notify
Unable to establish SSL connection.

I get this error with a newly imaged SD card with Jessie, currently on v94.

Any help on this would be greatly appreciated.

2

Hi Stum,

Never seen this one before. Must be network related.

Can you try the following command for me and let me know what is says:

wget --no-check-certificate https://raw.githubusercontent.com/Fourdee/DietPi/master/dietpi/server_version
3

Hi,

I’ve just tried that but I get exactly the same error. I’ve tested the Internet connection through dietpi-config and that works fine.

It’s quite strange, not too sure what else to do?

4

Just a further update…

I’ve also just tried an SD card with a fresh install of Wheezy, and that does exactly the same during initial setup.

My current setup is using a Wired connection with a static IP, although I’ve also tried a wireless connection with dynamic IP - both with the same results.

I’m able to communicate fine with the Rpi2 via SSH and also install other pre-configued software fine using “dietpi-software”.

5

A quick google shows this may be an issue with Wget and certain ssl certificates types on the server (GitHub).

Can you try the following commands and let me know results please:

wget --secure-protocol=TLSv1 https://raw.githubusercontent.com/Fourdee/DietPi/master/dietpi/server_version




curl -L -O https://raw.githubusercontent.com/Fourdee/DietPi/master/dietpi/server_version
6

Hi,

I’ve just tried what you suggested, the results are below:

root@dietpi:~# wget --secure-protocol=TLSv1 https://raw.githubusercontent.com/Fo urdee/DietPi/master/dietpi/server_version
–2015-11-19 19:31:59-- https://raw.githubusercontent.com/Fourdee/DietPi/master /dietpi/server_version
Resolving raw.githubusercontent.com (raw.githubusercontent.com)… 62.252.172.24 1
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|62.252.172.2 41|:443… connected.
GnuTLS: A TLS fatal alert has been received.
Unable to establish SSL connection.
root@dietpi:~# curl -L -O https://raw.githubusercontent.com/Fourdee/DietPi/maste r/dietpi/server_version
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 5 100 5 0 0 16 0 --:–:-- --:–:-- --:–:-- 19

7

Just another thought…

Is there a way I can update wget? My current version is 1.13.4.

Do you think there would be any benefit in doing this?

8

You can download directly from the debian package list:
https://packages.debian.org/search?keywords=wget
You’ll want to download the armhf package.

Here is the package for 1.16.3-3:
https://packages.debian.org/stretch/armhf/wget/download

to install:

dpkg -i packagename.deb

You may need to manually install additional dependencies for the latest wget to install.

9

Thanks for the help, I don’t think I’m competent enough to know how to try and update wget correctly.

I don’t really know what else to try, am I really the only person with this problem trying to update using an Rpi2?

10

This is the 1st and only time a user has reported this issue. It must be related to your network in some way (WAN/LAN). Now, what the cause may be, unfortunately, i’am out of ideas.

I cant promise anything, but when I get some free time i’ll look at trying the latest wget my end, or, updating DietPi to use curl instead. If i get anywhere, i’ll let you know.

11

That’ll be great, I appreciate your help with this.

I’ve been scratching my head for a while. Just to add though - I’ve tried rebooting my router, I’ve also tried with both an Ethernet and Wireless connection to the Rpi2; both with exactly the same results.

From what I can remember, the problem began when I decided to start with a clean install of the DietPi v94 image. I started with Jessie, thought that might be it, so tried Wheezy but that was the same.

I had been previously been using DietPi and it had been working great and was also updating correctly. From memory, I think I started using it around mid to end of September, I’m wondering whether the image I used would have been v94, or perhaps something earlier?

Is it possiblity that current DietPi users started from an earlier image (before v94), and perhaps that’s why it’s updating fine (as it was originally for me),

I know I’m plucking at thin air now, just a thought though…

Many thanks again.

12

Hi All

Another newbie here!

I am experiencing the exact same problem:

RPi2, with both Wheezy and Jessie. Have tried new images and SD cards. Have the same error messages as stum100.

Would be really grateful for any help. I have tried minibian, but much prefer DietPi.

Thanks in advance.

13

Hi Huffpuffin,

Thanks for the info.

I’ll convert wget to curl throughout DietPi. This will resolve the SSL issues both of you are experiencing.
Git Ticket: https://github.com/Fourdee/DietPi/issues/125

14

Hi Dan

Your help is much appreciated.

When you manage to implement the change, will I need to download a fresh image or will update work automatically?

Thanks

15

Hi Huffpufin,

A new image will be required. I’am creating new images for the v102 release at the moment. I’ll let you guys know when they are available.

I still have to do further research on a fix for this issue, you can track it here: https://github.com/Fourdee/DietPi/issues/125#issuecomment-160417710

16

Thanks for the update. Will look out for it.

Many thanks again for your excellent service!!

17

Hi,

I’d also like to thank you for your help with this. Out of interest, I see from the bug tracker that the issue is probably network related, but I’m curious to know what potentially may cause this?

Is this something to do with the certificates used on GitHub? Or something to do with my own internal network causing the problem?

Many thanks.

18

I’am unsure what’s causing the issue, if i’m honest.

I was able to replicate the error at another address. Both of us use Virgin Media fibre but mine is fine. The only difference between the two locations is the router. I use a TP-link archer, the other address was a netgear (forgot to take model numbers :frowning:).

It could be a github/dns issue as it seems none of the wget command line options (eg: force TLS/SSL) makes a difference.

19

Hi guys, can any of you with this issue please try the following and reply with results:

wget --retry-connrefused --no-check-certificate https://raw.githubusercontent.com/Fourdee/DietPi/testing/dietpi/server_version
cat server_version

And:

curl -L https://github.com/Fourdee/DietPi/archive/testing.zip > test.zip;echo -e "Exitcode = $?";
rm test.zip
20

Hi,

Just tried both, this is what I get:

 ───────────────────────────────────────
 DietPi | 14:04 | Tue 01/12/15                               ───────────────────────────────────────
 V94 | Raspberry Pi 2 (1GB)                                  ───────────────────────────────────────

 Created by: Dan Knight
 DietPi Website: http://dietpi.net                           Donate and support DietPi: http://goo.gl/DCY1vq

 Commands:
 dietpi-config    = Feature rich system configuration tool.
 dietpi-software  = Select / Install optimized software.
 dietpi-uninstall = Remove DietPi Installed Software.
 dietpi-bugreport = Found an issue or bug? Let us know!
 htop             = Resource monitor.
 cpu              = Shows CPU information and stats.

root@NETSERV:~# wget --retry-connrefused --no-check-certificate https://raw.githubusercontent.com/Fourdee/DietPi/testing
root@NETSERV:~# wget --retry-connrefused --no-check-certificate https://raw.githubusercontent.com/Fourdee/DietPi/testing/dietpi/server_version                                      --2015-12-01 14:06:03--  https://raw.githubusercontent.com/Fourdee/DietPi/testing/dietpi/server_version                 Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 62.252.172.241
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|62.252.172.241|:443... connected.
GnuTLS: A TLS fatal alert has been received.
GnuTLS: received alert [0]: Close notify
Unable to establish SSL connection.
root@NETSERV:~# cat server_version
cat: server_version: No such file or directory
root@NETSERV:~#
root@NETSERV:~#
root@NETSERV:~# curl -L https://github.com/Fourdee/DietPi/archive/testing.zip > test.zip;echo -e "Exitcode = $?";
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--100   120    0   120    0     0    234      0 --:--:-- --:--:-- --:--:--   238
  0     0    0     0    0     0      0      0 --:--:-- --:--100  218k  100  218k    0     0   145k      0  0:00:01  0:00:01 --:--:--  266k
Exitcode = 0
root@NETSERV:~# rm test.zip