SoliForum - 3D Printing Community — check for update -> 0 Error:

Re: check for update -> 0 Error:

null@example.com (sebastianboldsen) — Wed, 23 Sep 2020 17:24:18 +0000

Hi. I have the "0 Error:" as well when checking for an update.

I am on the version the scanner kit came with a few years ago.
How do I update?

Re: check for update -> 0 Error:

null@example.com (rilot) — Tue, 07 May 2019 08:22:49 +0000

In the end I decided to just use the pre-built image and apply my own customisations to that rather than the other way round. It's working well. Thanks.

Re: check for update -> 0 Error:

null@example.com (rilot) — Thu, 02 May 2019 11:47:45 +0000

Thanks for the reply @Uriah
I'll pop the image on another Pi and see if transferring works. Dependencies I can usually sort myself. Will report back.

Re: check for update -> 0 Error:

null@example.com (hairu526) — Thu, 02 May 2019 11:22:10 +0000

rilot,

We no longer offer the auto-update directly through the software but you may be able to copy the /opt/freelss-1-27/bin/freelss binary from the SD image to the already prepared card that you would like it to be on. Let me know if you have any missing dependency errors and I can provide you with the commands to install the dependencies. Whether this will work or not depends on how compatible your Linux environment is to the official ATLAS 3D environment.

Thanks,
Uriah

Re: check for update -> 0 Error:

null@example.com (rilot) — Tue, 30 Apr 2019 16:52:53 +0000

Same problem here. Running 1.22 from Github. Purchased a license yesterday and am getting the certificate expired error when trying to update the software.
I could just flash the image but I've made a lot of customisations to the base OS on the Pi image I'm using and would prefer to not have to do it all over again.

Re: check for update -> 0 Error:

null@example.com (hoopty) — Sat, 09 Feb 2019 18:51:29 +0000

UPDATE:

I FOUND URIAH to be a very helpful an honest person. I was impatient and for that I apologize.

I believe if he gets some time he will respond.

Re: check for update -> 0 Error:

null@example.com (ElisaCrow) — Wed, 28 Mar 2018 19:48:28 +0000

Nope, didn't help for me

Re: check for update -> 0 Error:

null@example.com (jz) — Wed, 28 Mar 2018 17:24:28 +0000

Just had an idea to try - change the date on you pi to prior to the cert expiry

e.g.
sudo date -s "Thu Feb 1 20:00:00 UTC 2018"

then check for the update. It just might work

Re: check for update -> 0 Error:

null@example.com (tonyno) — Mon, 26 Mar 2018 00:24:03 +0000

He usually checks in here, but I am surprised he hasn't answered yet. Give it some more time.

Re: check for update -> 0 Error:

null@example.com (rgmcleod52) — Mon, 26 Mar 2018 00:02:01 +0000

Isn't this an issue that the folks at www.murobo.com will have to fix? If so, is there any plan to update their SSL certificate or get a certificate from 'letsencrypt.org'?

Regards,

Rick

Re: check for update -> 0 Error:

null@example.com (jz) — Thu, 15 Mar 2018 18:36:06 +0000

yes, tested that url in web browser and ssl certificate has expired

Save some $ with a free certificate https://letsencrypt.org ? part of a project to make the web more secure

HTH

check for update -> 0 Error:

null@example.com (carlos.pierobon) — Sat, 10 Mar 2018 21:33:32 +0000

Hello Uriah,

I reply on this forum the email I send to you (you never gived a response):

I purchase a license key to update my FreeLss form 1.11 to 1.26, and when I try to uptade an error appears.

I put the serial number into the field on the setup page, then I try with “Check for update” and I have an “0 Error:” and nothing else.

I try with again using the lan connection instead of the wifi but the error is the same.

I running a FreeLSS version 1.11 into my Raspberry Pi model B+ with the latest Raspbian version.

The kernel is: Linux 4.14.20-v7+

The terminal says:

/updates/1520449706.989749908447265625.xml <-- https://www.murobo.com/atlas3d/updates.xml
* Trying 107.22.184.91...
* TCP_NODELAY set
* Connected to www.murobo.com (107.22.184.91) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* SSL certificate problem: certificate has expired
* Curl_http_done: called premature == 1
* stopped the pause stream!
* Closing connection 0

Two days later I try with an older Raspbian Raspbian distro “Linux Raspberry 4.1.19-v7+” by updating and recompiling but nothing to do.

I try an apt-get install ca-certificates but it's already the at newer version.

The terminal says again that the problem is an expired certificate:

/updates/1520626854.1831591129302978515625.xml <-- https://www.murobo.com/atlas3d/updates.xml
* About to connect() to www.murobo.com port 443 (#0)
* Trying 107.22.184.91...
* connected
* 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 has expired
* Closing connection #0
* Peer certificate cannot be authenticated with given CA certificates

Today I try to type on my Windows 10 Edge browser: "https://www.murobo.com/atlas3d/updates.xml" and the browser says in a red form that the certificate of the entered site is invalid or expired. Error code: DLG_FLAGS_SEC_CERT_DATE_INVALID.

At this point I think that the problem is not my Raspberry Pi but your server.

Please, can you update the certificate of your server? I don't want you do this for me, but for the comunity (all your users).

Thank you very much and sorry if I insist for the resolution of this problem.

Kind regards,
Carlos Pierobon