E170013: Unable to connect to a repository

[lapo-luchini]

Error while connecting to SSH:

svn: E170013: Unable to connect to a repository at URL 'svn+ssh://lapo@server/home/svn/repos/path/file.js'
svn: E210002: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file.
svn: E210002: La connessione di rete è stata improvvisamente interrotta

I'm using VSCode 1.26.0 on FreeBSD 11.2 (amd64), which is probably a rare environment not being officially supported yet, but e.g. johnstoncode.svn-scm is working correctly so it shouldn't be a system configuration error.
SSH is using agent to authenticate.

Still didn't find the time to properly debug the error.

[ghost]

Simulart issue.
svn: E170013: Unable to connect to a repository at URL 'svn://[repo]' svn: E210002: Network connection closed unexpectedly

Using VSCode 1.31.1 on Windows 10.

It shows blame but not for all files.

[liuyw07]

Exact same issue here, VSCode 1.32.3, Fedora 29, using ssh-agent

[jstolte]

Pretty sure this used to work for me when I was in the office and working on Ubuntu 18.04.5 LTS distribution of Linux.
Now, with COVID, I am working from home on a Windows 10 laptop.
I connect to the office network via a VPN.
I am using VSCode 1.52.1... and I connect up to my linux box in the office using the Remote - SSH plugin which is where my workspace/file physical reside... (I do not do a local Window 10 checkout... the build tool chain that we use needs a Linux environment to properly build and the target embedded controller is also on the VPN in my work office... so if I edited files locally, I would need to checkin from Windows, PuTTy or Terminal into the Linux box, update checkout on Linux box and then launch the build process from Linux terminal connection). Using VSCode and Remote - SSH plugin, I can setup my VSCode workspace to directly edit the files checked out on my remote Linux box... then in the Terminal built into VSCode I can launch the build system which builds the application on the Linux box and pushes it over to an embedded controller that is also on the work VPN in my office at work. This allows me to verify that my updates work before checking code into SVN repository.)
The SVN plugin by Chris Johnston is working fine as I can update/commit files to the SVN repository that are checked out on my Linux box.
The workaround mentioned in Issue #5 does NOT appear to work in my setup. Yes, it prompts me for credentials... but trying "blame" after successfully running "svn info --show-item revision http ://xx/xx/xx/xx/xx/xx/xx.xx" still generates the following error message in VSCode...
svn: E170013: Unable to connect to a repository at URL 'http ://xx/xx/xx/xx/xx/xx/xx.xx'
svn: E215004: No more credentials or we tried too many times. Authentication failed

[metacurb]

This is a duplicate of #5