Failed to Connect to the Development Environment Via VS Code

Network Link Check

1. On the ModelArts console, check that the notebook instance is normal.
2. Run the following command on the VS Code terminal to check whether the SSH command is available:

   ssh -i <Relative path for the key> -p <Port> ma-user@<Domain name/IP address>

   • If SSH is available, skip 3 and proceed with the remote check.
   • If SSH is unavailable, go to 3.
3. Run the following command on the VS Code terminal to check the network connectivity. If the network is abnormal, check the port.

   curl -kv telnet://<Domain name/IP address>:<Port>

   • If the port is abnormal, contact technical support.
   • If the port is normal, proceed with the remote check.

Remote Check

1. Check whether the permission on the /home/ma-user directory is 755 or 750. If not, run the following command to set the permission:

   chmod 755 /home/ma-user

2. Check whether the permission on the /home/ma-user/.ssh directory is 755 or 750. If not, change the permission.
3. If an error is displayed indicating that the key does not have the permission, check whether the key in use is your own key (a key with the same name may be used mistakenly). In this case, replace the key and connect to the instance again.

Local Check

1. Check whether the configurations are correct.

   Open the config file and check the configurations. Host must be placed in the first line of each group of configurations as the unique ID.

   

   HOST remote-dev
        hostname <instance connection host>
        port <instance connection port>
        user ma-user
        IdentityFile ~/.ssh/test.pem
        StrictHostKeyChecking no
        UserKnownHostsFile /dev/null
        ForwardAgent yes

   • If the configurations are correct, proceed with the subsequent steps.
   • If they are not, correct them according to the preceding format.

2. Check the key file path. You are advised to save the key file in C:\Users\{user}\.ssh and ensure that the file does not contain Chinese characters.
3. Check whether the plug-in package is of the latest version. Search for the plug-in in extensions and check whether it needs to be upgraded. Check whether the Remote-SSH third-party plug-in is compatible.

   

4. Check whether the local VS Code is of the latest version. The latest version may have bugs. Version 1.82 is recommended.

   If the fault persists, contact technical support.