1 (edited by skippy-17 2017-02-26 09:09:32)

Topic: 0 Error: when i press check for updates

i do have a liscence code

ewhen i press 0 Error: nothing happens, i do not know why

my original  i got in sd card i got from murdo 2015 no longer works

i tried B+ 2mb  and pi

any help would be greatfully recieved
do i need a new license code?

2

Re: 0 Error: when i press check for updates

Hi Skippy,

I have replied to you via your support email request.

- Uriah

3

Re: 0 Error: when i press check for updates

I am currently experiencing this issue as well.  I am currently running 1.18 (its been a while since I updated since I don't have high speed access at home).  I've verified that my serial number is valid, and have confirmed that I can see the outside world via my office's wireless network (via performing a "sudo apt-get update").

4

Re: 0 Error: when i press check for updates

Open a terminal and restart FreeLSS from there with the following commands.

sudo killall freelss
sudo /usr/local/bin/freelss

Try to perform an update again.  You should see a descriptive reason for the error message in the terminal window.  Post that here.

5

Re: 0 Error: when i press check for updates

OK, I am still getting the issue.  When run from a terminal, the output reads:

* Hostname was NOT found in DNS cache
*   Trying 107.22.184.91
* Connected to www.murobo.com (107.22.184.91) port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: none
CApath: /etc/ssl/certs
* SSL certificate problem: certificate is not yet valid
* Closing connection 0

6

Re: 0 Error: when i press check for updates

Check the current date on your Pi.  It seems to be set so far in the past that the certificate issue date has not occurred yet, which breaks the SSL connection.

The link below shows how to set the date.
https://www.raspberrypi.org/forums/view … mp;t=13313

- Uriah

7

Re: 0 Error: when i press check for updates

Thanks.  The "not yet valid" indication tweaked me to check the system date after submitting the info; turns out that NTP wasn't setting the system date (even though it was started by the system) and it was back in 2016.  Don't know why yet.  Manually set the date and it was a happy camper.  I have the update now.