
Member-only story
VSCode & Remote-SSH connectivity issue…
I have tried to learn and share my knowledge in the area of blockchain for quite some time, and through all those years, I have tried to use the same tools. Not because I don’t want to adapt to the new ones but because those tools simply do their job. I use mostly Virtual Box to run my virtual machines (it almost makes me a hacker ;) ), mainly with the Ubuntu distribution of Linux. Because I run it on my laptop with Windows 10 operating system, I also use WinSCP to transfer files with Putty as a session terminal.
But the tool I use the most often to prepare scripts, execute them and manage my GitHub repositories is Visual Studio Code whit a Remote-SSH connection. Because the VSCode also provides a terminal window, I use Putty less and less, not to mention WinSCP. As a result, VSCode seems to be the crucial tool in my workshop, so it’s vital to have it working reliably, especially when connecting to the virtual machines via Remote SSH, one of the VSC plugins.

But recently, when I decided to switch from Hyperledger Fabric blockchain to Hyperledger Besu, I was forced to extend the disk space for my VM. After completing all actions, I achieved the primary goal, but it wasn’t a complete success. For some reason, my connectivity configuration for the modified machine was dropped, and I could not restore it. All other tools worked fine (for example, putty and WinSCP), but establishing an SSH connection from VSC was challenging. Redefining configurations or even reinstalling some components didn’t help, and it seemed like I’ll have to recreate all VM with my BESU repositories.
But finally, I found the solution it worked fine. I want to share it with you, as it can save you some time.
The solution is as easy as removing all data stored in a ~/.vscode-server
directory, which actually removes all VSCode server data from the targeted VM.
The simplest way to do so is to use the command below:
rm -Rf ~/.vscode-server/
Of course, you may face the fact that some processes use the VSCode server resources, but it wasn’t my case. It can happen when the…