Ubuntu Error updating uboot

[jandvs]

I booted ubuntu on my Pine 64+ 2GB per this guide. I used the Ubuntu Base Longsleep download.  It booted just fine, but when i try to run the command to update uboot, i get this error.  The pine is connected to the network via cat-6 cable.  I can ping google.com and i can SSH to the pine from my desktop, so I know it's got a good network connection.

Code:

ubuntu@localhost:~$ sudo -i
[sudo] password for ubuntu:
root@localhost:~# /usr/local/sbin/pine64_update_uboot.sh
Checking for update ...
Downloading U-Boot image ...

curl: (56) GnuTLS recv error (-54): Error in the pull function.

root@localhost:~# /usr/local/sbin/pine64_update_kernel.sh
Checking for update ...
Downloading Linux Kernel ...

curl: (56) GnuTLS recv error (-54): Error in the pull function.
root@localhost:~#

Any ideas?

[jodybrown99]

I booted ubuntu on my Pine 64+ 2GB per this guide. I used the Ubuntu Base Longsleep download.  It booted just fine, but when i try to run the command to update uboot, i get this error.  The pine is connected to the network via cat-6 cable.  I can ping google.com and i can SSH to the pine from my desktop, so I know it's got a good network connection.

Code:

ubuntu@localhost:~$ sudo -i
[sudo] password for ubuntu:
root@localhost:~# /usr/local/sbin/pine64_update_uboot.sh
Checking for update ...
Downloading U-Boot image ...

curl: (56) GnuTLS recv error (-54): Error in the pull function.

root@localhost:~# /usr/local/sbin/pine64_update_kernel.sh
Checking for update ...
Downloading Linux Kernel ...

curl: (56) GnuTLS recv error (-54): Error in the pull function.
root@localhost:~#

Any ideas?

curl error 56 means it can't connect
http://curl.haxx.se/libcurl/c/libcurl-errors.html

try doing a curl of google.com and see if that works. ping can potentially work, but when you go to connect to a website, that can fail due to other network reasons (usually firewalls)

curl -v -k --head https://www.google.com/


(if you dont have curl, sudo apt-get install curl)

[longsleep]

Your TLS connectivity is broken. It can be as simple as wrong system time up to a full man-in-the-middle decrypting proxy. Check your setup.