Help Center/ ModelArts/ Troubleshooting/ DevEnviron/ SSH Faults/ Accessing a Notebook Instance Using SSH for Troubleshooting
Updated on 2025-11-18 GMT+08:00

Accessing a Notebook Instance Using SSH for Troubleshooting

The following table lists the possible reasons for SSH faults.

Table 1 SSH fault causes

Fault Type

Possible Cause

Reference

Permissions

The key pair does not match or the permission on the local key file is incorrect.

Error "Bad permissions/Permission denied (publickey)" Is Displayed When a Notebook Instance Is Connected Using SSH

The account is locked. As a result, the SSH or VS Code cannot be accessed.

Notebook Access Is Normal on ModelArts but Error "Permission denied (publickey)" Is Displayed When SSH/VS Code Is Used to Access a Notebook Instance

The permissions on the /home/ma-user/.ssh directory were changed, so SSH will not work.

SSH Cannot Be Used and the Error "Permission denied (publickey)" Is Displayed After the Permission on the /home/ma-user/.ssh Directory Is Changed

Connection rejected

If you use SSH to connect to a notebook instance and have more than 10 connections at the same time, your connection will be rejected.

Over 10 Connections Are Established When a User Uses SSH to Connect to a Notebook Instance. Error "ssh_exchange_identification: Connection closed by remote host" Is Reported

SSH access is occasionally denied. Error "Not allowed at this time" is reported.

SSH Access Is Occasionally Denied, and the Error Message "Not allowed at this time" Is Displayed

Remote SSH is enabled for your custom image, and OpenSSH is incompatible or earlier than 8.0. As a result, the connection is rejected.

Error "The OS version does not match" Is Displayed When Connecting to a Notebook Instance Created Using a Custom Image Through SSH