Error with latest upgrade

Troubleshooting the Pocket NC
#1

When I shutdown services is shows this error.

Active Version: 5.5.3

DEPLOY 5.4.7

CHECK FOR UPDATESerror: Commit a905d77caacfb32f367518dcca8b7501ca2354a3be86c7d5ebc9c20f365d5926: Signature made Mon Oct 16 21:12:24 2023 using RSA key ID 8FB9D19423755DA3 BAD signature from “Pocket NC Company info@pocketnc.com” Key expired Wed Sep 20 15:59:53 2023

Regards
TP

Rotary toolpath different in F360 vs Simulator
#2

Hey @TokyoPav

This is an issue with something on our side of the update process. The solution is to re-flash your Kinetic Control microSD card with a new image of KC. After that, future updates should work as normal.

Shoot us an email at service@pentamachine.com and we can get you the necessary instructions to re-flash that card.

#3

@TokyoPav the issue is your machine has an old key for verifying software updates come from us. We updated this key back in February and have been shipping machines with the new key, but failed to realize that the new key wasn’t properly included in the software updates that older machines would receive. To update the key manually, you can ssh to your machine and run the following command:

bash <(curl -k https://ostree.pocketnc.com/import_gpg.sh)

Once that runs (should be basically instantly), you should be able to update normally.

2 Likes
#4

Thanks John
Upgrade completed.
for those watching and have the inevitable question - what’s the password?
ssh pnc.ipa.ddr.ess -l pocketnc
password is pocketnc
It tells you the username and password pair when you first try to connect but you need to use the -l switch to get the right username.
Cheers
TP

1 Like
#5

It’s been awhile, but getting something similar when trying to update from 5.5.3 to latest, and I get the following:

error: Commit 3cdc2d3a32b863ad0520239e05f8999f175531a3f939958de0f060bcf037e122: Signature made Tue Apr 1 16:30:53 2025 using RSA key ID 8FB9D19423755DA3 BAD signature from "Pocket NC Company <info@pocketnc.com>" Key expired Sun Feb 15 18:14:15 2026

Stuck.

Thanks,

Pete

#7

Thanks for the fast response! I was working from those instructions. Looks like an update to the script from Penta is needed.

1 Like
#8

Looks like there needs to be a new key. I’m guessing as there hasn’t been any updates for a long time now this has slipped through the cracks. Definitely reach out to Penta Machine suppport.
https://pentamachine.atlassian.net/wiki/spaces/KCUR/pages/581074945/Kinetic+Control+Software+Versions

1 Like
#9

Yeah, I just saw the date on your text. I deleted the reply so as to not confuse others facing the same issue.

1 Like
#10

Thanks for the update! For anyone else who may be finding their way here from Google, as I did- here’s the response I’m getting when running the bash command and getting the following

pocketnc@pocketnc:~$ bash <(curl -k https://ostree.pocketnc.com/import_gpg.sh) % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1035 100 1035 0 0 6088 0 --:--:-- --:--:-- --:--:-- 6088 The correct key is already installed If your error persists, please contact supportpocketnc@pocketnc:~$

image
image1700×554 65 KB

1 Like
#11

Did this get resolved?

#12

Not directly, but I did find a workaround to complete the update. The underlying issue is that the trust chain is broken.

This needs a proper fix on the backend. The update only works if the system time is rolled back to before the key expiration date. With the correct system time, it still fails with a BAD signature / expired key, even after updating.

If order to narrow it down, can you do me a favor next time you’re at your machine, right before shutdown? Click the check for updates button, and see if you get an error message?

#13

Hi
I periodically do the check for update and never get an error.
TP

1 Like