I tried using the C++ template doing a helloworld project. It had issues

Technical Support
, , , ,
8

SSH Authentication Issue with Debug Container

This is a common authentication issue with the debug container. The problem is that the debug container uses SSH key authentication, not password authentication for the debugging session.

Understanding the Authentication Flow

When you connect to the target device on port 22, you’re connecting directly to the TorizonOS system (1). However, when debugging on port 2230, you’re connecting to the SSH service inside the debug container, which has different authentication requirements (2).

SSH Key Configuration

The Torizon IDE Extension automatically sets up SSH key authentication when you add a device (3). The extension should handle this automatically, but there might be an issue with the key setup.

Troubleshooting Steps

Step 1: Check SSH Key Configuration

Verify that SSH keys are properly configured in your project settings. The extension stores SSH connection parameters in the workspace settings (3):

  • torizon_ip: The IP address of your target device
  • torizon_login: The login username (typically “torizon”)
  • torizon_psswd: The password (stored as plain text in development)
  • torizon_ssh_port: The SSH port for the target device

Step 2: Verify Debug Container SSH Configuration

The debug container is configured with SSH access during the build process (4). Check if the container is properly configured by examining the container logs:

docker compose -p torizon logs helloworldcpp-debug

Step 3: Manual SSH Key Setup

If the automatic key setup isn’t working, you may need to manually configure SSH keys. The extension typically handles this, but based on community reports, there can be issues with SSH key authentication in certain environments (5).

Step 4: Check Extension Version Compatibility

You mentioned using extension version 3.2.5 with TorizonOS 7. Ensure that your extension version is fully compatible with your target OS version.

Alternative Debugging Approach

If SSH authentication continues to fail, you can try:

  1. Reset the device connection: Remove and re-add the target device in VS Code
  2. Check workspace settings: Verify that all connection parameters are correctly set in .vscode/settings.json (3)
  3. Try passwordless SSH setup: Configure SSH keys manually following the SSH documentation (6)

Common Resolution

Based on community feedback, this issue is often resolved by ensuring the SSH keys are properly generated and deployed by the extension (5). The extension should automatically handle the SSH key setup when you connect to a target device.

If the problem persists, try creating a fresh project and reconnecting to your target device to ensure clean SSH key generation.

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.