![]() If everything went fine you should now be connected to your server. If it is the later and you are sure no one messed with your server, you can ignore the warning and update the fingerprint with the following command: CopyĪfter the fingerprint confirmation VS Code Remote will ask you to put in the password for the specified user.Įntering the password each login is cumbersome, so later in this post I will show you how you can skip this step using SSH Public Key authentication.Īfter a successful login, VS Code Remote will start installing Visual Studio Server on the remote server which might take a while. This might also happen if you connect to a server with the same private IP address (RFC 1918), but in a different network. If for any reason you get an error saying the fingerprint does not match with the one saved on the computer, your server might have been altered. This is a security measure from SSH to be safe for future connections that the server will always be the same and was not compromised. The first time you connect to a server it will ask you to confirm the servers fingerprint. In my case I am connecting to the server 192.168.1.10 with the user pi. ![]() ]hostname is the syntax how you connect to a server using SSH. Next you need to enter which user and server IP or hostname you want to connect to. To connect to a server you just have to click it. You might notice a new icon on the bottom left of the VS Code window. Visual Studio Code Remote should now be installed and you should be able to connect to servers with SSH. You can also install it by visiting the Visual Studio Marketplace Website and click install. Go to the extension menu in VS Code and search for remote.Ĭlick on Remote - SSH and later install, after the installation click reload. Install the Visual Studio Code Remote extension I know some of that vim magic myself and also am capable of exiting it, but sometimes I wish I could just use a good IDE like Visual Studio Code to edit my files on the server. ![]() If you find yourself ever configuring a service on a server you probably had to edit files directly via the terminal using nano, vim, emacs or some other text based editor.īy no means are those editors bad, but they are also not the easiest to use, at least for most of us. Editing files on a remote server using the Visual Studio Code Remote extension is that easy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |