User Guide
Overview
Interactive Sessions
OverviewCreate Session
Interact With Devices
OverviewSSH KeysAutomotive SessionCompute SessionIoT SessionMobile SessionADB CommandsSSH TroubleshootingFile BrowserExtend Session
View Session
Preparing PowerShell Test PackagesProfiling DevicesRTSP StreamingLLDB Setup Guide
FAQContact Us

SSH Troubleshooting

Common issues and solutions when connecting to QDC devices over SSH.

Why am I seeing a security warning about host authenticity?

When connecting for the first time, you may see a message like:

The authenticity of host 'ssh.qdc.qualcomm.com' can't be established.
Are you sure you want to continue connecting (yes/no/[fingerprint])?

This is a standard SSH security feature that appears the first time you connect to a new server. Type yes and press Enter to continue.

What if the SSH tunnel fails with "Permission denied"?

If you see an error like this when running the SSH tunnel command:

bind [127.0.0.1]:<port>: Permission denied

This means the port is already in use by another process.

To fix:

  1. Close any other SSH tunnels or applications using the port
  2. Run the SSH tunnel command again

Using ADB?

If you're connecting to a Mobile, Automotive, or IoT device with ADB enabled, the port may be in use by a local ADB server. Run adb kill-server to free the port, then try the SSH tunnel command again.

What if the RDP connection fails?

If your RDP client can't connect to a Compute device:

  1. Verify the SSH tunnel is still running — check that the terminal window from Step 1 is still open and hasn't disconnected
  2. Verify the SSH session is active — check that the terminal window from Step 2 is still connected
  3. Confirm you ran the passwordless login command — the reg add command must be completed before RDP will accept a blank password
  4. Check the port — make sure you're using the correct RDP port value from the Connect dialog

How do I connect to additional ports on the device?

QDC allows you to connect to additional ports on the device in the range 8900 to 8909.

Before running the command below, replace the following values with your session details:

ValueDescriptionWhere to find it
{path_to_private_key}Path to your SSH private key fileThe file you created/uploaded when setting up SSH keys
{session_id}Your session execution IDShown in the Connect dialog of your Interactive Session

Example command to forward port 8900 over SSH tunnel:

ssh -i {path_to_private_key} -L 8900:sa{session_id}.sa.svc.cluster.local:8900 -N sshtunnel@ssh.qdc.qualcomm.com
ADB Commands
File Browser
Why am I seeing a security warning about host authenticity?
What if the SSH tunnel fails with "Permission denied"?
What if the RDP connection fails?
How do I connect to additional ports on the device?
Terms of UsePrivacy PolicyCookie PolicyCookie SettingsContact Us
2026 ©Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. References to "Qualcomm" may mean Qualcomm Incorporated, or subsidiaries or business units within the Qualcomm corporate structure, as applicable. Qualcomm Incorporated includes Qualcomm's licensing business, QTL, and the vast majority of its patent portfolio. Qualcomm Technologies, Inc., a wholly-owned subsidiary of Qualcomm Incorporated, operates, along with its subsidiaries, substantially all of Qualcomm's engineering, research and development functions, and substantially all of its products and services businesses. Qualcomm products referenced on this page are products of Qualcomm Technologies, Inc. and/or its subsidiaries. Materials that are as of a specific date, including but not limited to press releases, presentations, blog posts and webcasts, may have been superseded by subsequent events or disclosures. Nothing in these materials is an offer to sell any of the components or devices referenced herein.