I was getting the exact same error as the original poster received and yet none of the other answers were my issue. You have to put your assets (or pre-build app) in a repo and connect to cloudflare pages. If VS Code Remote Server installation had slightly better error logic and better error messages none of us would be wasting hours doing this simple task. Create quick diagrams and Wireframes using Excalidraw + VSCode. Even when all of my ssh keys and remote ids have been copied and tested from both the Windows command line and inside a WSL Ubuntu instance. I cannot figure out why on some machines, a smooth remote installation is not possible. I have tried playing with the setting "Use remote.SSH: Use Flock" and other tricks posted on StackOverflow but none of these work for me whenever I have remote installation issues. If you got here because you were trying to install VS Code in the first place and for whatever reason VS Code had issues with the remote installation, I highly recommend installing it manually by downloading and extracting the tar file to the remote machine directly. This trick only works if there is a valid ~/.vscode-server on the remote machine with a hash that matches your local VS Code installation. I use it on about 7 remote machines and every once in a while something goes awry and it cannot recover from simple errors and gets stuck in installation loops. VS Code Remote Server install is not very robust. I deleted both files and then VS Code came up right away. Install sshpass: Code: Select all sudo apt install sshpass in the directory HOME/bin, create a shell script named ssh-add. These two files on the remote server in the folder. Where was my remote user name and xxx the VS Code Remote Server build hash. In my case there were two files that look like
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |