<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Iago Felicio on Medium]]></title>
        <description><![CDATA[Stories by Iago Felicio on Medium]]></description>
        <link>https://medium.com/@iagofelicio?source=rss-92235f57a44b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*4_ZoJhqD6M3Tmedj.</url>
            <title>Stories by Iago Felicio on Medium</title>
            <link>https://medium.com/@iagofelicio?source=rss-92235f57a44b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:43:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iagofelicio/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How I connected my VS Code to a remote server using Remote Development Extension Pack in Windows]]></title>
            <link>https://medium.com/@iagofelicio/how-i-connected-my-vs-code-to-a-remote-server-using-remote-development-extension-pack-in-windows-3af1ada761ae?source=rss-92235f57a44b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3af1ada761ae</guid>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[remote-development]]></category>
            <category><![CDATA[vs-code-extensions]]></category>
            <category><![CDATA[vscode-extension]]></category>
            <dc:creator><![CDATA[Iago Felicio]]></dc:creator>
            <pubDate>Fri, 13 Sep 2019 21:57:49 GMT</pubDate>
            <atom:updated>2019-09-13T22:00:05.386Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello everyone,</p><p>If you don’t know about this amazing extension take a look at: <br><a href="https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack">https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*2jrQ7prLI9osPp1fIcU3Lg.png" /></figure><p>Well, let’s go to an important consideration:</p><blockquote><strong>This sharing do not intend to be a tutorial on how to connect your VS Code using Remote Development Extension Package in every Windows distributions. I’m simply sharing what I did that worked in my very specific case.</strong></blockquote><h3>This text is divided in sections:</h3><ol><li>Context</li><li>Problem and Workaround</li><li>Conclusion</li></ol><h3>Context</h3><p>I’m working with some EC2 instances of AWS (CentOS distros) that is managed by a “Manager” instance using Windows 10. Usually, I connect myself using RDP to this Manager instance, then I connect to some of this Linux server using <a href="https://cmder.net/">Cmder</a> or <a href="https://www.putty.org/">PuTTY</a> and finally I can work.</p><p>Previously I had a workaround using the extension <a href="https://marketplace.visualstudio.com/items?itemName=rafaelmaiolla.remote-vscode">Remote VSCode</a> which was pretty handy, but I hat to open each file individually and couldn’t import a project into VS Code.</p><h3>Problem and Workaround</h3><p>Since Microsoft released the extension package for <a href="https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack">Remote Development</a>, I got really excited to test it on this specific context because I had already tried connecting into remote servers from my personal Linux machine and I loved it.</p><p>But when I installed the extensions on VS Code in this Manager instance, a lot of problems appeared.</p><p><strong><em>First problem</em></strong>: Config file</p><p>Actually it’s not exactly a problem. Since I installed <em>Cmder</em> I was already aware that creating a config file for my SSH connections so VS Code could easily retrieve the information on Remote Connection Targets.</p><p>The <strong>config</strong> file looks like:</p><blockquote><em>Host </em>RandomName<em><br> HostName </em>xx.xxx.xxx.xxx<em><br> Port 22<br> User </em>myUser</blockquote><p>The Remote Explorer then shows my <em>RandomName</em> connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/278/1*vRi0yDpVY9Ct8NsFpKS7hQ.png" /></figure><p><strong><em>Second Problem</em></strong>: Setting up an SSH Client in Windows</p><p>This was the real problem. I’ve actually researched a lot until I could find some solution. <strong>Why was this a problem?</strong></p><p>The documentation of the package provides some <a href="https://code.visualstudio.com/docs/remote/troubleshooting#_installing-a-supported-ssh-client">Tips and Tricks</a> on how to install a supported SSH Client, which for me (Linux user) wasn’t clear and easy at all. At the end following the instructions didn’t work. For some IT Governance reasons, I couldn’t simply install an SSH Client using Windows native ways mentioned in the tutorials. So, this is how I easily installed the OpenSSH client.</p><ol><li>Download the proper package from here: <a href="https://github.com/PowerShell/Win32-OpenSSH/releases/">https://github.com/PowerShell/Win32-OpenSSH/releases/</a></li><li>Extract the content you downloaded and put all the files in your <strong>system32</strong> directory (.dll, .exe, folders, etc).</li></ol><p>That’s it! :P</p><p>I had a lot of troubles finding this out. It motivated me sharing this simple solution but may be not that simple to everyone.</p><p><strong><em>Third Problem</em></strong>: My user couldn’t create the proper config folders needed by Remote Development extension.</p><p>That was also really simple! You just need to create the following folder in the server you are trying to connect with and provide writing permissions:</p><blockquote>sudo mkdir /home/.vscode-server<br>chmod -R 777 /home/.vscode-server</blockquote><p><em>Disclaimer</em>: <em>Above I provided full permission to all users. This might not be secure or appropriated. Provide the right permissions accordingly to your need.</em></p><h3>Conclusion</h3><p>This simple sharing aims to show you some tips on what you should at least look for. The main part was the installation of the OpenSSH Client on my context.</p><p>If you have any tip that I should include, let me know!</p><p>:D</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3af1ada761ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>