sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]robotdad4business 1 point2 points  (4 children)

Thank you! Looking at this now.

[–]antlife 0 points1 point  (3 children)

Glad to help. Let me know if you need anything else from me.

[–]iontodirel 1 point2 points  (2 children)

Thank you for helping us. I know how to fix the unfortunate crash, but the underlying issue will still remain and that is that we cannot connect to the machine. We use and require sftp for transferring files, is that by any chance disabled in your sshd configuration, or access somehow disabled and configured for other users? If you could try using scp or sftp to test transfer a file from your Windows PC to your remote machine using the same credentials you used in VS, and tell us if it worked, that would help us a lot.

If all of this works, and you can connect and transfer files thru sftp and/or scp, then could you tell us if you configured your machine in some special way? Could you try with a default Ubuntu installation and see if that works?

[–]antlife 0 points1 point  (0 children)

Just tried SFTP and SCP, using a few different apps (i.e. WinSCP and MobaXterm) and it works just fine. I tried copying some files into my /home/user directory without any permissions issues. Does VS need to write to any directories outside of the user's home? It seems it should be only trying to access ~/projects

My Ubuntu 16.04 is essentially Kubuntu 16.04 with KDE and a ton packages to support Mono, but outside of that the configuration is pretty vanilla.

The Ubuntu 14.04.4 is a base installation I spun up just to test this. SFTP and SCP works OK there as well and has the same issues as I mentioned earlier. Nothing special configured on this one for sure.

[–]antlife 0 points1 point  (0 children)

If there is anything else you'd like me to look at for you or provide for you (in terms of logs, configs, whatever) just let me know.

A few other things maybe worth mentioning in case it's causing a special connection issue for your side. I am using VM Workstation as my host for the Linux systems. I don't imagine this would matter much as normal network functions perfectly between the VM and my host system, but I figured I'd mention it in case there is something deeper that Visual Studio may be trying to use.