首页The authenticity of host '192.168.16.203 (192.168.16.203)' can't be established.

The authenticity of host '192.168.16.203 (192.168.16.203)' can't be established.

时间: 2024-05-18 21:18:21 浏览: 126

transitions.glsl.io:我们已经搬到

转换.GLSL.io 源代码，这是构建的开放集合的开放平台。技术服务器：Scala 堆栈：、、客户端：JavaScript 堆栈： + + 更多构建和运行构建前端堆栈：需要： : 已安装。还有 # in ./client/ npm install && grunt 运行服务器：需要： : 已安装 + 已注册的 Github 应用程序 #! /bin/bash # to put in a script – in ./server/ APP_SECRET=... GIST_ROOT_ID=... GITHUB_CLIENT_ID=... GITHUB_CLIENT_SECRET=... GITHUB_COOKIE=... GITHUB_AUTHENTICITY_TOKEN=... sbt -Dglslio.rootGist= " $GIST_R

It seems like you are encountering an issue with the authenticity of a host. This warning usually occurs when connecting to a remote server using SSH for the first time. The authenticity of the host is not established because your computer does not have the host's public key stored in its known_hosts file. To resolve this issue, you can follow these steps: 1. Verify that you are connecting to the correct host. Double-check the IP address or hostname to ensure it matches the one you intended to connect to. 2. Check with the system administrator or owner of the remote server to confirm that it is safe to proceed with the connection. 3. If you trust the remote server, you can add its public key to your known_hosts file. You can do this by running the following command in your terminal: ``` ssh-keyscan -H 192.168.16.203 >> ~/.ssh/known_hosts ``` Replace `192.168.16.203` with the IP address or hostname of the remote server. 4. After adding the public key, try connecting to the remote server again. You should no longer see the authenticity warning. Remember to exercise caution when connecting to unfamiliar hosts and always verify their authenticity before proceeding.

阅读全文