Help Center/
ModelArts/
Troubleshooting/
DevEnviron/
Failures to Access the Development Environment Through VS Code
Updated on 2025-08-22 GMT+08:00
Failures to Access the Development Environment Through VS Code
- VS Code Window Is Not Displayed
- Remote Connection Failed After VS Code Is Opened
- Failed to Connect to the Development Environment Via VS Code
- Error Message "Could not establish connection to xxx" Is Displayed During a Remote Connection
- Connection to a Remote Development Environment Remains in the "Setting up SSH Host xxx: Downloading VS Code Server locally" State for More Than 10 Minutes
- What Do I Do If the Connection to a Remote Development Environment Remains in the State of "Setting up SSH Host xxx: Copying VS Code Server to host with scp" for More Than 10 Minutes?
- Connection to a Remote Development Environment Remains in the State of "ModelArts Remote Connect: Connecting to instance xxx..." for More Than 10 Minutes
- Remote Connection Is in the Retry State
- Error Message "The VS Code Server failed to start" Is Displayed
- Error Message "Permissions for 'x:/xxx.pem' are too open" Is Displayed
- Error Message "Bad owner or permissions on C:\Users\Administrator/.ssh/config" Is Displayed
- Error Message "Connection permission denied (publickey)" Is Displayed
- What Do I Do If Error Message "ssh: connect to host xxx.pem port xxxxx: Connection refused" Is Displayed?
- What Do I Do If Error Message "ssh: connect to host ModelArts-xxx port xxx: Connection timed out" Is Displayed?
- Error Message "Load key "C:/Users/xx/test1/xxx.pem": invalid format" Is Displayed
- Error Message "An SSH installation couldn't be found" or "Could not establish connection to instance xxx: 'ssh' ..." Is Displayed
- Error Message "no such identity: C:/Users/xx /test.pem: No such file or directory" Is Displayed
- Error Message "Host key verification failed" or "Port forwarding is disabled" Is Displayed
- Error Message "Failed to install the VS Code Server" or "tar: Error is not recoverable: exiting now" Is Displayed
- Error Message "XHR failed" Is Displayed During VS Code's Connection to a Remote Notebook Instance
- VS Code Connection Automatically Disconnected If No Operation Is Performed for a Long Time
- Remote Connection Takes a Long Time After VS Code Is Automatically Upgraded
- Error Message "Connection reset" Is Displayed During an SSH Connection
- Notebook Instance Is Frequently Disconnected or Stuck After It Is Connected with MobaXterm Using SSH
- Error Message "Missing GLIBC, Missing required dependencies" Is Displayed When VS Code Is Used to Connect to a Development Environment
- Error Message Is Displayed Indicating That ms-vscode-remote.remot-sdh Is Uninstalled Due to a Reported Issue When VSCode-huawei Is Used
- Instance Directory in VS Code Does Not Match That on the Cloud When VS Code Is Used to Connect to an Instance
Parent topic: DevEnviron
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot
