I don't know the details on what is happening on the server side. Here's a brief overview from the VS Code docs
The Visual Studio Code Remote - SSH extension allows you to open a remote folder on any remote machine, virtual machine, or container with a running SSH server and take full advantage of VS Code's feature set. Once connected to a server, you can interact with files and folders anywhere on the remote filesystem.
No source code needs to be on your local machine to gain these benefits since the extension runs commands and other extensions directly on the remote machine.
During the initial setup, when the VS Code client first makes a connection to the remote server, it downloads and installs the remote server components of the VS code extension. This is installed on the remote computer in the ~/.vscode-server path. It seems like that part worked ok.
Later, when the VS Code client makes a connection parts of the server side component are executed and will interact with the client to provide remote file access, remote debugging, etc. This is where I'm getting the errors posted above, and the full trace log is similar to what @niko86 posted above.
That is correct, I can connect via SSH and sync files (outside of VS Code). In order to use VS Code locally on my Win10 machine to edit and debug files on PythonAnywhere, I believe it's using server side code and it appears to be using node 12.4.0.
This isn't critical to me right now, but it is something that would be nice to have, and I think others would benefit from this feature as well.
Would you like us to update your account so that you're using our new virtualization system, which should support the latest Node? It's in beta, so there might be problems with it, but we're not aware of any problems right now and we're rolling out the beta as broadly as possible so that we can track them down if there are any.
Ah, sorry! I've just realised that it wouldn't help. The new virtualization system will make it possible to run the most recent Node on PythonAnywhere in all cases, except in Jupyter notebooks and over SSH connections. And of course it's over an SSH connection that you need to run it for VS Code.
Sorry for the false hope! I'll flag this as a forum thread to post to when the new system works over SSH too.
Hi! What parmeters did you use for agent, python etc?
I did get this error "Error connecting to PythonAnywhere: All configured authentication methods failed"
We're certainly working on it! Just to re-state the background (because it was in a post I made some time ago), VS Code needs to be able to run a recent version of Node.js from the SSH connection that it makes. Recent versions of Node need to have access to the /proc filesystem, which means that they need to use our new virtualization system. We're still working out the last bugs in that in order to make it live for all of the in-browser consoles, websites, scheduled and always-on tasks. Once that's done, we should be able to switch it on for Jupyter notebooks and SSH. The reason that they are last is that we can enable it on a per-user basis for the other things, but Jupyter and SSH are all-or-nothing -- either every user will have to have it switched on or no-one will.
I think you should give this a little more consideration.
GitHub now has the '.' web editor available everywhere, and their CodeSpaces editor is very useful if you have it enabled. The Visual Studio Code editor is become ubiquitous. So when I ask my students to edit code using the PA online editor, as useful as it is, it doesn't have the editing features that a VS code would have, and the students are less enthusiastic about using it.
Using VS Code to remotely edit works very well (when the host allows it) and would be hugely useful.
Hoping you'll give this some serious effort at some point.
Thanks.
I think you should give this a little more consideration.
GitHub now has the '.' web editor available everywhere, and their CodeSpaces editor is very useful if you have it enabled. The Visual Studio Code editor is become ubiquitous. So when I ask my students to edit code using the PA online editor, as useful as it is, it doesn't have the editing features that a VS code would have, and the students are less enthusiastic about using it.
Using VS Code to remotely edit works very well (when the host allows it) and would be hugely useful.
Hoping you'll give this some serious effort at some point.
Thanks.
Sorry, we have had to rate-limit your feedback sending. Please try again in a few moments...
Thanks for the feedback! Our tireless devs will get back to you soon.
