Read the statement by Michael Teeuw here.
Can't clone from GitHub
-
@sdetweil That one shows up first for me. In any case I tried and it still doesn’t work
-
@MMRPi1 u recompiled the git with openssl?? then it should give the gnutils error
sudo apt-get install -y build-essential fakeroot dpkg-dev sudo apt-get -y build-dep git sudo apt-get install -y libcurl4-openssl-dev mkdir git-openssl cd git-openssl apt-get source git cd git-* sed -i -e 's/libcurl4-gnutls-dev/libcurl4-openssl-dev/g' ./debian/control sed -i -- '/TEST\s*=\s*test/d' ./debian/rules sudo dpkg-buildpackage -rfakeroot -b sudo dpkg -i git_2.7.4-0ubuntu1.6_arm64.deb #CleanUp cd ../../ sudo rm -rf git-openssl You can follow This Bog or You can find simple script here to do that -
@sdetweil I tried that and got gnutls_handshake() failed: Close notify
But that’s the same error as before :/ -
@MMRPi1 then you are not running the openssl git…
u may have to run the pi admin tool for software and updates to enable source download… I had to
-
@sdetweil How do you do that?
-
“gnutls_handshake() failed: Close notify”… I’m sorry, I don’t understand this. Can you type out the exact error that you’re seeing? Including all the text after “failed”.
-
@bhepler fatal: unable to access: gnutls_handshake() failed: Close notify
-
the build process above doesn’t work. too old
-
@bhepler but he can git clone from windows on the same local network.
almost like an install failure or an sd card starting to fail.
-
@sdetweil - Yeah, this is all kinds of weird. He’s using what appears to be a consumer grade network router. He shouldn’t have to mess with proxy settings as he should just be behind the NAT functions. And even if he was, it should also affect his Windows installation.
Let’s try to reinstall git one more time, if you please:
sudo apt remove git --purge sudo apt install git -
@bhepler I don’t think its a git problem… I think its a library problem
-
@sdetweil - Yeah, at this point it may be easier to just back up the
config.jsfile and reflash the SD card. -
@bhepler Didn’t work
-
@bhepler I’d very much prefer it doesn’t come to that. I’m on a Pi 1 and I had enough (too much) trouble setting up MM in the first place (since its not officially supported), I’m kinda paranoid it won’t work this time around
-
@MMRPi1 use my installer script
see here https://github.com/sdetweil/MagicMirror_scripts
read the readme for the command to issue -
@sdetweil that to update?
-
@MMRPi1 - He has an installation script too. Use that one instead. It’s quite robust.
If you’re really paranoid about losing your data, you can make an image of your SD card before reflashing it. If anything goes wrong, you can just flash that image back onto the card.
The downside is that it’s going to take a fair amount of time to install Magic Mirror again. But I think at this point it’s going to be faster this way than to keep banging our heads against this TLS error.
-
@MMRPi1 no. install
my stuff does ONLY MagicMirror related work
so create a new sd card, get it all working, ssh, whatever
and check that git clone works (U can get this repo), just don’t use it after download
then ssh in and execute the MM install script command
-
@bhepler said in Can't clone from GitHub:
fair amount of time to install Magic Mirror again
typically less than 20 minutes
oh, use raspian buster, not jessie or stretch… too old now
-
@sdetweil said in Can't clone from GitHub:
typically less than 20 minutes
He’s on an RPI 1. That’s not typical.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login