Channel request subsystem failed when code <host>:<path/to/project> attempted about blink HOT 5 OPEN

Do you have SFTP enabled in the remote? One good test in this scenario is to enable the Files.app and see if things work there.

from blink.

Despite using a MacOS server, and reading (possibly out of date) that enabling Remote Login is all that is needed to enable sftp, SFTP was not enabled. I needed to uncomment the Subsystem sftp line in my /etc/ssh/sshd_config, and now it is working. Thx!

I would recommend better error messaging for this situation. You knew immediately what the problem was, but there was no error reported, and blink-fs was disabled keeping me from the .log. I'm guessing popping up a modal isn't easy in this situation, but something beyond the .log would be better UX.

But as notes:

1. I didn't realize I needed to add sftp support to the server to use code. Not clear at https://docs.blink.sh/advanced/code
2. Your Files.app Integration page does mention SFTP Subsystem errors, but I wasn't focused on Files.app integration (so I didn't read those docs), and the error message I got Channel request subsystem didn't lead me to think it was an sftp problem even once I was able to read the .log.

PS: now realizing that connecting this way does not allow me to use the integrated terminal. (Not that there is anything wrong with blink's terminal! 🙂) And that all my extensions need to be local not just remote, which is not how I was using the app up until now, but that's all on me.

from blink.

Thanks a lot for the extra feedback Daniel!! Yep, this is not the first time I deal with this issue, but I failed to see a way to communicate with the user. Definitely improving the docs and logs. I already have two issues open for improving both the instructions for VS Code installation and for the VS Code integration.

• You gave me one idea, we may not be able to communicate with the user through VS Code - I had problems setting that up, but maybe worth a second look -. But, we may be able to communicate through App Notifications. This way, we could point out "login" problems, or "channel initialization" issues which are usually on the SFTP subsystem.

And yes, using Blink-FS, which is just a SFTP integration on top of vscode.dev, will only give you access to proper file editing. But, the editor itself is a whole lot more powerful than current editors for iOS (ie. auto-complete with content of open files, etc...), and if you are for example connecting to a "low power" device like a Raspberry Pi, this is usually a better solution than running full VS Code in remote.

from blink.

I guess I had a different expectation for what remote dev would look/be like, something more akin to Remote-SSH. For instance, I was surprised to not be able to use Git extensions (Source Control or GitKraken) which I fully expected. I still need to explore using code-server with Blink as an option. Personally, I'm just trying to move my dev environment to the cloud, but have it be similar to working locally. So every caveat is a chin scratcher.

As for communicating with the user, perhaps making sure that Blink-FS extension loads (if available), and opening the blinkCode.log on error would be a means of communicating what happened without having to modify the UI at all. Just a thought on an innovative hack solution that may work.

from blink.

So for your intended use case, tunnels have replaced Remote-SSH, so that is the way to go. You can test things out within Blink Build, which is what I regularly use for this, and see what the experience from your side tweaking things could be. Let me know if you want to, I can throw you a code so you can kick the tires for a month.

PS: I think Microsoft never published the Remote SSH part of the extension and they just replaced it with Tunnels. Our integration just taps on the File system, which is the only thing they allowed.

from blink.