Certificates issue with wget #65
Comments
|
Did you read the readme? |
|
Yes, this happened suddenly after almost a year of running this script with no problems. |
|
Does Can you wget from any https page? |
|
Running with ERROR: certificate common name I saw, the cdn that GitHub uses is fastly and for some unknown reason couldn't identify the domain you were accessing (raw.github.com) so the server gave you the fastly generic ssl certificate causing wget fail because is not the site it asked for... Why the server is not identifying what domain is your wget is asking for? I don't know... can be a proxy forwarding bad info, can be a temporal issue, can be a bug on wget... don't really know... If you don't have proxys I think that the issue will disappear like it appeared... |
|
@popcornmix I get the same error with your suggested command. I don't use a proxy. |
|
Very funny, really... Have a look to this: So is not your issue, seems that GitHub's CDN it's failing... |
|
Interesting. So I should just wait till they fix it. |
|
I had some issues a few days ago too, not certificate related ( Hexxeh/rpi-firmware#7 ) but mostly pointing out that github itself seems at fault. |
|
Is this working again? |
|
No, still the same error. |
|
Update: |
|
To solve this issue, you could just add |
|
Another update: |
|
So do you believe it is a bug in older version of wget? |
|
After digging the internet I saw that wget debian packages prior to 1.14-1 don't have SNI [1] support so the webserver don't know which ssl certificate needs to use. I've checked and my failing machine has 1.12 and the working machine 1.14 :) For more info: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653267 |
|
I've also received reply from github support:
So someone should put the 1.14 version of wget on apt-get repositories for the old soft-float debian, so people could update it easily without compiling everything. |
The soft float debian should be the standard debian wheezy packages. Have you run |
|
Good job on finding the root cause. Currently the standard wget version in the wheezy repos is 1.12 (http://packages.debian.org/stable/wget). A quick fix for the meantime could be to add |
|
wheezy is not stable though: Which is newer than my Ubuntu 11.10 machine... |
|
Good point, I used the wrong link (first result habit on Google). Here's the overview: http://packages.debian.org/search?keywords=wget |
|
This is the debian I have:
|
|
@shrx |
|
Yeah, I got my raspberry pi in may 2012, and wheezy came out much later, when I already got my entire system set up and running. So I decided to not upgrade and deal with everything again. And afaik I can't just use wheezy packages on squeeze? |
|
I just got this errors, |
|
It is working for me at the moment: Not sure if it was a temporary glitch (I did notice that github web interface was very slow yesterday, but seems better today), or it's something location dependent. Can you try again now? |
|
It still doesn't work. I'm from Czech Republic, and github.com resolved to 192.30.252.131 and raw.githubusercontent.com resolved to 185.31.17.133. |
|
Exactly the same error for me. The redirection resolved first to 185.31.17.133 and then to 185.31.16.133 and neither worked. Tried on two raspis, both at the end of the upgrade process so already up-to-date software. wget version 1.13.4. Not a firewall issue - I can see the traffic tootling off over the www just fine. |
|
Ah, from the posts on the Troubleshooting forum at http://www.raspberrypi.org a lot of people are seeing the same fault. |
|
OK, on an old raspi, not up-to-date software but same wget version, the self update works just fine. Looks like something has happened in a piece of code we pick up elsewhere. |
|
@popcornmix seems to be a little random because sometimes fails and sometimes works for me on the RPi. On Ubuntu you probably have a greater version like me on Debian or Arch. |
|
after getting the updated file using curl it works fine |
|
So, to get from the current rpi-update to the latest rpi-update you should be able to run: |
|
Hi. root@raspberrypi:~# rpi-update |
|
Thanks popcornmix your post above to get from current to latest works fine on the two pis on which it failed yesterday |
|
Github interprets "`" tags as markdown, the alternative non-ambiguous command is |
Works great for me thanks, |
|
@popcornmix : said: "Strangely rpi-update is still working just fine for me. I've run it multiple times, and can wget from github both on Pi and Ubuntu." -using fresh wheezy image, then dist-upgrade, then rpi-update => will fai.l -using fresh wheezy image, then rpi-update then dist-upgrade => works fine. EDIT 2014-03-27 08:30: |
|
I've updated the rpi-update debian package. You can |
|
It's works fine for me ! |
|
The solution from @asb did the trick for me :) |
|
@shrx okay to close? |
|
I am experiencing the same issues in this thread. This issue is most definitely not closed. If I do It just says it can't find rpi-update If I try: the script downloads but if I try to run it the whole thing fails. I don't know how to add --no-check-certificate to the script. I tried in the URL but it failed. I'm just trying to get my rpi up and running because I got my pi from the store with an SD card that was carrying a raspbian version that causes a kernel panic when I plug in a wired keyboard. rpi-update should fix that but it doesn't work. These are my first steps into Linux and it's like a nightmare so far. Everything I try is like a beartrap. |
|
The correct command is: If that doesn't work might be worth installing an official image from here: You can also manually install it with: |
|
This is an official raspbian release but it just needs to be updated. I didn't buy this at the corner shop I bought it at RS Components. when I try the first one some updates come through but the rest is When I try the curl command I just get |
|
This really needs to be taken to the forums. curl has been included on the Foundation's Raspbian image since June 2012. What does your /etc/rpi-issue say? |
|
Apparently my starter pack was older. uname -a says |
|
That's ancient. You didn't buy it recently did you? I strongly, strongly recommend you download a new image and reflash your SD card. |
|
I bought last year but I only got around to using it now. I dread flashing my card because I only have windows machines and I hear that can cause some problems too. |
|
As long as you follow the official instructions you should be fine. Even using Windows :-) |
Use curl instead of wget in Vagrantfile to fetch the install script due to a bug in the default version of wget on Debian Squeeze. Fixes #1691 > wget debian packages prior to 1.14-1 don't have SNI [1] support so the > webserver don't know which ssl certificate needs to use > > – Hexxeh/rpi-update#65 (comment)
Use curl instead of wget in Vagrantfile to fetch the install script due to a bug in the default version of wget on Debian Squeeze. Fixes #1691 > wget debian packages prior to 1.14-1 don't have SNI [1] support so the > webserver don't know which ssl certificate needs to use > > – Hexxeh/rpi-update#65 (comment)
|
It looks like this issue has been resolved and can therefore be closed. |
and others
output of running
sudo rpi-update:The text was updated successfully, but these errors were encountered: