T2 update not working [ Error: certificate has expired]

[oleksu535]

C:\tessel>t2 update
INFO Looking for your Tessel...
INFO Connected to MEGA.
ERR! Error: certificate has expired

[knaut]

Also getting this. Mac OS 10.12.2. Restarted the Tessel a couple times, no change.

Also happens while using t2 version

[ScottJr]

Same issue here, OSX 10.12.3. Flashed device, no change.

[ScottJr]

This seems to be an issue further reaching, I just got my Tessel, it was working one day. I flashed it and now it's pretty much bricked. It runs the script sometimes.. meaning it will boot and then run but maybe 10% of the time when the button is pressed it will log the event. Other times at run I am getting this:

/tmp/remote-script/node_modules/tessel-io/lib/index.js:322
read.callback(data.readUInt16LE(0) >> 2);
^

TypeError: data.readUInt16LE is not a function
at callback (/tmp/remote-script/node_modules/tessel-io/lib/index.js:322:28)
at null. (/usr/lib/node/tessel-export.js:314:29)
at emitNone (events.js:67:13)
at Socket.emit (events.js:166:7)
at emitReadable_ (streamreadable.js:411:10)
at emitReadable (streamreadable.js:405:7)
at readableAddChunk (streamreadable.js:157:11)
at Socket.Readable.push (streamreadable.js:110:10)
at Pipe.onread (net.js:523:20)

Something not right.. just got this yesterday.

[Grandalf]

I'm also experiencing this problem. I just opened my brand new J5IK and was working through the Experiment Guide, marvelling at the excellent quality of the tutorial, and everything was going as expected until issuing the t2 update command. I see the following:

C:\Users\User\j5ik>t2 update
INFO Looking for your Tessel...
INFO Connected to grandalf.
ERR! Error: certificate has expired

I searched for the error via Google and it brought me here. (First post! Hi!)

t2 version produces the same error.

I've tried all the obvious things; rebooting, cycling power on Tessel2, changing USB ports (at some point t2 list stopped reporting my Tessel.)

Has anyone tried using LTS v4.4.5, the version specified in the Experiment Guide? I installed the latest node.js which is v6.11.0.

EDIT: I changed my system date back one year (6/11/2016) and t2 version and t2 update appear to work as expected.

EDIT2: Rolling back the system date seems to have allowed firmware update v0.0.16 to succeed but necessitated going through a lot of the setup steps again (like naming my network and setting up wifi.) Unfortunately setting the system back to the correct date causes t2 version to display "certificate has expired" so the problem still exists. I'm going to try to proceed with the Experiment Guide. I know software is complicated but i'm pretty bummed that this beginner kit is exhibiting these problems.

[ScottJr]

@gandalf - Interesting I set my system date/time back just prior to getting mine and could not get it to work still. Not 2016 like you did. I'll have to try that tonight. Really sucks you have to keep your system time set in the past. Seems like a simple update from their end should solve this. I just got mine too, if they don't address soon I'm going to return to Amazon.

[Kelsey]

Hi all,

Sorry about the inconvenience– we somehow let our SSL certificates expire (which shouldn't have happened, but we're putting this down to a transition in ops and are putting in safeguards against it happening again).

I believe the issue you are experiencing is a continuation of that issue, which we are actively working to correct. Specifically, all of our domains except packages.tessel.io are up and running, and we're sorting out an access issue for this last subdomain.

In the meanwhile, you have two options:

1. Wait until we fix it (shouldn't be more than a couple of days)
2. Compile and update the firmware manually using the instructions found here: https://github.com/tessel/t2-firmware#compiling

Sorry again for the inconvenience, and I'll update this thread when the certificate error is resolved.

All the best,
Kelsey (Tessel Steering Committee Member)

[rwaldron]

@reconbot fixed this around 11:35am today.

This was my fault. When we addressed the cert problem last week, I was taking survey of affected domains and when I typed "builds.tessel.io" and hit enter, I observed the request successfully respond and load into the browser, but didn't notice that it did not occur over https—so I thought that it was not one of the domains that needed to be updated. Sorry for the inconvenience and frustration.

Rick

[ScottJr]

Awesome! Thank you both. At this point flash and update the device and we should be good to go?

[Grandalf]

Verified fix! Thank you Rick and Kelsey. Blinking LEDs here I come!

[rwaldron]

Again, sorry about the inconvenience and thank you for your patience

[ScottJr]

Confirmed fix on my end as well.