Help Center>
ModelArts>
FAQs>
Notebook (New Version)>
VS Code>
What Do I Do If a Restarted Notebook Instance Can Be Connected Only After I Locally Delete known_hosts?
Updated on 2022-12-06 GMT+08:00
What Do I Do If a Restarted Notebook Instance Can Be Connected Only After I Locally Delete known_hosts?
To resolve this issue, set notebook parameters StrictHostKeyChecking no and UserKnownHostsFile=/dev/null in the local ssh config file.
Host roma-local-cpu HostName x.x.x.x # IP address Port 22522 User ma-user IdentityFile C:/Users/my.pem StrictHostKeyChecking no ForwardAgent yes
Note: SSH logins are insecure because the known_hosts file will be ignored during the logins.
Parent topic: VS Code
VS Code FAQs
- What Do I Do If Installing a Remote Plug-in Failed?
- What Do I Do If a Restarted Notebook Instance Can Be Connected Only After I Locally Delete known_hosts?
- What Do I Do If the Source Code Cannot Be Accessed When I Use VS Code for Debugging?
- What Do I Do If a Message Is Displayed Indicating an Incorrect Username or Email Address When I Use VS Code to Submit Code?
- How Can I View Remote Logs in VS Code?
- How Can I Open the VS Code Configuration File settings.json?
- How Can I Change the VS Code Background Color to Light Green?
- How Can I Set the Default Remote Plug-in in VS Code?
- How Can I Install a Local Plug-in on the Remote End or a Remote Plug-in on the Local End Through VS Code?
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.
Chatbotmore