SSH Key Entry Returns 500 Error: Torizon Cloud Remote Access

Technical Support
1

Attempting to add any SSH key to Torizon Cloud’s remote access portal returns this error:

SSH Key was not added, please try again.

Request failed with status code 500

I’ve attempted to add keys from multiple separate machines (Windows and Ubuntu) and multiple browsers (Firefox, Chrome, and Edge) with the same result.

sshKey_500Error
sshKey_500Error802×523 15.2 KB

Any advice on why this might be happening would be greatly appreciated.

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.

SSH Key Registration Issue with Torizon Remote Access

The error you’re encountering (status code 500) when attempting to add SSH keys to Torizon Cloud’s remote access portal suggests a server-side issue. Based on the documentation, SSH keys are registered using the POST endpoint for remote access user public keys(1).

Prerequisites for SSH Key Registration

Before troubleshooting the key registration issue, ensure you meet the preparation requirements for Torizon Remote Access(2):

  • Have an account on https://app.torizon.io with access to the remote access feature
  • Check the commercial plans for access to this feature(2)
  • Your target device should be provisioned in Torizon Cloud(2)
  • The device must comply with network requirements(2)

SSH Key Format Requirements

When generating SSH keys for Torizon Remote Access, ensure they follow proper SSH key formatting standards(3). The API expects the key data in a specific JSON format with “meta” and “pubkey” fields(1):

{
  "meta": null,
  "pubkey": "string"
}

(1)

Troubleshooting Steps

  1. Verify Key Format: Ensure your SSH public key is properly formatted and doesn’t contain any extra characters or line breaks that might cause parsing issues.

  2. Check Account Permissions: Verify that your Torizon Cloud account has the appropriate permissions for the remote access feature.

  3. Try Different Key Types: If you’re using a specific key type (RSA, ED25519, etc.), try generating a different type to see if the issue is key-type specific.

  4. Browser Cache: Clear your browser cache and cookies for the Torizon Cloud portal.

Since this appears to be a server-side error (HTTP 500), and you’ve already tried multiple machines and browsers, the issue likely requires attention from the Torizon Cloud infrastructure team.

Alternative Connection Methods

While resolving the SSH key registration issue, you can still establish SSH connections to your Torizon devices using traditional methods with IP addresses or hostnames(3), though this won’t provide the security benefits of Torizon Remote Access(2).

If the issue persists across multiple attempts and platforms, I recommend checking the Torizon Cloud service status or reaching out through the community portal for server-side troubleshooting assistance.

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

Hi @srwillie

It seems you marked the AI message as a solution. That’s great. Can you elaborate what specifically fixed it for you?

Drew

4

This was the section that helped me:

The exact formatting in the quoted text didn’t work, but it convinced me to paste the entire contents of the generated SSH key file rather than just the key string.

Pasting in just,

<ssh-key>

returns the 500 error.

However, with the full file contents,

ssh-rsa <ssh-key>=user@domain

it works.

Thanks,

Sean