Provisionning new device failn using Torizon platform

Technical Support
, , , , ,
1

Hello Toradex Community,

I’ve tried to provision a new device to my Torizon Platform accoun using the Torizon OS provisionning command but when I paste the command nothing happens.

This is not the first time I use this commad and pretty used to it, even with the latest deisng on Torizon Platform the command was working.

He is an example of the command I’m getting :

curl -fsSL https://app.torizon.io/scripts/provision-device.sh | sudo bash -s – -t “eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJzYUowczhvMjY4WTdRSzA5R0dmOXJLLVNhS3RMTWNLMkhYcGlqN2pWSm5ZIn0.eyJleHAiOjE3Nzg1OTQzMTksImlhdCI6MTc3ODU5NDAxOSwianRpIjoiNzZkMDg1NzMtMmJjMC00MDJiLTliYjgtMTIzMTUzODM2ZGMxIiwiaXNzIjoiaHR0cHM6Ly9rYy50b3Jpem9uLmlvL2F1dGgvcmVhbG1zL290YS11c2VycyIsImF1ZCI6InByb3Zpc2lvbi1kZXZpY2UiLCJzdWIiOiJjZjNmOThjNC1lZjUyLTQwM2ItODU3Ny1kNWM2MDkxYTRjZDMiLCJ0eXAiOiJCZWFyZXIiLCJhenAiOiJwcm92aXNpb24tZGV2aWNlIiwic2Vzc2lvbl9zdGF0ZSI6ImI4N2VlYmQxLTdkYzgtNDk1YS04YzE3LTU5YTU5MmNhZTI1MSIsImFsbG93ZWQtb3JpZ2lucyI6WyJodHRwczovL2FwcC50b3Jpem9uLmlvIiwiaHR0cHM6Ly9hcHAtdjEudG9yaXpvbi5pbyJdLCJzY29wZSI6InByb2ZpbGUgZW1haWwiLCJzaWQiOiJiODdlZWJkMS03ZGM4LTQ5NWEtOGMxNy01OWE1OTJjYWUyNTEiLCJlbWFpbF92ZXJpZmllZCI6ZmFsc2UsIm5hbWVzcGFjZSI6IjczYzMxMzBiLWU0ZjYtNDIzOC1hN2VmLTM0NjgxYTc3NGY1MCIsIm5hbWUiOiJQcm9lbmdpbiIsInByZWZlcnJlZF91c2VybmFtZSI6InNvbHV0aW9uc0Bwcm9lbmdpbi5jbG91ZCIsImdpdmVuX25hbWUiOiJQcm9lbmdpbiIsImVtYWlsIjoic29sdXRpb25zQHByb2VuZ2luLmNsb3VkIiwidHpuX3Njb3BlcyI6WyJjcmVhdGU6ZGV2aWNlcyJdfQ.LwLNIAaZyevc3HW4bphEI1z4VeAswacVLBBXer892SzUOsTqd5HCG3SX7gcMbev0xIKexqJwu54uQdhrZrsnP_edIoFZTYZr_kZFuvIZVjaETKCLkfahud9Nw5cesilYflYtdoY47r-835DB2wkKY470KrUrxGxwLb3Tro–B13c9xDsitcMrq2mX0BUPgV6tFKykUTHD4lzy9hhUL3QJZph9WmyVlc8t7he9jZkJwbjr0i5KpHgeCywgn-M4N9GT2fyvNfAg6dIPfNlBSWnjBmySoX0glc2yzvgBkgfwiS67I4aTOG2U1kOFt7CkOuyYNwVU7ToTZtj5fTuP2ciCQ” -u https://app.torizon.io/api/accounts/devices -g https://dgw.torizon.io && sudo systemctl restart aktualizr fluent-bit.

Before bringing the issue here I’ve asked Claude for some workaround and here are the command that solve the issue :

curl -vL https://app.torizon.io/scripts/provision-device.sh -o /tmp/provision.sh

cat /tmp/provision.sh

curl -L https://app.torizon.io/scripts/provision-device.sh -o /tmp/provision.sh sudo bash -x /tmp/provision.sh \ -t “TOKEN” \ -u https://app.torizon.io/api/accounts/devices \ -g https://dgw.torizon.io

This sequence of command worked for me, but the workaround won’t be viable for production,

Hope these information will be enough I don’t know which information I can give you guys,

I’m working on a Torizon 6.7 OS (tried on a 7.6 and the issue is the same) verdin imx8mp,

Thank you in advance for your help,

Kind regards,

Muzzy

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

(1)

The provisioning command format you’re using appears correct based on the standard Torizon Cloud provisioning process (1). Let me help troubleshoot this issue.

Standard Provisioning Process

The normal provisioning command should follow this format (1):

curl -fsSL <provisioning-script-URL> | sudo bash -s -- -t "<token-string>" <extra-script-parameters> && sudo systemctl restart aktualizr fluent-bit

Troubleshooting Steps

Since your workaround of downloading the script first worked, this suggests a potential issue with the direct piping method. Here are some diagnostic steps:

1. Check Network Connectivity

First, verify you can reach the provisioning script:

curl -I https://app.torizon.io/scripts/provision-device.sh

2. Test Script Download

Try downloading the script to examine it:

curl -fsSL https://app.torizon.io/scripts/provision-device.sh -o /tmp/provision-test.sh

3. Check for Silent Failures

Add verbose output to see what’s happening:

curl -fsSLv https://app.torizon.io/scripts/provision-device.sh | sudo bash -s -- -t "YOUR_TOKEN" -u https://app.torizon.io/api/accounts/devices -g https://dgw.torizon.io && sudo systemctl restart aktualizr fluent-bit

Custom Device ID and Name

If you want to set custom Device ID and Device Name during provisioning, you can add the -d and -n options (1):

curl -fsSL <provisioning-script-URL> | sudo bash -s -- -t "<token-string>" -d "my-device-id" -n "My Product 0053" && sudo systemctl restart aktualizr fluent-bit

Alternative Approach

For production environments, consider using provisioning at scale with shared-data and online-data embedded in your Torizon OS image (1). This eliminates the need for manual provisioning commands on each device.

Verification

After successful provisioning, verify the device appears in your Torizon Cloud dashboard and check the Aktualizr service status:

sudo systemctl status aktualizr
journalctl -f -u "aktualizr*"

The fact that your manual download approach works suggests the issue is likely related to the direct piping method rather than authentication or network connectivity problems.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Greetings @Muzzy,

I was able to reproduce similar findings on my own device. I’ll report this to our Platforms team for further analysis and fixing. Thank you for bringing this to our attention.

Best Regards,
Jeremias

4

The provisioning command from the web UI is now fixed. Thank you again for bringing this to our attention.

Best Regards,
Jeremias